[%# 1.0@bugzilla.org %] [%# The contents of this file are subject to the Mozilla Public # License Version 1.1 (the "License"); you may not use this file # except in compliance with the License. You may obtain a copy of # the License at http://www.mozilla.org/MPL/ # # Software distributed under the License is distributed on an "AS # IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or # implied. See the License for the specific language governing # rights and limitations under the License. # # The Original Code is the Bugzilla Bug Tracking System. # # The Initial Developer of the Original Code is Netscape Communications # Corporation. Portions created by Netscape are # Copyright (C) 1998 Netscape Communications Corporation. All # Rights Reserved. # # Contributor(s): Terry Weissman # Gervase Markham #%] [% PROCESS global/variables.none.tmpl %] [% INCLUDE global/header.html.tmpl title = "A $terms.Bug's Life Cycle" %]

The status and resolution fields define and track the life cycle of a [% terms.bug %].

STATUS

RESOLUTION

The status field indicates the general health of a [% terms.bug %]. Only certain status transitions are allowed. The resolution field indicates what happened to this [% terms.bug %].
UNCONFIRMED
This [% terms.bug %] has recently been added to the database. Nobody has validated that this [% terms.bug %] is true. Users who have the "canconfirm" permission set may confirm this [% terms.bug %], changing its state to NEW. Or, it may be directly resolved and marked RESOLVED.
NEW
This [% terms.bug %] has recently been added to the assignee's list of [% terms.bugs %] and must be processed. [% terms.Bugs %] in this state may be accepted, and become ASSIGNED, passed on to someone else, and remain NEW, or resolved and marked RESOLVED.
ASSIGNED
This [% terms.bug %] is not yet resolved, but is assigned to the proper person. From here [% terms.bugs %] can be given to another person and become NEW, or resolved and become RESOLVED.
REOPENED
This [% terms.bug %] was once resolved, but the resolution was deemed incorrect. For example, a WORKSFORME [% terms.bug %] is REOPENED when more information shows up and the [% terms.bug %] is now reproducible. From here [% terms.bugs %] are either marked ASSIGNED or RESOLVED.
No resolution yet. All [% terms.bugs %] which are in one of these "open" states have the resolution set to blank. All other [% terms.bugs %] will be marked with one of the following resolutions.
RESOLVED
A resolution has been taken, and it is awaiting verification by QA. From here [% terms.bugs %] are either re-opened and become REOPENED, are marked VERIFIED, or are closed for good and marked CLOSED.
VERIFIED
QA has looked at the [% terms.bug %] and the resolution and agrees that the appropriate resolution has been taken. [% terms.Bugs %] remain in this state until the product they were reported against actually ships, at which point they become CLOSED.
CLOSED
The [% terms.bug %] is considered dead, the resolution is correct. Any zombie [% terms.bugs %] who choose to walk the earth again must do so by becoming REOPENED.
FIXED
A fix for this [% terms.bug %] is checked into the tree and tested.
INVALID
The problem described is not a [% terms.bug %]
WONTFIX
The problem described is a [% terms.bug %] which will never be fixed.
DUPLICATE
The problem is a duplicate of an existing [% terms.bug %]. Marking a [% terms.bug %] duplicate requires the [% terms.bug %]# of the duplicating [% terms.bug %] and will at least put that [% terms.bug %] number in the description field.
WORKSFORME
All attempts at reproducing this [% terms.bug %] were futile, reading the code produces no clues as to why this behavior would occur. If more information appears later, please re-assign the [% terms.bug %], for now, file it.
MOVED
The problem was specific to a related product whose [% terms.bugs %] are tracked in another [% terms.bug %] database. The [% terms.bug %] has been moved to that database.

Severity

This field describes the impact of a [% terms.bug %].
Blocker Blocks development and/or testing work
Critical crashes, loss of data, severe memory leak
Major major loss of function
Minor minor loss of function, or other problem where easy workaround is present
Trivial cosmetic problem like misspelled words or misaligned text
Enhancement Request for enhancement

Priority

This field describes the importance and order in which a [% terms.bug %] should be fixed. This field is utilized by the programmers/engineers to prioritize their work to be done. The available priorities range from P1 (most important) to P5 (least important.)

Platform

This is the hardware platform against which the [% terms.bug %] was reported. Legal platforms include: Note: When searching, selecting the option "All" does not select [% terms.bugs %] assigned against any platform. It merely selects [% terms.bugs %] that are marked as occurring on all platforms, i.e. are designated "All".

Operating System

This is the operating system against which the [% terms.bug %] was reported. Legal operating systems include: Sometimes the operating system implies the platform, but not always. For example, Linux can run on PC and Macintosh and others.

Assigned To

This is the person in charge of resolving the [% terms.bug %]. Every time this field changes, the status changes to NEW to make it easy to see which new [% terms.bugs %] have appeared on a person's list.

The default status for queries is set to NEW, ASSIGNED and REOPENED. When searching for [% terms.bugs %] that have been resolved or verified, remember to set the status field appropriately.

[% INCLUDE global/footer.html.tmpl %]