BMO/UserGuide: Difference between revisions

← Older edit

BMO/UserGuide (view source)

Revision as of 16:37, 16 July 2024

4,193 bytes added , 16 July 2024

Added bug tracking statuses link

DanielNL

64

edits

@@ Line 89: / Line 89: @@
 The whiteboard field is for free tagging. It's used both by teams and by people who want to track bugs they're interested in.
-== Tracking Flags ==
+== Tracking Status ==
+See [[BMO/UserGuide/BugStatuses]]
+== Tracking Flags  ==
+[[File:Flagexample.png||400px|right]]
+=== tracking-firefoxXX ===
 ''Who's doing the tracking?  Should i even set these flags?''
-Tracking flags are used by developers, triagers, QA and the release management teams to keep track of bugs whose fixes are slated to go into a particular product release.
+Tracking flags are used by developers, triagers, QA and the release management teams to keep track of bugs whose fixes are slated to go into a particular product release. A tracking flag shows whether a bug is being investigated for possible resolution in the Firefox XX release. Bugs marked tracking-Firefox XX are bugs that must be resolved one way or another before a particular release ships. [[Firefox/Drivers|Release drivers]] will track and shepherd the bug until it is determined the bug no longer impacts the release.
 [[File:Tracking-flag-example.png|thumb]]
@@ Line 118: / Line 124: @@
 If you would like to suggest a bug and its fix be considered (by release managers) for a particular release, edit the bug and set the tracking flag for that release to ''?''. This is often done for a bug that's been fixed in one release channel but needs to be uplifted to another.
+Refer to [http://web.archive.org/web/20160417051846/https://blog.mozilla.org/channels/2011/06/01/more-details-about-how-to-use-the-tracking-firefox-bugzilla-flag/ these guidelines] on setting the tracking flag.
+=== status-firefoxXX ===
+A flag which represents the status of the bug with respect to Firefox XX.
+{| class="wikitable"
+|+ status-firefoxXX
+|-
+| --- || We don't know whether Firefox XX is affected
+|-
+| ? || We don't know whether Firefox XX is affected, but we want to find out
+|-
+| unaffected || This bug does not affect Firefox XX
+|-
+| affected || This bug affects Firefox XX
+|-
+| fix-optional || This bug affects Firefox XX, we would take a fix but don't consider it as release blocking
+|-
+| fixed || This bug is fixed in Firefox XX
+|-
+| verified || This bug is fixed and verified in Firefox XX
+|-
+| disabled || This feature is disabled in Firefox XX
+|-
+| verified disabled || Disabling the feature is verified in Firefox XX
+|-
+| wontfix || A fix for this bug will not be accepted in Firefox XX
+|-
+|}
+'''Approval Flags''': Set on the attachment of a bug
+All patches landing on ''mozilla-beta/release/esr'' branches must have these nominated by setting a ''''' ? ''''' flag. <br>Please make sure to fill in the populated list of questions '''[Approval Request Comment]''' that come up on the attachment.
+This helps Release Management understand the user impact & the risk/reward analysis before we grant or deny approval. If this form is left incomplete it will be sent back to you for completion.
+[[File:ApprovalRequest.png|750px|centre]]
 == Status Flags ==
-Status flags detail, at the release level, [https://mozilla.github.io/bug-handling/triage-bugzilla#what-about-release-status-status_firefoxnn-flags if a bug is present or will be addressed in a particular version].
+Status flags detail, at the release level, if a bug is present or will be addressed in a particular version.
 [[File:Status-flag-example.png|Thumb]]
@@ Line 128: / Line 169: @@
 Project flags are used to supplement a bug's prioritization. These flags are defined at the product and component level and will not be present for all bugs. Most often they are used to establish when a bug is to be worked on during a multi-release spanning project.
+Example project flags are:
+* [https://firefox-source-docs.mozilla.org/bug-mgmt/processes/accessibility-review.html a11y-review]
+* [https://wiki.mozilla.org/Compatibility/WebCompat_Priority_Flags Webcompat Priority]
+* [https://wiki.mozilla.org/Performance/Bugzilla#Project_Flag Performance Impact]
 == Needinfo Flag ==
-''It's good and you should use it.''
-If you have a question about a bug, and you'd like to direct that question to a specific person, you can do that easily with the needinfo flag.
+In some bug tracking systems, to request information from someone about a bug, the bug is usually assigned to the person asked. In Bugzilla, we use ''needinfo'' flags.
+The ''needinfo'' flag can be set at or after a bug's creation. When a ''needinfo'' flag is set, the person asked receives an email directing them to visit the bug, logging in if necessary, and answer the question.
+To create a ''needinfo'', you can specify the bug's assignee (if any,) the bug's triage owner (if one is defined,) the bug's reporter, or another user. Ask the question in a comment and set the ''needinfo'' flag before you save the bug.
+Common uses of ''needinfo'' include:
+* Asking a bug reporter for more information so that a bug can be triaged
+* Asking a subject matter expert for direction or clarification
+Please respond to ''needinfo'' requests quickly to keep others from being blocked.
+To clear a needinfo, go to the bug's page, respond to the question and save your comment. By default the ''clear this needinfo request'' checkbox is ticked.
+If you need to route the request to another person, leave the ''clear this needinfo request'' checkbox ticked, and set a new ''needinfo'' for the person to which you want to send the question to, then save the bug.
+You can see the ''needinfo'' flags you have requested of others and the ones requested of you in  [https://bugzilla.mozilla.org/page.cgi?id=mydashboard.html My Dashboard].
+= Team to components mapping =
+All Bugzilla components are linked to a team.
+The full list of teams is available at https://bugzilla.mozilla.org/rest/config/component_teams.
+The full list of components linked to a specific team is available at https://bugzilla.mozilla.org/rest/config/component_teams/TEAM_NAME (replace TEAM_NAME with an actual team name).
+Use https://bugzilla.mozilla.org/rest/product?type=accessible&include_fields=name&include_fields=components.name&include_fields=components.team_name if you want to find out what team is assigned to a specific component.
+When creating a new component, make sure to link it to the right team. If you are not sure, use the team the triage owner of the new component belongs to.
+== Adding a new team or changing an existing one ==
-The person you need info from will get bugmail with (look up the X-Bugzilla-header) in the header. This may get a person's attention faster than adding them to the CC list of a bug.
+File a bug at https://bugzilla.mozilla.org/enter_bug.cgi?product=bugzilla.mozilla.org&component=Administration asking to change component info.
-You can see the needinfo flags you have requested of others and the ones requested of you in  [https://bugzilla.mozilla.org/page.cgi?id=mydashboard.html My Dashboard].
+Make sure :marco is CCed so they can adjust the quality weekly reports. Needinfo :dveditz to adjust the weekly security report
 = Other Ways to use BMO and its Data =