Provide separate Tickets opened, Tickets closed checkboxes on timeline

[Ryan J Ollos]

I have a suggestion that I believe would make the timeline a more powerful project management/review tool.

In the weekly progress meetings that my team schedules, it would be useful to display on the Timeline: Tickets closed and Milestones reached. After discussing progress for the week, we might switch to display only Tickets opened in order to review new tickets generated this week.

To facilitate this, we'd need to change the Opened and closed tickets checkbox to two checkboxes: Tickets opened and Tickets closed.

On a related note, I think the nomenclature Tickets opened and closed for the existing checkbox is more consistent with the other labels: Tickets updated, Milestones reached, … and so forth, so even if the main topic of this ticket is not implemented, I think it would be worthwhile to change the label of the existing filter.

Some (perhaps all?) of what I would like to do here can be done using ticket queries, however the timeline is very user friendly and easy for project manager to use, so I think it would be worthwhile to have this functionality in the timeline.

Alternatives would be: use a TracIni option to determine whether the Tickets opened and closed checkbox is separated to two checkboxes, or implement as a plugin (though I'm not entirely sure this coudl be done … although I see how to add two filters, it is not clear to me how to remove the existing filter when creating a plugin).

I tried implementing a patch for this tonight, but came to the conlusion that I woud probably need a better understanding of what is going on inside the produce_event method in trunk/trac/ticket/web_ui.py@9278:247,278-320#L246​, so I probably won't finish this tonight.

[lkraav <leho@…>]

interesting, cc-ing

[Mikael Relbe]

Some thoughts expressed in ticket:2469#comment:4 are related to this ticket.

[Ryan J Ollos <ryano@…>]

I'd like to work on a patch for this if it is a feature enhancement that would be accepted. I'm assuming this would be targeted for 0.13, if anyone else even likes the feature.

The simplest implementation I can think of is to just replace the Tickets opened and closed checkbox with 2 checkboxes:

Tickets opened
Tickets closed

A more sophisticated approach might be to use some javascript to perform an action similar to what is done with Changesets in all repositories.

Tickets changed

Opened
Closed
Updated

When Tickets changed is selected, the 3 checkboxes below would appear and would initially all be selected. When Tickets changed is unselected, they would disappear.

[Christian Boos]

I'm not sure it's worth making the timeline filters more complex when we already have a lot of flexibility to achieve the same result in the Custom Query view, as you've noted yourself. If you'd like to have the results shown in a timeline, I think it would make more sense to have an option to show the Custom Query results in a timeline view (a new format 'timeline' that could also be used by the TicketQuery macro). Something like I did in the old SearchRefactoring branch (r5543) for an alternative display of the search results.

[Ryan Ollos <ryano@…>]

Replying to cboos:

I'm not sure it's worth making the timeline filters more complex …

That sounds like a good solution, though it looks to be a bit more complex and will take me a bit longer to implement. I'll probably tackle a few more simple tickets before I try to take on this one.

[AdrianFritz]

just noted this part

On a related note, I think the nomenclature Tickets opened and closed for the existing …

was done @ #9594

[Ryan J Ollos]

#12156 has a patch with a Ticket query renderer extension point (comment:4). Another possibility is to have a query syntax and a timeline filter in the timeline view (comment:1:ticket:11331).

#1329 is also related.