Bugmasters/Projects/Folk Knowledge/Priority Field: Difference between revisions
< Bugmasters | Projects | Folk Knowledge
Jump to navigation
Jump to search
(Document priority-based triage used by Media and Search teams) |
(→Priority-based triage: Media team tries to close bugs which aren't actionable) |
||
| Line 11: | Line 11: | ||
* P5 - A real issue, but no intent to fix. (patches usually welcome) | * P5 - A real issue, but no intent to fix. (patches usually welcome) | ||
Bugs without the priority field set are untriaged. | Bugs without the priority field set are untriaged. Bugs that are not real issues or which go several weeks without progress toward determining an actionable cause are generally closed. | ||
The following teams use this workflow: | The following teams use this workflow: | ||
Revision as of 20:50, 1 April 2016
Mobile team (Fennec, iOS) essentially don't use Bugzilla's priority field. Mobile team uses tracking-fennec 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. Bugs that are not real issues or which go several weeks without progress toward determining an actionable cause are generally closed.
The following teams use this workflow:
- Media Playback
- Awesome Search Team