While I don't have any input on ticket dependencies, I'd like to offer this bit about user interface. My experience using Bugzilla and even Trac is that when I want to link one ticket to another (in Trac I can just do that in the discussion area for the absence of a better way), it's a very inconvenient process. I have to open another tab in the browser, find the related ticket's number, then go back to the original tab (and I may have 5-15 already open if I'm in the middle of something). To facilitate it, Roundup for example presents a list of all tickets to choose from. However, I don't think it's a "usable" UI decision because even small projects may have hundreds and thousands of tickets, with a large percentage of those open. A better UI would somehow limit choices in such a list to a manageable number, say 10-20 most suitable tickets. A "short list" may be constrained by a search word (harder to do nicely without AJAX stuff) or by similarity. For example, picking 10 tickets that have the same words as this ticket in their summary would be a first approximation. So, if I want to find a parent ticket for something called "Workflow incorrectly closes tickets," Trac behind the scenes would do a query for these words, find tickets that have words "workflow" or "close" in their summary, and present ten most suitable ones. I don't know if this is an original idea or it's implemented somewhere already, but I think it would work with Trac's "minimalistic but insanely convenient" philosophy (if I may characterize it like that). Thank you,
Sergey. _______________________________________________ Trac-dev mailing list [email protected] http://lists.edgewall.com/mailman/listinfo/trac-dev
