sort report by issue type rather than bug number

[David Farning]

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://wiki.ubuntu.com/MozillaTeam/Bugs/Bughelper/Results

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

[C de-Avillez (hggdh2)]

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..

[David Farning (dfarning)]

I have attached the necessary files. I put the .info in the info directory and the bughelper-mt in the bughelper.main dir.

Please be warned you will need about 10G of cache space to run the script as is;(

[Pappan (ppadman)]

David,

By I. List of bugs that need initial contact, did you mean bugs that had
been reported but not looked at by anyone ? If yes, we can obtain it in a
form like this:

bugnumbers --count -p firefox | grep "Comments: 0"

I agree that bugnumbers does not have a option or its output with respect to
the count is not sorted.

Hope this may be useful.

Pappan

On 2/27/07, David Farning <email address hidden> wrote:
>
> Public bug reported:
>
> 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://wiki.ubuntu.com/MozillaTeam/Bugs/Bughelper/Results
>
>
> 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
>
> ** Affects: bughelper (Ubuntu)
> Importance: Undecided
> Status: Unconfirmed
>
> --
> sort report by issue type rather than bug number
> https://launchpad.net/bugs/88102
>
> --
> Bughelper mailing list
> <email address hidden>
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/bughelper
>

[David Farning (dfarning)]

Sorry for the confusion.

Currently in bughelper.main, as each issue is pulled from LP, if a clue is triggered print_bug is called. This does not allow for sorting.

I would like to request that instead of calling print_bug, the (bugnumber, info string) tuples are stored in a data structure so that they can be sorted by info string to make a more organized result.

This is probably not an issues for most packages. For the 700+ bug the mozilla team has open, it would be rather helpful.

thanks
David

[Daniel Holbach (dholbach)]

Can you commit your info files to the bughelper-data branch? https://wiki.ubuntu.com/BugHelper/doc/writing-clue-files - please don't maintain them separately.

Apart from that: valid request.

[David Farning (dfarning)]

Daniel,

I will commit them. I was a bit hesitant to start committing my test stuff prematurely. I was hoping that someone on the Mozillateam who can actually code would pick them up before committing them;)

Additionally, because of all the handshaking, the scripts hammer the LP server pretty badly.

You Guys Rock

thanks
David Farning

[Daniel Holbach (dholbach)]

This will be somehow addressed by the reports that a server running a certain cronjob will output.