QA/Bugzilla/Fields/Priority

From The Document Foundation Wiki
< QA‎ | Bugzilla‎ | Fields
Jump to: navigation, search

This page is about the Priority field in Bugzilla.

Getting Started

Below is a list of each level of priority from Highest to Lowest. These are meant to be general guidelines for QA individuals trying to triage bugs.

At the end of the section is a flowchart which provides an example of how one could potentially triage priority of bugs as they are moved from UNCONFIRMED to NEW or ASSIGNED. These are meant to be guidelines not strict standards, any suggestions to make the process better should be made through the QA mailing list where we can discuss potential changes.

Access Control

To ensure that bugs triaged by QA are being prioritized as consistently as possible, access to the Priority field is restricted to admins and users in the 'Contributors' group who have learned our policy about setting the Priority.

If you'd like to become a Contributor, it's easy. Just

  1. Read this page and familiarize yourself with our Priority structure
  2. Ask one of the Bugzilla admins in the QA IRC Channel or on the QA Mailing List to upgrade your Bugzilla account. We're happy to have you on board!

Priority Levels

  • Highest
Crash/Loss of data/Inability to install/Other broken core functionality. Affects all/nearly-all users and documents.
We reserve this level for our "Most Annoying Bugs" -- items that need attention super-promptly.
  • High
Serious problems/Inability to open certain documents/Tediously slow.
Affects many users.
  • Medium
Prevents users from making professional-quality work or breaks some features.
  • Low
Doesn't affect ability to make high-quality work. Suggestion for improvement.
  • Lowest
Wishlist item, Incredibly minor issue, or similar.

Example Flowchart(s)

Feel free to amend this section with examples of how triaging Priority can be done. There is no one right way but when it is being done the QA member should do everything in their power to be consistent. Also, try to comment when changing things so that other members and our users know your thought process.

Example 1.jpg