Our use of trac doesn't lead to optimal use:
3) the severity/priority fields are not used consistently 4) there's a lack of fields stating - a) how much effort would be required b) what else would be impacted c) whether people would be willing to sponsor financially d) the type of bug (e.g. ui) 5) the fields that are there have no definition, like at what point does something become 'critical' 6) there is also the need for an impacts mechanism, like "impacts: UI, Security"
I asked on #trac:
(08:40:48) MartinCleaver: can the fields in trac be customised without coding, e.g. where it says "Type: Priority: Milestone: ", I want an Impacts: (checkboxes) UI, Security
(08:41:02) MartinCleaver: added to the existing set
(08:41:16) alect: yes, it's in the manual
(08:42:45) MartinCleaver: ok, thanks alect
If there are key people close to the development project core, can they be given at least some control over the development process?
In TWiki this is the TWikiCommunityGroup - they have elevated privileges over newcomers, including changes to the bug tracking frameworks and access to submit to SVN.