A Bug's Life Cycle
The status and resolution field define and track the
life cycle of a bug.
STATUS |
RESOLUTION |
| 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. |
- NEW
- This bug has recently been added to the list of bugs and must
be processed. Bugs in this state may be VERIFIED,
remain NEW, or resolved and marked CLOSED.
- ASSIGNED
- This bug is not yet resolved, but is assigned to the proper
person. From here bugs can be given to another person, or
resolved and become CLOSED.
- NEEDINFO
- This bug is waiting on additional information from the
reporter or other person in order to proceed further with
verifying/fixing of the bug report. From here the bug can
go back to ASSIGNED once the information has been given
or be CLOSED.
- MODIFIED
- Code has been modified in response to this report. A developer
has verified the problem and has discovered a solution. This means
the developer may be waiting for word from either a tester or
the reporter verifying that the problem is indeed resolved. From
here the bug can transition to CLOSED if fixed, ASSIGNED if
the problem continues, or NEEDINFO if more information is required.
- REOPENED
- 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, NEEDINFO
if more information is required, MODIFIED if code has been changed in
response to the problem, or CLOSED if it is still unreproducible or
a fix has been verified.
|
No resolution yet. All bugs which are NEW,
VERIFIED, ASSIGNED, or REOPENED have the
resolution set to blank. All other bugs will be marked with
one of the following resolutions.
|
- CLOSED
- The bug has been closed. Meaning one of several things. The bug has been
verified to be fixed by Quality Assurance and is therefore closed or the
bug was closed due to being resolved for a long period of time with no
activity meaning the bug was verified fixed by the reporter or noone seems
seems to care about it anymore. This can be changed by the reporter, assignee,
or others with proper permission.
|
- NOTABUG
- The problem described is not a bug.
- WONTFIX
- The problem described is a bug which will never be fixed.
- DEFERRED
- The problem described is a bug which will not be fixed in this
version of the product.
- DUPLICATE
- 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.
- WORKSFORME
- 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.
- CURRENTRELEASE
- The problem described has already been fixed and can be obtained
in the latest version of our product.
- RAWHIDE
- The problem describe has been fixed in the latest development
release of our product obtainable from our ftp site.
- ERRATA
- The problem described has been fixed and will be available as
an errata update from our support web site. Please check the site
to see if it is currently available for download.
- UPSTREAM
- Bugs closed with this resolution are filed in the upstream bug tracker or
reported to the upstream mailing list.
This typically includes almost all feature requests and enhancements, and most
bugs that we don't consider release showstoppers. (moving a bug upstream
typically increases the chance that someone will have time to look at it, and
often the upstream developer or bug owner even works at Red Hat - moving things
upstream simply allows us to keep everything in one place, and work better with
open source community developers outside of Red Hat. We only keep bugs open on
redhat.com to track our immediate short-term TODO items, or issues with our
patches/packaging, or because the upstream package in question has poor bug
tracking. The main focus of development for most packages is the upstream
community, even when Red Hat is a big contributor to the community.) Some
upstream bug trackers: http://bugzilla.gnome.org http://bugzilla.kde.org
http://bugzilla.mozilla.org.
|
Other Fields
Severity
|
Priority
|
| This field describes the impact of a bug. |
This field describes the importance and order in which
a bug should be fixed. The available priorities are:
|
| Security |
This report is a security issue. |
| High |
Problem due to crashes, loss of data, severe memory leak, etc. |
| Normal |
It's a bug that should be fixed eventually. |
| Low |
Problem is minor loss of function, or other problem where
easy workaround is present. |
| Enhancement |
For some feature or change you would like to see in any future releases of the product. |
| Translation |
A translation is needed for problem component or current translation is incorrect. |
|
| High |
Problem is very important. |
| Normal |
Problem is of an average importance. |
| Low |
Problem is not very important. |
|
Platform
This is the platform against which the bug was reported.
Legal platforms include:
- All (happens on all platforms; cross-platform bug)
- i386
- sparc
- alpha
- etc...
Note: Selecting the option "All" does not select bugs assigned
against all platforms. It merely selects bugs that occur on
all platforms.
Assigned To
This is the person in charge of resolving the bug.
Reporter
This is the person who reported the bug.
The default status for queries is set to NEW, ASSIGNED, NEEDINFO and REOPENED. When
searching for bugs that have been resolved or verified, remember to set the
status field appropriately.
Description and Additional Comments
Markup tags entered in these fields will appear as plain text. Numbers preceded by the word
'bug' will be converted to hyperlinks
pointing to the proper bug reports. Any email addresses
will be automatically converted to mailto: hyperlinks. Also any urls starting
with http://
will be made automatically into hyperlinks.
|
