Talk:BugZappers/Metrics

From FedoraProject

< Talk:BugZappers
Revision as of 14:47, 27 July 2010 by Jraber (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

We are working to create some basic metrics to report on the activities on the BugZappers. The current approach is to use the python-bugzilla package as much as possible.

Tools You Will Need

  • The python-bugzilla package. (Try 'yum install python-bugzilla'
  • The modified bugzilla CLI to add the --summary option. I (jraber) suggest saving this as ~/bin/bzilla (only because that is what I have done)

Proposed Metrics

Description Status Comments/Notes/Reference
# of Bugs 'Triaged' in the last xx days DONE See: [1]
# of Bugs 'Triaged' in the last xx days by Current Status DONE bzilla query --from-url='https://bugzilla.redhat.com/buglist.cgi?chfieldto=Now&query_format=advanced&chfield=keywords&chfieldfrom=-90d&chfieldvalue=Triaged&classification=Fedora&product=Fedora' --summary bug_status
# of Bugs 'Triaged' in the last xx days by Component DONE bzilla query --from-url='https://bugzilla.redhat.com/buglist.cgi?chfieldto=Now&query_format=advanced&chfield=keywords&chfieldfrom=-90d&chfieldvalue=Triaged&classification=Fedora&product=Fedora' --summary component
# of Bugs 'Triaged' in the last xx days by Triager In Process I am working on a patch to add the ability to query/display the bug history data via XMLRPC to the python-bugzilla package. This metric will provide the list of active BugZappers.
# of 'Triaged' bugs CLOSED in last xx Days DONE See: [2]
# of 'Triaged' bugs CLOSED in last xx Days by Resolution DONE bzilla query --from-url='https://bugzilla.redhat.com/buglist.cgi?keywords=Triaged&chfieldto=Now&query_format=advanced&chfield=bug_status&keywords_type=allwords&chfieldfrom=-90d&chfieldvalue=CLOSED&bug_status=CLOSED&classification=Fedora&product=Fedora' --summary resolution
# of 'Triaged' bugs CLOSED in last xx Days by # of days since Triaged flag was set PENDING To know if/how 'Triaging' is impacting the life expectancy of bugs. (Need a better definition. How about 'Average number of days from Triaged to CLOSED by resolution for 'Triaged' bugs CLOSED in last xx days')
List of 'Triaged' bugs currently marked as NEEDINFO CANCELED This should generally be an empty list. Bugs showing up here could be an indicator of poor Triaging. See: [3] (Is this useful. Remove?) This was discussed and determined to be of no value as a metric.
# of bugs CLOSED by BugZappers in last xx days CANCELED Need a list of BugZappers This is no longer necessary as Triagers should be marking bugs as 'Triaged' when CLOSING them.
# of bugs CLOSED by BugZappers in last xx days by BugZapper CANCELED Need a list of BugZappersThis is no longer necessary as Triagers should be marking bugs as 'Triaged' when CLOSING them.
# of bugs CLOSED by BugZappers in last xx days by Resolution CANCELED Need a list of BugZappersThis is no longer necessary as Triagers should be marking bugs as 'Triaged' when CLOSING them.

Additional Thoughts/Questions

  • Q:Who are the BugZappers? A:BugZappers = Members of he Triagers group in FAS. But since this is not easy to scrape (and may included inactive persons) I am going to use the following definition. BugZappers = BugZilla users that have used the 'Triaged' flag in the previous 90 days.
  • Eventually, these metrics should probably come from a SQL query. Pulling all this data via XMLRPC could be slow.
  • Pretty graphs could be created showing how these metrics change (or don't) over time.
  • What other metrics should we be tracking?
  • Should these metric be limited to bugs where Product=Fedora & Classification=Fedora?