QA/Data harvesting/Progress Card
Progress Card
Feature | Prio | Status | Estimated Date of Completion | Additional Comments |
Find/fixed Rate-trend Graphs |
P1 |
2010-08-27
|
Needs flags (graphs per release)
| |
Buckets:grouped by priority |
P1 |
Can be done with current DW data
| ||
Buckets:grouped by severity |
P1 |
Can be done with current DW data
| ||
Buckets:grouped by component |
P1 |
Can be done with current DW data
| ||
Buckets:grouped by bug-asignee |
P3 |
Can be done with current DW data
| ||
Buckets:grouped by flags |
P1 |
2010-08-20
|
Needs flags
| |
Ability to compare data from different releases |
P1 |
2010-08-27
|
Needs flags What data (everything listed in the other features?) | |
Ability to compare data from different projects |
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?) | ||
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 |
P1 |
Can be done with current DW data
| ||
Rate/percentage of bugs being reopened/project |
P2 |
Can be done with current DW data (?) how are projects identified (see above) | ||
Regression bugs per release/project |
P1 |
2010-09-04
|
Needs keywords and flags
| |
Average age of bugs in unconfirmed status |
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.
|