From Fedora Project Wiki
m (1 revision(s)) |
(→Triage Check List: fix up list for MW) |
||
| Line 1: | Line 1: | ||
== Triage Check List == | == Triage Check List == | ||
Here is a check list of regular things to check for: | Here is a check list of regular things to check for: | ||
# Reviewing bugs in a states of ''NEW'' | |||
* changing them to assigned if sufficient information is present to reproduce or fix the bug | #* changing them to assigned if sufficient information is present to reproduce or fix the bug | ||
* changing the status to ''NEEDINFO'' if insufficient information is present | #* changing the status to ''NEEDINFO'' if insufficient information is present | ||
# Reviewing bugs in a states of of ''NEEDINFO'' greater than thirty (30) days | |||
* Close them if the NEEDINFO request has not be addressed | #* Close them if the NEEDINFO request has not be addressed | ||
# Is the bug a duplicate? | |||
* This is the most common type | #* This is the most common type | ||
* Is this bug is a duplicate of a previous solved or unsolved bug? | #* Is this bug is a duplicate of a previous solved or unsolved bug? | ||
* See [[BugZappers/FindingDuplicates| Finding Duplicates]] for more information on the master art of finding duplicates | #* See [[BugZappers/FindingDuplicates| Finding Duplicates]] for more information on the master art of finding duplicates | ||
# Does the bug need more information from the original reporter? | |||
* Is enough information present about the reporter's system? | #* Is enough information present about the reporter's system? | ||
* Are clear instructions present about how to reproduce the bug? | #* Are clear instructions present about how to reproduce the bug? | ||
* Has the reporter included sufficient troubleshooting information or error logs? | #* Has the reporter included sufficient troubleshooting information or error logs? | ||
* Are there attached screenshots for GUI bugs? | #* Are there attached screenshots for GUI bugs? | ||
# Is the reported bug related to another bug that has already been reported? | |||
* Would solving one bug help the other? | #* Would solving one bug help the other? | ||
# Is the bug reported under the correct bugzilla component (source package)? | |||
* See determining the [[BugZappers/CorrectComponent| correct component]] | #* See determining the [[BugZappers/CorrectComponent| correct component]] | ||
* For example, if someone reported a problem running Firefox in GNOME, should the bug be filed under Firefox or GNOME? | #* For example, if someone reported a problem running Firefox in GNOME, should the bug be filed under Firefox or GNOME? | ||
# Is the bug reporting more than one problem--a ''Two-in-one bug''. | |||
* Should this bug be split into two bugs? | #* Should this bug be split into two bugs? | ||
* If you aren't sure get a second opinion from another triager or developer on IRC. | #* If you aren't sure get a second opinion from another triager or developer on IRC. | ||
# Is the bug already fixed? | |||
* If someone has confirmed it is fixed add a comment to that affect and close it. | #* If someone has confirmed it is fixed add a comment to that affect and close it. | ||
* If a fix has not been confirmed suggest trying the latest build from [http://koji.fedoraproject.org Koji Build System] | #* If a fix has not been confirmed suggest trying the latest build from [http://koji.fedoraproject.org Koji Build System] | ||
== Going Deeper == | == Going Deeper == | ||
Revision as of 01:57, 27 May 2008
Triage Check List
Here is a check list of regular things to check for:
- Reviewing bugs in a states of NEW
- changing them to assigned if sufficient information is present to reproduce or fix the bug
- changing the status to NEEDINFO if insufficient information is present
- Reviewing bugs in a states of of NEEDINFO greater than thirty (30) days
- Close them if the NEEDINFO request has not be addressed
- Is the bug a duplicate?
- This is the most common type
- Is this bug is a duplicate of a previous solved or unsolved bug?
- See Finding Duplicates for more information on the master art of finding duplicates
- Does the bug need more information from the original reporter?
- Is enough information present about the reporter's system?
- Are clear instructions present about how to reproduce the bug?
- Has the reporter included sufficient troubleshooting information or error logs?
- Are there attached screenshots for GUI bugs?
- Is the reported bug related to another bug that has already been reported?
- Would solving one bug help the other?
- Is the bug reported under the correct bugzilla component (source package)?
- See determining the correct component
- For example, if someone reported a problem running Firefox in GNOME, should the bug be filed under Firefox or GNOME?
- Is the bug reporting more than one problem--a Two-in-one bug.
- Should this bug be split into two bugs?
- If you aren't sure get a second opinion from another triager or developer on IRC.
- Is the bug already fixed?
- If someone has confirmed it is fixed add a comment to that affect and close it.
- If a fix has not been confirmed suggest trying the latest build from Koji Build System
Going Deeper
- Understanding the differences between Bugs and Features .
- Bug state flow: Bug Lifecycle
- Understanding things that Bugzilla does automatically