This page describes the various fields that you see on a bug.
STATUS |
RESOLUTION |
The Status field indicates the current state of a bug. Only certain status transitions are allowed. | The Resolution field indicates what happened to this bug. |
Open Bugs | |
|
No resolution yet. All bugs which are in one of these "open" states have no resolution set. |
Closed Bugs | |
|
|
Other Fields
- Alias
- 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.
- Assignee
- The person in charge of resolving the bug.
- Assignee Real Name
- A custom Unknown Type field in this installation of Bugzilla.
- Bisected commit-id
- Full commit-id of the commit that introduced this regression.
- Blocks
- 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.
- CC
- Users who may not have a direct role to play on this bug, but who are interested in its progress.
- Changed
- When this bug was last updated.
- Classification
- Bugs are categorised into Classifications, Products and Components. classifications is the top-level categorisation.
- Comment
- Bugs have comments added to them by Bugzilla users. You can search for some text in those comments.
- Comment Tag
- A custom Unknown Type field in this installation of Bugzilla.
- Component
- Components are second-level categories; each belongs to a particular Product. Select a Product to narrow down this list.
- Content
- This is a field available in searches that does a Google-like 'full-text' search on the Summary and Comment fields.
- Creation date
- When the bug was filed.
- Deadline
- The date that this bug must be resolved by, entered in YYYY-MM-DD format.
- Depends on
- The bugs listed here must be resolved before this bug can be resolved.
- Duplicate of
- A custom Unknown Type field in this installation of Bugzilla.
- Hardware
- The hardware platform the bug was observed on. Note: When searching, selecting the option "All" only finds bugs whose value for this field is literally the word "All".
- Importance
- The importance of a bug is described as the combination of its Priority and Severity.
- Kernel Version
- A custom Free Text field in this installation of Bugzilla.
- Keywords
- You can add keywords from a defined list to bugs, in order to easily identify and group them.
- Last Visit
- A custom Date/Time field in this installation of Bugzilla.
- OS
- The operating system the bug was observed on. Note: When searching, selecting the option "All" only finds bugs whose value for this field is literally the word "All".
- Personal Tags
- Unlike Keywords which are global and visible by all users, Personal Tags are personal and can only be viewed and edited by their author. Editing them won't send any notification to other users. Use them to tag and keep track of bugs.
- Priority
- Engineers prioritize their bugs using this field.
- Product
- Bugs are categorised into Products and Components.
- QA Contact
- The person responsible for confirming this bug if it is unconfirmed, and for verifying the fix once the bug has been resolved.
- QA Contact Real Name
- A custom Unknown Type field in this installation of Bugzilla.
- Regression
- A custom Drop Down field in this installation of Bugzilla.
- Reporter
- The person who filed this bug.
- Reporter Real Name
- A custom Unknown Type field in this installation of Bugzilla.
- See Also
- This allows you to refer to bugs in other 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 whitespace.
You should normally use this field to refer to bugs in other installations. For bugs in this installation, it is better to use the Depends on and Blocks fields.
- Severity
- How severe the bug is, or whether it's an enhancement.
- Subsystem
- The subsystem responsible for this bug (must match MAINTAINERS entry verbatim)
- Summary
- The bug summary is a short sentence which succinctly describes what the bug is about.
- URL
- Bugs can have a URL associated with them - for example, a pointer to a web site where the problem is seen.
- Version
- The version field defines the version of the software the bug was found in.