Overview

The document is to help anyone that's interested in QA at Mozilla to learn techniques on how to help bugs go along their way. It'll help important bugs get fixed faster and optimize our community's Bugzilla efficiency. Before we get into the details, it's important to know what the Triage does as well as why its important!

What is Triaging?

Bug Triaging is the process of moving bugs logically from state to state, so they get resolved in an efficient and easy-to-comprehend manner.

Why would you want to help?

Bugzilla is the heart of the Mozilla project, every Mozilla product tracks its software defects and enhancements in BMO.  There is nothing in the project quite as central or as important as BMO. Triaging is required to ensure that all the defects reported on Bugzilla get responded to.  A back-load of bugs in any state, especially the UNCONFIRMED state, would eventually kill our ability to react to your important issues quickly and efficiently. So, our bug triagers are incredibly vital to our work-life.

Requirements

Get Set Up

• Download the newest nightly build (recommended)
  
• Register an account with Bugzilla

Bugzilla Permissions

• In order to modify bugs, you need to have at least "canconfirm" permissions.
• If you've been using Bugzilla for quite some time, you might already have these privileges. To double check, look at your Bugzilla Preferences. If your permissions say "Can confirm a bug", then you have them!
• Otherwise, you'll need to get them. To find a good place to learn about gaining permissions, please read What to do and Not to do on Bugzilla.

Table of Contents

Each of the following pages will you give you a snippet of what it's like to perform this task on a regular basis.

1. How to Track Incoming Bugs
2. How to "Clean" Incoming Bugs
3. How to Narrow Down the Steps to Reproduce
4. Finding Regression Windows