|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.
- This bug has recently been added to the database. Nobody has
validated that this bug is true. 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 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.
- 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.
- 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
- No resolution yet. All bugs which are in one of these "open" states
have the resolution set to blank. All other bugs
will be marked with one of the following resolutions.
- 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.
- 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 ships, at
which point they become 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
- A fix for this bug is checked into the tree and tested.
- The problem described is not a bug
- The problem described is a bug which will never be fixed.
- The problem described is a bug which will not be fixed in this
version of the product.
- The problem described is a bug which will probably not be fixed in this
version of the product, but might still be.
- 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.
- 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.