User talk:Jraber

From FedoraProject

Revision as of 19:02, 21 June 2010 by Jraber (Talk | contribs)

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

I am currently working to create some basic metrics to report on the activities on the BugZappers. My current approach employs the python-bugzilla package and a few basic Bugzilla queries.

Proposed Metrics

  • # of Bugs 'Triaged' in the last xx days - See: [1]
  • # of Bugs 'Triaged' in the last xx days by Current Status - Slightly modified bugzilla-python can create this report.
  • # of Bugs 'Triaged' in the last xx days by Triager - Requires modification to bugzilla-python to enable gathering of 'history' data from bugzilla via XMLRPC. (The ability to get History data via XMLRPC was intrduced in BugZilla 3.4 and is marked as EXPERIMENTAL.)
  • # of 'Triaged' bugs CLOSED in last xx Days
  • # of 'Triaged' bugs CLOSED in last xx Days by Resolution
  • # of 'Triaged' bugs CLOSED in last xx Days by # of days since Triaged flag was set - To know if/how 'Triaging' is impacting the life expectancy of bugs.
  • List of 'Triaged' bugs currently marked as NEEDINFO - This should generally be an empty list. Bugs being listed here could indicate poor Triaging. See: [2] (**NEED TO TEST THIS**)
  • # of bugs CLOSED by BugZappers in last xx days
  • # of bugs CLOSED by BugZappers in last xx days by BugZapper
  • # of bugs CLOSED by BugZappers in last xx days by Resolution

My Thoughts/Questions

  • Who are the BugZappers? Where is the list of members of the BugZappers? Proposed alternative is: BugZappers = BugZilla users that have made use of the 'Trigaed' flag in the previous xx days.
  • Eventually, these metrics should probably come from a SQL query. Pulling all this data via XMLRPC will be slow.
  • Pretty graphs could be created showing how these metrics change (or don't) over time.
  • What other great data points could we be tracking?