[Python-Dev] New bugtracker project
Tue, 21 May 2002 16:55:10 -0700
My list of requirements isn't so much a list of reqs as a list of
features from bugzilla that we've found exceedingly useful.
0) keywords -- massively useful for targeting, filtering, etc.
1) Attachments on bugs (somewhat of a merge of the patch tracker and
bug tracker, but also useful for attaching test cases, screenshots, etc.)
2) Being able to "watch" people - be notified when their bugs have
events happen to them, e.g.. when they're on vacation.
3) Saving and recalling searches
4) non-web, non-email access to the database (e.g. take all the bugs
assigned to so and so, and take those submitted by people in england,
and set the keyword "never" to them).
5) scalability (in # of developers, # of users, # of bugs, # of
'versions', # of 'products', etc.)
6) Being able to migrate a bug from one product to another (not all that
relevant for a Python-only bug tracker, except if the versions are
handled as different products).
7) Bug linkages (depends on/blocks, duplicate handling, etc.)
Useful things we've added to bugzilla include:
1) Ability to designate bugs as 'for internal use only' (not especially
important for python-dev =)
2) an 'efficient' UI. The bugzilla default search results pages are
very inefficient from a UI point of view. Andy McKay's version is much
better, I think.
As I've mentioned in the past, we used an earlier version of roundup and
found it didn't scale well with thousands of users. I haven't look at
the new roundup to know if it's dealt with the problems we had (way too
much mail generation by default, much too brittle, and poorly
It's also important to have flexibility in handling the bug cycle (who
closes, who verifies, etc.). Both roundup and bugzilla did that pretty