BugZappers/How to Triage

Triage Check List

Here is a check list of regular things to check for:

1. 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

1. Reviewing bugs in a states of of NEEDINFO greater than thirty (30) days

• Close them if the NEEDINFO request has not be addressed

1. 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

1. 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?

1. Is the reported bug related to another bug that has already been reported?

• Would solving one bug help the other?

1. 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?

1. 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.

1. 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

---