sort report by issue type rather than bug number
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bug Helper |
Confirmed
|
Medium
|
Unassigned | ||
bughelper (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Another Mozillateam request.
I guess you can tell that we are using and abusing bughelper quite a bit.
Currently I create the following report for our triagers so they can easily find bug they can triage.
https:/
The report would be easier to use if it were structured like:
I. List of bugs that need initial contact
... <list>
II. List of bugs that need a crash report
III. List of bugs that need a retrace
... (e.g. for tags)
IX. all bugs that might be ready for transition them to next state
XI. List of bugs that have an inconsitent state and need to be recategorized
XII. Pairs of bugs that might be duplicates of current hot issues.
XII. a) Hot Issue A (e.g. totem destructor crashers)
...
b) Hot Issue B (e.g. gtk_restyle crashers)
thanks
David Farning
On Mon, 2007-02-26 at 19:42 +0000, David Farning wrote:
> Currently I create the following report for our triagers so they can
> easily find bug they can triage.
>
David, with the risk of being plainly abusive... could you send me the
bughelper info file you are using for this? I would like to adapt it for
other packages.
Thanks,
..hggdh..