Trac doesn't handle lots of tickets or changesets very well

[dneary@…]

Once the size of a repository goes over a few hundred revisions and a couple of hundred bugs, a few issues become very annoying in Trac.

1. There is no way to search open bugs on the Label or Comment fields. The search page does not filter out closed bugs.
2. I cannot run a custom query, and save it for future use if I like it (generate report from custom query).
3. If I run a query and get a list of bugs, "Next ticket/Previous ticket" does not filter on the list, or filter out closed bugs. Ideally, the behavious would be identical to Bugzilla, and next/prev would traverse the last executed query.
4. The RSS feeds from changeset lists are not limited in size. I have an RSS feed with 2000+ entries, which is both useless and invalid RSS. This should be limited to 20 or 30 entries at most.
5. The RSS changeset feed entries bring you to a browser view of the tree at the revision chosen. It would be more useful to be brought to the changeset view.
6. Comments in bug reports are not editable. It would be great to have an "Edit" button beside ticket comments, which would eventually be included in the page's revision history (make ticket pages completely wikised, perhaps?). Obviously, permission issues could complicate things, but in most cases allowing comments to be edittable by validated users would be most useful.

I should probably have creates 6 different tickets for these issues, I hope you don't mind them all being lmumped in together. Hopefully I will be able to attach a couple of patches for one or two of them later. I really like Trac, by the way, and theer are a bunch of functions which are now part of my workflow and which I wondered how I could ever do without before. Keep up the good work.

[Christian Boos]

I'd suggest that you join the Trac MailingList in order to discuss the points you have raised, some of them being valid, some others are already addressed…

But as it is now, one can't really "act" on this compound ticket…

Later, you can still fill new tickets, one for each of the remaining points.

[Christian Boos]

1. open bugs on the label/comment

The Ticket Custom Query allows you to search on the label. The search module allows you to search within the ticket description and comments as well, but the results are not as useable as those presented by the reports/query module. The search module will be re-implemented in Trac 1.0.

2. save custom query

Actually, you can save the query in wiki pages, using either the query: syntax or the [[TicketQuery]] macro (see #909 and [1363])

3. query prev/next

This is actually implemented the way you suggest in the /trunk. I think this feature miss the possibility to "cancel" the last query, so that one can easily revert to normal prev/next in the whole sequence.

4. RSS for changesets

There are two kind of feeds for changesets.

• The one from the timeline, where you select the repository check-ins. You can set for how many days back this feed will generate events.
• The one from the revision log view of a given path. For this one, there's the 'limit' parameter, set to 100 by default.

5. RSS changeset feed → changeset view instead of browser view

In the trunk, the two RSS feeds mentionned above work as you suggest.

6. Edit ticket comment

See #454

[anonymous]

Thanks for the feedback.

I just modified my local templates for the RSS changeset feed →changeset issue, and introduced a hard limit to the RSS feeds (I upgraded to 0.8.4 while I was at it).

For limiting the RSS feed, what's the 'limit' parameter, and where do I set it?

For the next/prev ticket issue, it's not in 0.8.4 - when will the trunk see the light of day in a release?

For the custom query, the query.cs that came by default with 0.8.4 doesn't include the summary.

Thanks for the quick reply.

[Christian Boos]

Well, most of what I wrote applies to the devel version…

0.9 is still a few weeks ahead (should be reasonably stable and usable, though, and testing the bleeding edge is always appreciated anyway :) )