Ideas and suggestions for Trac's Custom Query
This page collects ideas and suggestions for enhancing the custom query, the batch modification feature and the TracQuery macro.
If you have a small nice idea but don't feel like starting a discussion on the MailingList or creating a new ticket, this is the place!
Related tickets
There are a 32 open issues in total: #1943, #2036, #2141, #2465, #2497, #2855, #3153, #3255, #4644, #5031, #5367, #5526, #5720, #6330, #7043, #7558, #7608, #7699, #8371, #9006, #9149, #9643, #9735, #9736, #10152, #10311, #10633, #10983, #11574, #12662, #13406, #13600
See them in custom query view!
TicketQuery
Integration with other modules
An "old" idea was to add to the possibility to view matching search results (from a TracSearch with tickets enabled) in the custom query view.
Now that we have the TracBatchModify feature, this is even more useful. And for that reason, it even be useful to do this from TracReports.
CSS
- …
Layout
- …
User interface guidelines
- …
Other glitches
- Header for last group in a page should show that it's only a partial count. For example, 3 matches (on this page) or 3 matches (more on next page). We already have a hint at the end of the group, so this must be easy to add
- Bonus points for doing the same for TracReports, there we don't even have a hint.
- Would be nice if Tickets by Milestone listed the milestones by date instead of name.
See also:
