This page describes the various fields that you see on a bug.



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
This bug has recently been added to the database. Nobody has confirmed that this bug is valid. Users who have the "canconfirm" permission set may confirm this bug, changing its state to NEW. Or, it may be directly resolved and marked RESOLVED.
This bug is valid and has recently been filed. Bugs in this state become ASSIGNED when somebody is working on them, or become resolved and marked RESOLVED.
This bug is not yet resolved, but is assigned to the proper person who is working on the bug. From here, bugs can be given to another person and become NEW, or resolved and become RESOLVED.
The report is not complete to determine whether the described problem is a bug and we need additional information or actions from the reporter. For more information, click here.
No resolution yet. All bugs which are in one of these "open" states have no resolution set.
Closed Bugs
A resolution has been performed, and it is awaiting verification by QA. From here bugs are either reopened and given some open status, or are verified by QA and marked VERIFIED.
QA has looked at the bug and the resolution and agrees that the appropriate resolution has been taken. This is the final status for bugs.
A fix for this bug is checked into the tree and tested.
The problem described is not a proper bug report.
The problem lacks information or the attach example document to follow up with the bug triage.
The problem described by the bug reporter is part of the expected behavior of LibreOffice.
There is a problem here, but it's not a problem in LibreOffice.
Used, when Bugzilla is not the proper place to report the problem.
The problem described is a bug which will never be fixed.
The problem is a duplicate of an existing bug. When a bug is marked as a DUPLICATE, you will see which bug it is a duplicate of, next to the resolution.
The problem used to be reproducible, but it is not anymore with the latest version of LibreOffice. Unlike FIXED, exact fix commit is not known.

Other Fields

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.
The person in charge of resolving the bug.
Assignee Real Name
A custom Unknown Type field in this installation of Bugzilla.
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 categorisation.
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.
Components are second-level categories; each belongs to a particular Product. Select a Product to narrow down this list.
This is a field available in searches that does a Google-like 'full-text' search on the Summary and Comment fields.
Crash report or crash signature
A crash signature (or a crash report UUID / URL) linking the bug report to A signature is surrounded by double-quotes and square brackets so it can be linked: ["crash-sign"]. For several, separate by commas: ["sign1","sign2"].
Creation date
When the bug was filed.
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.
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".
The importance of a bug is described as the combination of its Priority and Severity.
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.
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.
Engineers prioritize their bugs using this field.
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 By
Use this field to write the author ( as displayed in git ) of the commit that introduced this regression when you bisect it
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.

How severe the bug is, or whether it's an enhancement.
The bug summary is a short sentence which succinctly describes what the bug is about.
Bugs can have a URL associated with them - for example, a pointer to a web site where the problem is seen.
The earliest version of the software in which the bug can be reproduced.
Some bugs can be voted for, and you can limit your search to bugs with more than a certain number of votes.
Each bug has a free-form single line text entry box for adding tags and status information.