add Closed Date to list of columns offered in custom query

[jhn@…]

the Created and Modified columns are already offered by TracQuery. it would be very useful to also be able to add the Closed date to a report.

note that the Closed date on a ticket is not the same as the Last Modified date on a closed ticket. there may be follow-up communications long after a ticket has already been closed.

we often get requests from upper management or from clients for reports such as how many tickets were closed in a particular month. it is extremely tedious to search all closed tickets that were modified during or after that time, and then see when the ticket was actually closed.

another use of the Closed date column would be to run metrics such as average length of time that a ticket was open. if this column was available, it would take a quick export to excel and some simple calculations.

this data would be accessible with custom sql but i think there are enough common use cases that it would be worthwhile to make it part of the default package. i recall seeing many tickets related to custom date reports and this enhancement might provide enough for a lot of people.

it may not be that simple since i see in TracReports that the time and changetime columns live on the ticket table, but not the closed time. but the TracTimeline does show when tickets are closed, so hopefully that means it wouldn't be too hard to get at the data.

[Remy Blank]

Sounds like a good idea.

[Remy Blank]

Wrong milestone, sorry.

[anonymous]

I'd love to see this too. We've got very similar requirements to the requestor.

[Christian Boos]

Milestone 1.0 deleted

[Remy Blank]

Related to #8371, which suggests a filter for the last updater.

[Remy Blank]

Refocusing.

[anonymous]

I have to report that this missing features is the main reason I am looking for an alternative solution to Trac. We really like using Trac otherwise.

When managing projects with different builds going to different customers, or using multiple milestones for each (Agile), one needs to be able to quickly assess the changes from different Milestones that went into the current release. The only way I have found is using "Last Modified date". However, this is not equivalent to closed (for many people I guess). We put validation results in tickets, and other sorts of information, after the ticket is closed. Without being able to search on the closed date, it takes a day worth of sorting through tickets to get the proper list to report to customers. I've added a changeset closed on field, but that isn't automatic like a date would be.

[rpshaw@…]

I would like to see this added to Trac as well. Getting the date closed from the custom query would allow me to much more easily calculate ticket life and generate other reports.

[Andrew Kindred]

Just to add another name to the request for this. I too would love to have a Closed Date for the custom query. It would be extremely useful so please add this in ASAP.

[richard.mair@…]

Another request for that feature. We really need that heavily….

[torsten <torsten.piotraschke@…>]

We need this, too.

[john.ferg@…]

+1

[Marco A.]

We too would like to see this feature; it would be a great help in easily summarising metrics for our internal configuration management standards.

[jtorres]

This would be useful to have

[trac.domain.gauner@…]

I'm also missing this feature. At the moment we use as a "Recently closed tickets"-Query: status=closed&modified=1weekago.., but this breaks for instance, if a closed ticket gets a comment added to.