Opened 18 years ago
Closed 17 years ago
#5326 closed enhancement (fixed)
New columns on report
Reported by: | Owned by: | Christian Boos | |
---|---|---|---|
Priority: | normal | Milestone: | 0.11 |
Component: | report system | Version: | |
Severity: | normal | Keywords: | query |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
Would it be possible to have a 'days open' type column available for reporting?
In analysing the issues reported (particularly from our legacy system) it would be useful to be able to determine how long an issue has been open before deciding what to do with it.
Attachments (0)
Change History (4)
comment:1 by , 18 years ago
Resolution: | → duplicate |
---|---|
Status: | new → closed |
follow-up: 3 comment:2 by , 18 years ago
Resolution: | duplicate |
---|---|
Status: | closed → reopened |
It's not quite the same thing. You're showing when a ticket was last modified, but I need a report that shows when it was opened.
eg If there is an intermittent issue it may be 6 months old, but because there is a lot of activity on the issue, the last change may be a couple of weeks ago. In this instance, days open would be around 150, whereas last mod will be about 14.
comment:3 by , 18 years ago
Keywords: | query added |
---|---|
Milestone: | → 0.11 |
Owner: | changed from | to
Status: | reopened → new |
Replying to anonymous:
It's not quite the same thing. You're showing when a ticket was last modified, but I need a report that shows when it was opened.
Sure, it's not exactly the same, but those 2 informations always go together in the code, so #4966 and this one will get implemented together anyway. But let's keep this ticket open.
As for the report in #4296, it should be straightforward to modify it so that it uses the time
column instead of the changetime
one.
comment:4 by , 17 years ago
Milestone: | 0.11.1 → 0.11 |
---|---|
Resolution: | → fixed |
Status: | new → closed |
r6566 makes it possible to select the Created column for achieving this.
(That ticket really bordering on duplicate, as I said previously …)
For SQL reports, it's already possible, have a look at our report:20 (see #4296 for the corresponding SQL - it's PostgreSQL specific though).
For custom queries, this corresponds to #4966.