Bugzilla fields
Take a look at the diagram: Diagram_triagers.png
Bug Status |
The status field indicates the general status of a bug- i.e., where is it in the lifecycle of a bug? |
UNCONFIRMED |
This bug has recently been added to the database. Nobody has validated that this bug is true. Users who have obtained permissions from the bugsquad may confirm this bug, changing its state to NEW. It may also be directly resolved and marked RESOLVED, or more information may be necessary, moving it to NEEDINFO. |
NEW |
This bug has recently been added to the assignee's list of bugs and must be processed. 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 bug is not yet resolved, but is assigned to the proper person. From here bugs can be given to another person and become NEW, or resolved and become RESOLVED. |
NEEDINFO |
More information from the reporter is needed to proceed further in fixing this bug. This should not be used when someone needs more information from a developer- a NEW or ASSIGNED bug implicitly needs more information from the developer. |
RESOLVED |
The bug has been resolved in some way. The resolution field should contain a secondary status describing the way in which it was resolved. See the Resolutions section for more details. |
VERIFIED and CLOSED |
GNOME does not substantially use VERIFIED or CLOSED. When used, they indicate that a third party has checked to see that a bug was properly resolved. |
Resolutions |
Once a bug is RESOLVED, the 'resolution' field indicates in what way the bug was resolved. |
FIXED |
A fix for this bug is checked into the tree and tested. |
INCOMPLETE |
The bug lacks sufficient information to be fixed, and unlike NEEDINFO, no answer is possible or expected. |
OBSOLETE |
This bug is in an old (obsolete) or unmaintained version. This includes GNOME 1.x. |
NOTABUG |
The problem described is not actually a bug, but a design choice of some sort. |
NOTGNOME |
The bug is either not in a module that is part of GNOME, or is caused by something outside of GNOME that cannot be worked around or otherwise resolved by the GNOME application. |
INVALID |
This bug is in some way not valid- usually used when INCOMPLETE or NOTABUG just don't quite fit. |
WONTFIX |
The problem described is a bug which will never be fixed. |
Severity |
This field describes the impact of a bug on a user |
Blocker |
Blocks development and/or testing work |
Critical |
Crashes, causes loss of data, or is a severe memory leak. |
Major |
Major loss of functionality- menu item broken, data output extremely incorrect, or otherwise difficult/useless to use. |
Normal |
A minor part of the component is nonfunctional or broken. |
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 a new feature or functionality. |
Priority |
This field describes the importance and order in which a bug should be fixed. This field is utilized by hackers to prioritize their work to be done. While each term has a description, it it important to note that priority is highly subjective, and bugs can move up or down the priority scale based on subjective questions like 'would we be embarassed to release the software with this bug.' |
Immediate |
This bug blocks development or testing work and should be fixed ASAP, or is a security issue in a released version of the software. |
Urgent |
This bug blocks usability of a large portion of the product, and really should be fixed before the next planned release. |
High |
Seriously broken, but not as high impact. Should be fixed before next major release. Frequently includes cosmetic bugs of particularly high visibility, regressions from functionality provided in previous releases, and more minor bugs that are frequently reported. |
Normal |
Either a fairly straightforward workaround exists or the functionality is not very important and/or not frequently used. |
Low |
Just not all that important. Rarely used in GNOME. |
Target Milestone |
This field describes the version of the product that developers or the maintainers believe they should fix the bug by. This field is not meant for use by general users, the bugsquad, or the release team. It is reserved for developers and maintainers of the given module. |
Gnome Version |
This field describes the version of GNOME that a bug has most recently been found in. This field is used by the GNOME release team and other interested parties to find all bugs in a specific version of GNOME, no matter what program the bug is in. For example, one query can find all GNOME 2.8 bugs, whether they are in Metacity 2.91, totem 0.99, or nautilus 2.8. |
Unspecified |
This bug is in a module that is not in GNOME, or in an unspecified version of GNOME. |
Unversioned Enhancement |
This bug is an enhancement,and hence can be implemented at any point. |
2.(odd)/2.(even) |
This bug is in the odd/even-numbered series which culminates in GNOME 2.even. |
Gnome Target Milestone |
This field describes the version of GNOME that a bug should be fixed in. This is not a 'it would be nice' field, it is a 'Gnome releases may need to be delayed for this issue' field. It is intended for use by senior-ish bug triagers and the release team. We allow others to nominate 'showstopper' bugs by setting this field, but bugsquadders and release team members review such bugs and unmark ones where the change is not warranted. |
Operating System |
This field lists the operating system the bug was found on. We know a lot of these are useless, bear with us. :) |