Update: this is sadly not as easy technically as it should be (e.g. Bugzilla 3.6 has several hard-coded status names lurking in the code). This is definitely not happening on Tuesday, and may have to wait until we upgrade to 4.0. <sigh>.
Next Tuesday, 9th November When we upgrade to Bugzilla 4.0, the values of the Status field in bugzilla.mozilla.org are changing, as discussed in mozilla.dev.planning. This is to match us up with upstream changes, make it more clear what each state means, and to clarify which bugs are the responsibility of QA and which of Dev.
The changes are as follows:
- NEW will be rename to CONFIRMED, so all existing bugs change
- ASSIGNED will be renamed to IN_PROGRESS, ditto
- READY_TO_FIX is a new state (see below)
- REOPENED will be removed (reopened bugs go straight to CONFIRMED or IN_PROGRESS)
So the Statuses and their meanings will be as follows:
|UNCONFIRMED||not confirmed; filed by inexperienced reporter||QA|
|CONFIRMED||can reproduce, not an obvious dupe||QA|
|READY_TO_FIX||has appropriate QA/UX work complete, ready for a developer||Dev|
|IN_PROGRESS||developer is working on a patch||Dev|
|RESOLVED||patch has been committed to trunk||QA|
|VERIFIED||fix has been QAed in builds||n/a|