QA/Data harvesting/Progress Card: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 18: Line 18:


| <br>  
| <br>  
| <br>  
|  
| <br>
2010-08-27
 
<br>  
 
|  
Needs flags (graphs per release)
 
<br>  
 
|-
|-
|  
|  
Line 29: Line 37:
| <br>  
| <br>  
| <br>  
| <br>  
| <br>
|  
Can be done with current DW data
 
<br>  
 
|-
|-
|  
|  
Line 40: Line 52:
| <br>  
| <br>  
|  
|  
Can be done with current DW data
<br>
|-
|-
|  
|  
Line 49: Line 65:
| <br>  
| <br>  
| <br>  
| <br>  
| <br>
|  
Can be done with current DW data
 
<br>  
 
|-
|-
|  
|  
Line 59: Line 79:
| <br>  
| <br>  
| <br>  
| <br>  
| <br>
|  
Can be done with current DW data
 
<br>  
 
|-
|-
|  
|  
Line 68: Line 92:


| <br>  
| <br>  
| <br>  
|  
| <br>
2010-08-20
 
<br>  
 
|  
Needs flags
 
<br>  
 
|-
|-
|  
|  
Line 78: Line 110:


| <br>  
| <br>  
| <br>  
|  
| <br>
2010-08-27
 
<br>  
 
|  
Needs flags
 
''What data (everything listed in the other features?)''
 
|-
|-
|  
|  
Line 89: Line 129:
| <br>  
| <br>  
| <br>  
| <br>  
| <br>
|  
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<br>
Tabular reporting  


|  
|  
Line 98: Line 142:


| CURRENTLY AVAILABLE<br>  
| CURRENTLY AVAILABLE<br>  
| <br>
|  
NA<br>
 
<br>
 
|
The metrics dashboard should automatically deliver this with all dashboard items.
 
<br>
 
|-
|-
|  
|  
Line 108: Line 161:
| <br>  
| <br>  
| <br>  
| <br>  
| <br>
|  
Can be done with current DW data
 
<br>  
 
|-
|-
|  
|  
Rate/percentage of bugs&nbsp; being reopened/project<br>  
Rate/percentage of bugs being reopened/project<br>  


|  
|  
Line 118: Line 175:
| <br>  
| <br>  
| <br>  
| <br>  
| <br>
|  
Can be done with current DW data(?)
 
''how are projects identified (see above)''<br>  
 
|-
|-
|  
|  
Line 127: Line 188:


| <br>  
| <br>  
| <br>  
|  
| <br>
2010-09-04<br>
 
<br>
 
|  
Needs keywords and flags<br>
 
<br>
 
|-
|-
|  
|  
Line 137: Line 206:


| <br>  
| <br>  
| <br>  
|  
| <br>
<br>
 
<br>
 
|  
Can be done with current DW data<br>
 
|-
|-
|
|  
Options to-CSV/JSON/Save the graph as an image<br>  
Options to-CSV/JSON/Save the graph as an image<br>  


|
P3<br>  
P3<br>  


| CURRENTLY AVAILABLE<br>
| <br>  
| <br>  
| <br>  
|  
| <br>
If anything of this is buggy or difficult, it is probably best to file a metrics bug.<br>
 
<br>
 
|}
|}


<br>
<br>

Revision as of 23:31, 6 August 2010

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

If anything of this is buggy or difficult, it is probably best to file a metrics bug.