BMO/UserGuide/BugFields: Difference between revisions

{{anchor|dependson}}

: 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].

: This is the operating system against which the bug was reported.

 

: 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]].

: 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)

: 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].

  ! 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.

|(Catastrophic) Blocks development/testing, may impact more than 25% of users, causes data loss, likely dot release driver, and no workaround available

  |'''S2'''

  |(Serious) Major functionality/product severely impaired or a high impact issue and a satisfactory workaround does not exist

  |'''S3'''

  |(Normal) Blocks non-critical functionality or a work around exists

  |'''S4'''

  |(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

: 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.  

: User that is responsible [https://firefox-source-docs.mozilla.org/bug-mgmt/policies/triage-bugzilla.html for triaging bugs in a specific component].

: This field describes the [https://firefox-source-docs.mozilla.org/bug-mgmt/guides/bug-types.html type of a bug].

: 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.