Bugzilla Field Descriptions
- A short, unique name assigned to a bug in order to assist with looking it up and referring to it in other places in Bugzilla.
- This is the person in charge of resolving the bug. Every time this field changes, the status changes to NEW to make it easy to see which new bugs have appeared on a person's list.
- This bug must be resolved before the bugs listed in this field can be resolved.
- Bug ID
- The numeric id of a bug, unique within this entire installation of Bugzilla.
- Users who may not have a direct role to play on this bug, but who are interested in its progress.
- When this bug was last updated.
- Bugs are categorised into Classifications, Products and Components. classifications is the top-level categorization.
- Bugs have comments added to them by Bugzilla users. You can search for some text in those comments.
- Comment Tag
- Comments can have arbitrary tags added to them to help with filtering as well as mark comments as spam or abusive.
- Components are second-level categories; each belongs to a particular Product. Select a Product to narrow down this list.
- Creation date
- When the bug was filed.
- Depends on
- The bugs listed here must be resolved before this bug can be resolved.
- List of bugs that have been marked a duplicate of the bug currently being viewed.
- This is the hardware platform against which the bug was reported.
- The importance of a bug is described as the combination of its Priority and Severity.
- Keywords are a controlled vocabulary for characterizing bugs across Products and Components. Examples of this field are
topcrash. Bugzilla administrators manage the list of keywords. If you believe you need a new keyword, please contact the administrators to discuss.
- Mentors are users who have offered to help the bug owner with such tasks as setting up a development environment, finding relevant information to fixing the bug, how to submit a patch for review, and finally how to get the fix committed.
- More information has been requested from specific individuals, or anyone, to move the bug forward to completion.
- This is the operating system against which the bug was reported.=
- This field describes the importance and order in which a bug should be fixed compared to other bugs. This field is utilized by the programmers/engineers/release managers/managers to prioritize the work to be done. See the Firefox triage documentation or for the main Bugzilla project, Bugzilla:Priority_System.
- Bugs are categorised into Products and Components. Select a Classification to narrow down this list.
- QA Contact
- The person responsible for confirming this bug if it is unconfirmed, and for verifying the fix once the bug has been resolved.
- Used by some groups to provide finer-grained ordering for working on bugs than afforded by the Priority field. Use of this field is restricted to the `rank-setters` group.
- Regressed by
- This bug has been introduced by the bugs listed here.
- This bug has introduced the bugs listed here.
- The person who filed this bug.
- See Also
- This allows you to refer to bugs in other bug tracker installations. You can enter a URL to a bug in the 'Add Bug URLs' field to note that that 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 bugs in other bug tracker installations. For bugs in this bug tracker installation, it is better to use the Depends on and Blocks fields.
- This field describes the impact of a bug.
|blocker||Broken important user-facing feature, Blocks development and/or testing work|
|normal||Default; Regular issue, some loss of functionality under specific circumstances|
|minor||Affecting a small number of users (i.e. ArchLinux users on PowerPC), a problem with an easy workaround, or a cosmetic issue such as misspellings or text alignment|
- The bug summary is a short sentence which succinctly describes what the bug is about.
- Target Milestone
- For Firefox-related bugs, when a change set (patch) lands in Mozilla-Central, the sheriffs will set this field to the corresponding release value for the current Nightly.
- Release status and tracking flags are used to mark intentions for when a fix or other patch should land.
- If you need to track a bug against a set of milestones other than upcoming versions of Firefox, please tell the Bugzilla team, you may want a custom status flag.
- Triage Owner
- User that is responsible for triaging bugs in a specific component.
- This field describes the type of a bug.
|defect||regression, crash, hang, security vulnerability and any other general issue.|
|enhancement||new feature, improvement in UI, performance, etc. and any other request for user-facing changes and enhancements in the product; not engineering changes|
|task||refactoring, removal, replacement, enabling or disabling of functionality and any other engineering task|
- Bugs can have a URL associated with them - for example, a pointer to a web site where the problem is seen.
- The version field defines the version of the software the bug was found in.
- Some bugs can be voted for, and you can limit your search to bugs with more than a certain number of votes. Votes are not used by Mozilla developers to set priorities.
- Each bug has a free-form single line text entry box for adding tags and status information