From Fedora Project Wiki
(Moving this away from my talk page.) |
No edit summary |
||
Line 1: | Line 1: | ||
We are working to create some basic metrics to report on the activities on the [[BugZappers]]. The current approach is to use the [https://fedorahosted.org/python-bugzilla/ python-bugzilla] package as much as possible. | |||
== Tools You Will Need== | == Tools You Will Need== | ||
* The [https://fedorahosted.org/python-bugzilla/ python-bugzilla] package. (Try 'yum install python-bugzilla' | * The [https://fedorahosted.org/python-bugzilla/ python-bugzilla] package. (Try 'yum install python-bugzilla' | ||
* [http://therabers.com/fedora/python-bugzilla/bzilla The modified bugzilla CLI] to add the --summary option. I suggest saving this as ~/bin/bzilla (only because that is what I have done) | * [http://therabers.com/fedora/python-bugzilla/bzilla 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 == | == Proposed Metrics == | ||
Line 15: | Line 15: | ||
|# 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 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 | |# 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: [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] | |# of 'Triaged' bugs CLOSED in last xx Days || DONE || See: [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] | ||
Line 23: | Line 23: | ||
|# 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') | |# 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 || | |<del>List of 'Triaged' bugs currently marked as NEEDINFO</del> || CANCELED || <del>This should generally be an empty list. Bugs showing up here could be an indicator of poor Triaging. See: [https://bugzilla.redhat.com/buglist.cgi?type0-1-0=allwords&field0-1-0=flagtypes.name&field0-0-0=flagtypes.name&classification=Fedora&query_format=advanced&value0-1-0=Triaged&bug_status=NEW&bug_status=ASSIGNED&bug_status=MODIFIED&bug_status=ON_DEV&type0-0-0=allwords&value0-0-0=NEEDINFO&product=Fedora] (Is this useful. Remove?)</del> This was discussed and determined to be of no value as a metric. | ||
|- | |- | ||
|# of bugs CLOSED by BugZappers in last xx days || | |<del># of bugs CLOSED by BugZappers in last xx days</del> || CANCELED || <del>Need a list of BugZappers</del> 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|| | |<del># of bugs CLOSED by BugZappers in last xx days by BugZapper</del>|| CANCELED ||<del>Need a list of BugZappers</del>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 Resolution|| | |<del># of bugs CLOSED by BugZappers in last xx days by Resolution</del>|| CANCELED ||<del>Need a list of BugZappers</del>This is no longer necessary as Triagers should be marking bugs as 'Triaged' when CLOSING them. | ||
|} | |} | ||
Latest revision as of 14:47, 27 July 2010
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') |
CANCELED | ||
CANCELED | ||
CANCELED | ||
CANCELED |
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?