This page describes the various fields that you see
on a bug.
|The field indicates the
current state of a bug. Only certain status transitions
||The field indicates what
happened to this bug.
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
Or, it may be directly resolved and marked
This bug is valid and has recently been filed.
Bugs in this state become
when somebody is working on them, or become resolved and marked
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
resolved and become
No resolution yet. All bugs which are in one of
these "open" states have no resolution set.
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
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
The problem described is not a bug.
The problem described is a bug which will never be
The problem is a duplicate of an existing bug.
When a bug is marked as a
you will see which bug it is a duplicate of,
next to the resolution.
All attempts at reproducing this bug were futile,
and reading the code produces no clues as to why the described
behavior would occur. If more information appears later,
the bug can be reopened.
- The person responsible for confirming this bug if it is unconfirmed, and for verifying the fix once the bug has been resolved.
- A custom Unknown Type field in this installation of Bugzilla.
- The importance of a bug is described as the combination of
its and .
- Some bugs can be voted for, and you can limit your search to bugs with more than a certain number of votes.