MozillaWiki

BMO/UserGuide/BugFields: Difference between revisions

Page Discussion

BMO/UserGuide/BugFields (view source)

Revision as of 14:22, 14 May 2024

2,927 bytes added ,  14 May 2024
no edit summary
(improve the priority section)
No edit summary
 
(27 intermediate revisions by 10 users not shown)
Line 34: Line 34:
; Creation date
; Creation date
: When the bug was filed.
: When the bug was filed.
{{anchor|depends_on}}
{{anchor|dependson}}
; Depends on
; Depends on
: The bugs listed here must be resolved before this bug can be resolved.
: The bugs listed here must be resolved before this bug can be resolved.
Line 40: Line 40:
; Duplicates
; Duplicates
: List of bugs that have been marked a duplicate of the bug currently being viewed.
: 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}}
{{anchor|keywords}}
; Keywords
; Keywords
: You can add keywords from a defined list to bugs, in order to easily identify and group them.
: Keywords are a controlled vocabulary for characterizing bugs across Products and Components. Examples of this field are <code>regression</code>, <code>sec-high</code>, and <code>topcrash</code>. Bugzilla administrators manage [https://bugzilla.mozilla.org/describekeywords.cgi the list of keywords]. If you believe you need a new keyword, [https://bugzilla.mozilla.org/enter_bug.cgi?product=bugzilla.mozilla.org&component=Administration please contact the administrators to discuss].
{{anchor|bug_mentor}}
{{anchor|bug_mentor}}
; Mentors
; Mentors
Line 57: Line 51:
{{anchor|op_sys}}
{{anchor|op_sys}}
; OS
; 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}}
{{anchor|priority}}
; 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://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage How Do You Triage] 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}}
{{anchor|product}}
; Product
; Product
Line 70: Line 84:
; Rank
; Rank
: Used by some groups to provide finer-grained ordering for working on bugs than afforded by the Priority field. Use of this field is restricted to the `rank-setters` group.
: Used by some groups to provide finer-grained ordering for working on bugs than afforded by the Priority field. Use of this field is restricted to the `rank-setters` group.
{{anchor|regressed_by}}
; Regressed by
: This bug has been introduced by the bugs listed here.
{{anchor|regresses}}
; Regressions
: This bug has introduced the bugs listed here.
{{anchor|reporter}}
{{anchor|reporter}}
; Reporter
; Reporter
Line 75: Line 95:
{{anchor|see_also}}
{{anchor|see_also}}
; 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}}
{{anchor|bug_severity}}
; 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"
{| 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
  |-
  |-
  |'''enhancement'''
  |'''N/A'''
  |Request for enhancement
  |(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}}
{{anchor|short_desc}}
Line 106: Line 126:
{{anchor|target_milestone}}
{{anchor|target_milestone}}
; Target Milestone
; Target Milestone
: The Target Milestone field is used to define when the patch landed first. Relying on status flags is usually safer.
: For Firefox-related bugs, when a change set (patch) lands in Mozilla-Central, the [[Sheriffing|sheriffs]] will set this field to the corresponding release value for the current Nightly.
: Release status and tracking flags are used to mark intentions for when a fix or other patch should land.  
: If you need to track a bug against a set of milestones other than upcoming versions of Firefox, please tell the Bugzilla team, you may want a custom status flag.  
{{anchor|triage_owner}}
{{anchor|triage_owner}}
; Triage Owner
; Triage Owner
: User that is responsible for triaging bugs that are assigned to 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://firefox-source-docs.mozilla.org/bug-mgmt/guides/bug-types.html type of a bug].
{| class="wikitable"
|-
! Type !! Description
|-
|'''defect'''
|regression, crash, hang, security vulnerability and any other general issue.
|-
|'''enhancement'''
|new feature, improvement in UI, performance, etc. and any other request for user-facing changes and enhancements in the product; not engineering changes
|-
|'''task'''
|refactoring, removal, replacement, enabling or disabling of functionality and any other engineering task
|}
{{anchor|bug_file_loc}}
{{anchor|bug_file_loc}}
; URL
; URL
Line 118: Line 156:
{{anchor|votes}}
{{anchor|votes}}
; Votes
; Votes
: Some bugs can be voted for, and you can limit your search to bugs with more than a certain number of votes. Votes are not really used by Mozilla developers.
: Some bugs can be voted for, and you can limit your search to bugs with more than a certain number of votes. Votes are not used by Mozilla developers to set priorities.
{{anchor|status_whiteboard}}
{{anchor|status_whiteboard}}
; Whiteboard
; Whiteboard
: Each bug has a free-form single line text entry box for adding tags and status information
: Each bug has a free-form single line text entry box for adding tags and status information
Glob
Confirmed users
1,201

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/1202573...1250790"