Bugzilla Help and Glossary

This form will allow you to call up a subset of the bug list. You should be able to add the URL of the resulting list to your bookmark file in order to preserve queries.

The way the query works, if you have nothing checked in a box, then all values for that field are legal, for example if you checked nothing in any of the boxes, you would get the entire bug list.

The default value of this form should correspond roughly to a "personal" bug list.

There is a hacky way to do some searches that aren't supported by the form. The buglist script will build queries based on the URL, so you can add other criteria.

For example, if you wanted to see all bugs reported against the X platform and assigned to jwz, you could ask for all bugs assign to jwz, then edit the URL in the "Location" box, adding the clause"&rep_platform=X-Windows" to the URL.

Here is a list of someof the field names you could use for additional unsupported searches...
version	reporter area
rep_platform	bug_file_loc
op_sys	short_desc

Definitions

The status and resolutionfield define and track the life cycle of a bug.

Status	Resolution
The status field indicates the general health of a bug. Only certain status transitions are allowed.	The resolution field indicates what happened to this bug.
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. REOPENED This bug was once resolved, but the resolution was deemed incorrect. For example, a WORKSFORME bug is REOPENED when more information shows up and the bug is now reproducible. From here bugs are either marked ASSIGNED or RESOLVED.	No resolution yet. All bugs which are NEW or ASSIGNED have the resolution set to blank. All other 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 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 bug and the resolution and agrees that the appropriate resolution has been taken. Bugs remain in this state until the product they were reported against actually ship, at which point the become CLOSED. CLOSED The bug is considered dead, the resolution is correct. Any zombie bugs who choose to walk the earth again must do so by becoming REOPENED.	FIXED A fix for this bug is checked into the tree and tested. INVALID The problem described is not a bug WONTFIX The problem described is a bug which will never be fixed. LATER The problem described is a bug which will not be fixed in this version of the product. REMIND The problem described is a bug which will probably not be fixed in this version of the product, but might still be. DUPLICATE The problem is a duplicate of an existing bug. Marking a bug duplicate requires the bug# of the duplicating bug and will at least put that bug number in the description field. WORKSFORME All attempts at reproducing this 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 bug, for now, file it.

Other Fields

Severity

This field describes the impact of a 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 problemwhere easy workaround is present
Trivial cosmetic problem like misspelt words ormisaligned text
Enhancement Request for enhancement

This field describes theimportance and order in which a bug should be fixed. This fieldis utilized by the programmers/engineers to prioritized their workto be done. The available priorities are:

P1 Most important

P2

P3

P4

P5 Least important

Platform
This is the hardware platform against which the bug was reported. Legal platforms include:

This is the person in charge of resolving the bug.Every time this field changes, the status changes to NEW to makeit easy to see which new bugs have appeared on a person's list. The defaultstatus for queries is set to NEW, ASSIGNED and REOPENED. When searchingfor bugs that have been resolved or verified, remember to set the statusfield appropriately.

Bugzilla uses several non-standard Netscape extentions,but this does not seem to cause any problem with other browsers. Thelynx browser does work, but lynx seems to cache results of a .cgi. You'llsometimes need to press CONTROL-R to reload the screen to see an update.