[%# 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 %] [% PROCESS "global/field-descs.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 [% terms.abug %].

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 %].
[% display_value("bug_status", "UNCONFIRMED") FILTER html %]
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 [% display_value("bug_status", "NEW") FILTER html %]. Or, it may be directly resolved and marked [% display_value("bug_status", "RESOLVED") FILTER html %].
[% display_value("bug_status", "NEW") FILTER html %]
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 [% display_value("bug_status", "ASSIGNED") FILTER html %], passed on to someone else, and remain [% display_value("bug_status", "NEW") FILTER html %], or resolved and marked [% display_value("bug_status", "RESOLVED") FILTER html %].
[% display_value("bug_status", "ASSIGNED") FILTER html %]
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 [% display_value("bug_status", "NEW") FILTER html %], or resolved and become [% display_value("bug_status", "RESOLVED") FILTER html %].
[% display_value("bug_status", "REOPENED") FILTER html %]
This [% terms.bug %] was once resolved, but the resolution was deemed incorrect. For example, a [% display_value("resolution", "WORKSFORME") FILTER html %] [% terms.bug %] is [% display_value("bug_status", "REOPENED") FILTER html %] when more information shows up and the [% terms.bug %] is now reproducible. From here [% terms.bugs %] are either marked [% display_value("bug_status", "ASSIGNED") FILTER html %] or [% display_value("bug_status", "RESOLVED") FILTER html %].
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.
[% display_value("bug_status", "RESOLVED") FILTER html %]
A resolution has been taken, and it is awaiting verification by QA. From here [% terms.bugs %] are either re-opened and become [% display_value("bug_status", "REOPENED") FILTER html %], are marked [% display_value("bug_status", "VERIFIED") FILTER html %], or are closed for good and marked [% display_value("bug_status", "CLOSED") FILTER html %].
[% display_value("bug_status", "VERIFIED") FILTER html %]
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 [% display_value("bug_status", "CLOSED") FILTER html %].
[% display_value("bug_status", "CLOSED") FILTER html %]
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 [% display_value("bug_status", "REOPENED") FILTER html %].
[% display_value("resolution", "FIXED") FILTER html %]
A fix for this [% terms.bug %] is checked into the tree and tested.
[% display_value("resolution", "INVALID") FILTER html %]
The problem described is not [% terms.abug %].
[% display_value("resolution", "WONTFIX") FILTER html %]
The problem described is [% terms.abug %] which will never be fixed.
[% display_value("resolution", "DUPLICATE") FILTER html %]
The problem is a duplicate of an existing [% terms.bug %]. Marking [% terms.abug %] duplicate requires the [% terms.bug %]# of the duplicating [% terms.bug %] and will at least put that [% terms.bug %] number in the description field.
[% display_value("resolution", "WORKSFORME") FILTER html %]
All attempts at reproducing this [% terms.bug %] were futile, and reading the code produces no clues as to why the described behavior would occur. If more information appears later, the [% terms.bug %] can be reopened.
[% display_value("resolution", "MOVED") FILTER html %]
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.

Importance

The importance of [% terms.abug %] is described as the combination of its priority and severity, as described below.

Priority

This field describes the importance and order in which [% terms.abug %] should be fixed compared to other [% terms.bugs %]. This field is utilized by the programmers/engineers to prioritize their work to be done.

Severity

This field describes the impact of [% terms.abug %].
Blocker Blocks development and/or testing work
Critical crashes, loss of data, severe memory leak
Major major loss of function
Normal regular issue, some loss of functionality under specific circumstances
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

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 [% display_value("bug_status", "NEW") FILTER html %] 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 [% display_value("bug_status", "NEW") FILTER html %], [%+ display_value("bug_status", "ASSIGNED") FILTER html %] and [% display_value("bug_status", "REOPENED") FILTER html %]. When searching for [% terms.bugs %] that have been resolved or verified, remember to set the status field appropriately.

[% IF Param("use_see_also") %]

See Also

This allows you to refer to [% terms.bugs %] in other installations. You can enter a URL to a [%+ terms.bug %] in the "Add [% terms.Bug %] URLs" field to note that that [% terms.bug %] is related to this one. You can enter multiple URLs at once by separating them with a comma.

You should normally use this field to refer to [% terms.bugs %] in other installations. For [% terms.bugs %] in this installation, it is better to use the "Depends On" and "Blocks" fields.

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