Many open source projects use Bugzilla to manage their bug killing efforts.
I suspect that not all projects that use Bugzilla use the same status progression.
In an effort to test that hypothesis, I am starting to collect some of the progressions as I run across them, see the
Status Progression Table.
See:
Contents
Notes
Status Progression Table
This table shows how various projects label the status of bugs as they progress towards resolution:
| |
Bugzilla Status |
| Condition |
AbiWord |
Next Project |
| Initial bug report |
UNCONFIRMED |
|
| Confirmed by someone else |
NEW |
|
| Developer accepts bug |
ASSIGNED |
|
| Solved and pending verification |
RESOLVED |
|
| Solution verified |
VERIFIED |
|
| Bug report rejected |
CLOSED1 |
|
Notes:
1. From
AbiWord
: The status "CLOSED" is reserved for use by core developers to describe a bug that, for whatever reason, does not belong in Bugzilla.
Aside: I'm not sure the AbiWord progression is the most intuitively obvious progression. On the other hand, if most projects that use Bugzilla (or similar tools) follow a similar progression, I guess we might as well standardize on it.
Contributors
- () RandyKramer - 27 Apr 2003
- If you edit this page: add your name here; move this to the next line; and if you've used a comment marker (your initials in parenthesis), include it before your WikiName.
Page Ratings