This bug is valid and has recently been filed. Bugs in this state become IN_PROGRESS when somebody is working on them, or become resolved and marked RESOLVED.

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

A fix for this bug is checked into the tree and tested.

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 CONFIRMED, or resolved and become RESOLVED.

The problem described is not a bug.

The problem was specific to a related product whose bugs are tracked in another application

This word, or the terms "REQUIRED" or "SHALL", mean that the definition is an absolute requirement of the specification. RFC2119

This phrase, or the phrase "SHALL NOT", mean that the definition is an absolute prohibition of the specification. RFC2119

This word, or the adjective "RECOMMENDED", mean that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course. RFC2119

This phrase, or the phrase "NOT RECOMMENDED" mean that there may exist valid reasons in particular circumstances when the particular behavior is acceptable or even useful, but the full implications should be understood and the case carefully weighed before implementing any behavior described with this label. RFC2119

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 CONFIRMED. Or, it may be directly resolved and marked RESOLVED.

The problem described is a bug which will never be fixed

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.