QA/Data harvesting/Progress Card: Difference between revisions
Line 8: | Line 8: | ||
| style="background: none repeat scroll 0% 0% rgb(239, 239, 239); width: 5%;" | '''Prio''' | | style="background: none repeat scroll 0% 0% rgb(239, 239, 239); width: 5%;" | '''Prio''' | ||
| style="background: none repeat scroll 0% 0% rgb(239, 239, 239); width: 10%;" | '''Status''' | | style="background: none repeat scroll 0% 0% rgb(239, 239, 239); width: 10%;" | '''Status''' | ||
| style="background: none repeat scroll 0% 0% rgb(239, 239, 239); width: | | style="background: none repeat scroll 0% 0% rgb(239, 239, 239); width: 10%;" | '''Estimated Date of Completion''' | ||
| style="background: none repeat scroll 0% 0% rgb(239, 239, 239); width: | | style="background: none repeat scroll 0% 0% rgb(239, 239, 239); width: 20%;" | '''Owner'''<br> | ||
| style="background: none repeat scroll 0% 0% rgb(239, 239, 239); width: | | style="background: none repeat scroll 0% 0% rgb(239, 239, 239); width: 30%;" | '''Additional Comments''' | ||
|- | |- | ||
| | | | ||
Line 89: | Line 89: | ||
* Same, but only the 10 components with the most bugs: [http://cm-metricsetl05.mozilla.org:8983/solr/select/?q=expiration_date:%5BNOW+TO+*%5D%20major_status:OPEN%20%28product:Firefox%20OR%20product:Core%29&facet=true&facet.field=component&facet.limit=10&rows=0] | * Same, but only the 10 components with the most bugs: [http://cm-metricsetl05.mozilla.org:8983/solr/select/?q=expiration_date:%5BNOW+TO+*%5D%20major_status:OPEN%20%28product:Firefox%20OR%20product:Core%29&facet=true&facet.field=component&facet.limit=10&rows=0] | ||
* Ideally we want to support faceting by combination of component x status so we can have nice bar charts with multiple colors per column (one column per component, one segment/color per status). This is not currently in SOLR, but there is a patch ([https://issues.apache.org/jira/browse/SOLR-792]) that we could use. Can also be done currently with one SOLR query per status. | |||
<br> | <br> |
Revision as of 18:13, 31 August 2010
Progress Card
Feature | Prio | Status | Estimated Date of Completion | Owner |
Additional Comments |
Find/fixed Rate-trend Graphs Sample metrics types here |
P1 |
2010-08-27
|
Michael Kurze |
This will need flags to allow for better selection of releases. Also, DWH data is incomplete (only bugs #560K to about #585K are included).
| |
Buckets:grouped by priority Samples from bugzilla here. |
P1 |
| |||
Buckets:grouped by severity |
P1 |
| |||
Buckets:grouped by component Sample from bugzilla here |
P1 |
| |||
Buckets:grouped by bug-asignee Sample metrics types here |
P3 |
Can be done with current DW data
| |||
Buckets:grouped by flags Sample metrics types here |
P1 |
2010-08-20
|
Michael Kurze |
Needs flags | |
Ability to compare data from different releases Sample from bugzilla here
|
P1 |
2010-08-27
|
Michael Kurze |
Needs flags
What data (everything listed in the other features?) Answer: Ideally,we should be able to trim the data we want to compare based on target milestone,component,keywords,flags etc | |
Ability to compare data from different projects Sample from bugzilla here |
P2 |
Can be done with current DW data (?) is Product/Component sufficient for this? Please add other fields that can indicate a project (flags? keywords?) Answer: Ideally,we should be able to trim the data we want to compare based on target milestone,component,keywords,flags etc | |||
Tabular reporting |
P3 |
CURRENTLY AVAILABLE
|
NA
|
The metrics dashboard should automatically deliver this with all dashboard items.
| |
Average age of a bug in each component Sample metric types here |
P1 |
Can be done with current DW data
| |||
Rate/percentage of bugs being reopened/project Sample metric types here |
P2 |
Can be done with current DW data (?) how are projects identified (see above) | |||
Regression bugs per release/project Samples from bugzilla here |
P1 |
2010-09-04
|
Michael Kurze |
Needs keywords and flags
| |
Average age of bugs in unconfirmed status Sample metrics types here |
P1 |
|
Can be done with current DW data | ||
Options to-CSV/JSON/Save the graph as an image |
P3 |
CURRENTLY AVAILABLE
|
NA
|
If anything of this is buggy or difficult, it is probably best to file a metrics bug.
|