Triaging a Bug on Bugzilla
Purpose
- I could go on with how many bugs are still in an UNCONFIRMED state on Bugzilla, but I don't think it needs any mentioning
- Currently, there isn't a triaging guideline doc on what's needed in order to perform that job correctly and we'd like to get a host of volunteers that are interested in it
- The only way to do that is to let it be known that not only is that job available, but also how and what's needed to do that job
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
Requirements
- Get Set Up
- Download the newest nightly build
- Register an account with Bugzilla
- Bugzilla Permissions
- The community member will need to have their permissions upgraded to "canconfirm" status which allows a person to change bug states, details and flags on all bugs
- 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 do this, you'll need to verify your competency to a MozQA Community Member who has the ability to give you those permissions.
- List of people who can (link to the QMO community page)
Table of Contents
- Unfortunately, the learning curve is very high for performing such a complex undertaking like this, but it's actually not that bad if it's split up into smaller ones. Each of the following pages will you give you a snippet of what it's like to perform this task on a regular basis.