UsefulBugMetrics

Differences between revisions 1 and 2
Revision 1 as of 2008-05-30 11:10:44
Size: 2057
Editor: cpc1-oxfd8-0-0-cust993
Comment:
Revision 2 as of 2008-06-02 17:52:03
Size: 3387
Editor: c-24-21-234-111
Comment: Added rationale
Deletions are marked like this. Additions are marked like this.
Line 16: Line 16:

The bug tracking system of Launchpad has been expanded to record new date information regarding bug tasks. The information currently being recored includes the following:

 * date-created (the date the bug task was created)
 * date-left-new (the date the bug task's status was first changed)
 * date-incomplete (the date the bug task's status was last set to Incomplete)
 * date-confirmed (the date the bug task's status was last set to Confirmed)
 * date-triaged (the date the bug task's status was last set to Triaged)
 * date-inprogress (the date the bug task's status was last set to In Progress)
 * date-fixcommitted (the date the bug task's status was last set to Fix Committed)
 * date-fixreleased (the date the bug task's status was last set to Fix Released)
 * date-closed (the date the bug task's status was set to a end status)
 * date-assigned (the last date the bug was assigned to someone)

Currently, this information is only available via the +text interface for a bug report. Additionally, this information is not particularly useful by itself. Rather, these dates becoming more useful when considering the difference between any two dates and over a package as a whole. Subsequently, a new tool should be developed to find the differences and aggegrate the information for packages or teams.

Summary

Identify bug statistics that will be useful to the Ubuntu team during the cycle to drive quality improvements and assist during release periods.

Release Note

Rationale

The bug tracking system of Launchpad has been expanded to record new date information regarding bug tasks. The information currently being recored includes the following:

  • date-created (the date the bug task was created)
  • date-left-new (the date the bug task's status was first changed)
  • date-incomplete (the date the bug task's status was last set to Incomplete)
  • date-confirmed (the date the bug task's status was last set to Confirmed)
  • date-triaged (the date the bug task's status was last set to Triaged)
  • date-inprogress (the date the bug task's status was last set to In Progress)
  • date-fixcommitted (the date the bug task's status was last set to Fix Committed)
  • date-fixreleased (the date the bug task's status was last set to Fix Released)
  • date-closed (the date the bug task's status was set to a end status)
  • date-assigned (the last date the bug was assigned to someone)

Currently, this information is only available via the +text interface for a bug report. Additionally, this information is not particularly useful by itself. Rather, these dates becoming more useful when considering the difference between any two dates and over a package as a whole. Subsequently, a new tool should be developed to find the differences and aggegrate the information for packages or teams.

Use Cases

Assumptions

Design

Implementation

UI Changes

Code Changes

Test/Demo Plan

Outstanding Issues

BoF agenda and discussion


CategorySpec

QATeam/Specs/UsefulBugMetrics (last edited 2008-08-06 16:36:14 by localhost)