Confirm
3,324
edits
Changes
m
Clean up Priority, Severity, and Type tables
! Priority !! Description
|-
| '''- -''' || No decision
|-
| '''P1 ''' || Fix in the current release cycle
|-
| '''P2 ''' || Fix in the next release cycle or the following (nightly + 1 or nightly + 2)
|-
| '''P3 ''' || Backlog
|-
| '''P4 ''' || Do not use, this . This priority is for web platform test botsthe Web Platform Test bot.
|-
| '''P5 ''' || Will not fix, but will accept a patch
|}
: This field describes the impact of a bug. This field is utilized by the programmers/engineers/release managers/managers to determine the severity of issues and used as input for the priority of the bug. It should not be set by people filing bugs. See the Firefox [https://firefox-source-docs.mozilla.org/bug-mgmt/policies/triage-bugzilla.html triage documentation] and [https://firefox-source-docs.mozilla.org/bug-mgmt/guides/severity.html severity documentation].
{| class="wikitable"
|-
! Severity !! Description
|-
|'''--'''
|Default value for new bugs; bug triagers for components (ie engineers and other core project folks) are expected to update the bug's severity from this value. To avoid them missing new bugs for triage, do not alter this default when filing bugs.
: This field describes the [https://firefox-source-docs.mozilla.org/bug-mgmt/guides/bug-types.html type of a bug].
{| class="wikitable"
|-
! Type !! Description
|-
|'''defect'''
