BMO/UserGuide/BugFields: Difference between revisions

← Older edit

BMO/UserGuide/BugFields (view source)

Revision as of 14:22, 14 May 2024

1,493 bytes added , 14 May 2024

no edit summary

Glob

Confirmed users

1,201

edits

@@ Line 34: / Line 34: @@
 ; Creation date
 : When the bug was filed.
-{{anchor|depends_on}}
+{{anchor|dependson}}
 ; Depends on
 : The bugs listed here must be resolved before this bug can be resolved.
@@ Line 40: / Line 40: @@
 ; Duplicates
 : List of bugs that have been marked a duplicate of the bug currently being viewed.
-{{anchor|rep_platform}}
-; Hardware
-: This is the hardware platform against which the bug was reported.
-{{anchor|importance}}
-; Importance
-: The importance of a bug is described as the combination of its Priority and Severity.
 {{anchor|keywords}}
 ; Keywords
@@ Line 57: / Line 51: @@
 {{anchor|op_sys}}
 ; OS
-: This is the operating system against which the bug was reported.=
+: This is the operating system against which the bug was reported.
+{{anchor|rep_platform}}
+; Platform
+: This is the hardware platform against which the bug was reported (ARM, ARM64, x86, x86_64, etc).
 {{anchor|priority}}
 ; Priority
-: This field describes the importance and order in which a bug should be fixed compared to other bugs. This field is utilized by the programmers/engineers/release managers/managers to prioritize the work to be done. See [https://mozilla.github.io/bug-handling/triage-bugzilla the Firefox triage documentation] or for the main Bugzilla project, [[Bugzilla:Priority_System]].
+{| class="wikitable"
+|-
+! 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 priority is for the Web Platform Test bot.
+|-
+| '''P5''' || Will not fix, but will accept a patch
+|}
+: This field describes the importance and order in which a bug should be fixed compared to other bugs. This field is utilized by the programmers/engineers/release managers/managers to prioritize the work to be done. 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/priority.html priority definitions], or for the main Bugzilla project, [[Bugzilla:Priority_System]].
 {{anchor|product}}
 ; Product
@@ Line 81: / Line 95: @@
 {{anchor|see_also}}
 ; See Also
-: This allows you to refer to bugs in other installations. You can enter a URL to a bug in the 'Add Bug URLs' field to note that that bug is related to this one. You can enter multiple URLs at once by separating them with a comma. You should normally use this field to refer to bugs in other installations. For bugs in this installation, it is better to use the Depends on and Blocks fields.
+: This allows you to refer to bugs in other bug tracker installations. You can enter a URL to a bug in the 'Add Bug URLs' field to note that that bug is related to this one. You can enter multiple URLs at once by separating them with a comma. You should normally use this field to refer to bugs in other bug tracker installations, or bugs which are related to, but not known to be duplicates of the bug. Bugs which are regressions should be listed in the Regressed by field (above)
 {{anchor|bug_severity}}
 ; Severity
-: This field describes the impact of a bug.
+: 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"
- |'''blocker'''
- |Blocks development and/or testing work
   |-
-  |'''critical'''
+  ! Severity !! Description
- |Crashes, loss of data, severe memory leak
   |-
-  |'''major'''
+  |'''--'''
-  |Major loss of function
+  |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.
+ |-
+ |'''S1'''
+ |(Catastrophic) Blocks development/testing, may impact more than 25% of users, causes data loss, likely dot release driver, and no workaround available
   |-
-  |'''normal'''
+  |'''S2'''
-  |Regular issue, some loss of functionality under specific circumstances
+  |(Serious) Major functionality/product severely impaired or a high impact issue and a satisfactory workaround does not exist
   |-
-  |'''minor'''
+  |'''S3'''
-  |Minor loss of function, or other problem where easy workaround is present
+  |(Normal) Blocks non-critical functionality or a work around exists
   |-
-  |'''trivial'''
+  |'''S4'''
-  |Cosmetic problem like misspelled words or misaligned text
+  |(Small/Trivial) minor significance, cosmetic issues, low or no impact to users
+ |-
+ |'''N/A'''
+ |(Not Applicable) The above definitions do not apply to this bug; this value is reserved for bugs of type Task or Enhancement
   |}
 {{anchor|short_desc}}
@@ Line 114: / Line 131: @@
 {{anchor|triage_owner}}
 ; Triage Owner
-: User that is responsible [https://mozilla.github.io/bug-handling/triage-bugzilla for triaging bugs in a specific component].
+: User that is responsible [https://firefox-source-docs.mozilla.org/bug-mgmt/policies/triage-bugzilla.html for triaging bugs in a specific component].
 {{anchor|bug_type}}
 ; Type
-: This field describes the [https://mozilla.github.io/bug-handling/bug-types type of a bug].
+: 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'''