Confirmed users
111
edits
Bugmasters/Projects/Folk Knowledge/Priority Field: Difference between revisions
Bugmasters/Projects/Folk Knowledge/Priority Field (view source)
Revision as of 20:48, 1 April 2016
, 1 April 2016Document priority-based triage used by Media and Search teams
Nalexander (talk | contribs) (Created page with "Mobile team (Fennec, iOS) essentially don't use Bugzilla's priority field. Mobile team uses <tt>tracking-fennec</tt> flags to track releases; we assign individuals to track t...") |
(Document priority-based triage used by Media and Search teams) |
||
| Line 1: | Line 1: | ||
Mobile team (Fennec, iOS) essentially don't use Bugzilla's priority field. Mobile team uses <tt>tracking-fennec</tt> flags to track releases; we assign individuals to track tickets; and we switch the status to ASSIGNED to mean "work is happening". | Mobile team (Fennec, iOS) essentially don't use Bugzilla's priority field. Mobile team uses <tt>tracking-fennec</tt> flags to track releases; we assign individuals to track tickets; and we switch the status to ASSIGNED to mean "work is happening". | ||
== Priority-based triage == | |||
Some teams us the priority field to sort bugs. | |||
* P1 - Fix immediately | |||
* P2 - Needs to be fixed, but not urgent | |||
* P3 - Would like to fix, but waiting for resources (optional) | |||
* P4 - Not used or the same as P5. | |||
* P5 - A real issue, but no intent to fix. (patches usually welcome) | |||
Bugs without the priority field set are untriaged. | |||
The following teams use this workflow: | |||
* Media Playback | |||
* Awesome Search Team | |||