Improving the bug workflow

Registered by Simon Law on 2006-06-23

We'll try making each bug go through a process were the bug report first gets looked at by a large set a people that will make sure that the bug report contains all the necessary information. After that smaller set of people, the Bug Contact team, will look at the report to decide whether the bug report has enough information, and either prioritize the bug and mark it Triaged so that a developer can look at it, ir push it back to Incomplete for more information. As the final step, the developers will look at all the Triaged bug reports and mark the ones that need to be fixed as Todo, to put it in the developers' queue of bugs to fix.

The following statuses will be renamed:

Unconfirmed -> New

Needs Info -> Incomplete

Rejected -> Invalid

The following statuses will be added:

Triaged

Won't Fix

Todo

Only the Bug Contact will be able to set a bug to Triaged, only the Bug Contact or developers will be able to set it to Won't Fix, and only the developers will be able to set the bug status to the developer statuses; Todo, In Progress, Fix Committed and Fix Released

Blueprint information

Status:
Complete
Approver:
None
Priority:
High
Drafter:
Björn Tillenius
Direction:
Needs approval
Assignee:
Gavin Panella
Definition:
Approved
Series goal:
None
Implementation:
Implemented
Milestone target:
None
Started by
Björn Tillenius on 2007-06-06
Completed by
Joey Stanford on 2007-08-01

Related branches

Whiteboard

Some unresolved issues were added to the spec, but it should still be ready for review.

Everything except adding the Todo status is done.

(?)

Work Items