BMO/How to Use Bugzilla: Difference between revisions

← Older edit

BMO/How to Use Bugzilla (view source)

Revision as of 01:19, 4 April 2019

240 bytes added , 4 April 2019

→‎Bug triage: link to triage documentation

Emceeaich

Administrators

550

edits

@@ Line 24: / Line 24: @@
 <div class="toccolours mw-collapsible mw-collapsed" style="width:auto">
-<big>'''1. Go to https://bugzilla.mozilla.org/ .'''</big>
+'''1. Go to https://bugzilla.mozilla.org/ .'''
 <div class="mw-collapsible-content">
 * '''[[File:Bugzilla_first_page.png]]
@@ Line 30: / Line 30: @@
 <div class="toccolours mw-collapsible mw-collapsed" style="width:auto">
-<big>'''2. Click the [https://bugzilla.mozilla.org/createaccount.cgi New Account] button.'''</big>
+'''2. Click the [https://bugzilla.mozilla.org/createaccount.cgi New Account] button.'''
 <div class="mw-collapsible-content">
 * '''[[File:Create_bugzilla_account.png]]
@@ Line 36: / Line 36: @@
 <div class="toccolours mw-collapsible mw-collapsed" style="width:auto">
-<big>'''3. Enter a valid email address, check the agreement checkbox and click the Create Account button.'''</big>
+''3. Enter a valid email address, check the agreement checkbox and click the Create Account button.'''
 <div class="mw-collapsible-content">
 * '''[[File:Email_address1.png]]
@@ Line 42: / Line 42: @@
 <div class="toccolours mw-collapsible mw-collapsed" style="width:auto">
-<big>'''4. Log in with the email entered in the previous step and click the confirmation link in order to confirm the email address.'''</big>
+'''4. Log in with the email entered in the previous step and click the confirmation link in order to confirm the email address.'''
 <div class="mw-collapsible-content">
 * '''[[File:Confirmation_email.png]]
@@ Line 48: / Line 48: @@
 <div class="toccolours mw-collapsible mw-collapsed" style="width:auto">
-<big>'''5. Enter your name and a password for your account.'''</big>
+'''5. Enter your name and a password for your account.'''
 <div class="mw-collapsible-content">
 * '''[[File:Create_account_after_confirmation_email.png]]
@@ Line 54: / Line 54: @@
 <div class="toccolours mw-collapsible mw-collapsed" style="width:auto">
-<big>'''ER: The 'Welcome to Bugzilla' page is displayed.'''</big>
+'''ER: The 'Welcome to Bugzilla' page is displayed.'''
 <div class="mw-collapsible-content">
 * '''[[File:Welcome_to_bugzilla.png]]
@@ Line 85: / Line 85: @@
 *Make sure that the issue is not already logged
+=====Logging a new bug=====
 '''Step 1 of 3: Choose a product.'''
@@ Line 176: / Line 176: @@
 There's a detailed guide to making your bug as well formed as possible: the [https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines Bug writing guidelines] on MDN.
-====Many thanks to every contributor for all the hard work!====
 ==needinfo flag==
 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.
-(screenshot of individual bug with needinfo checked and dropdown menu open)
+<div class="toccolours mw-collapsible mw-collapsed" style="width:auto">
+'''Screenshot'''
+<div class="mw-collapsible-content">
+* '''[[File:Need_info.png]]
+</div></div>
 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.
@@ Line 189: / Line 190: @@
 You can see the needinfo flags you have requested of others and the ones requested of you in your [https://bugzilla.mozilla.org/page.cgi?id=mydashboard.html Dashboard].
-(screenshot of dashboard)
+<div class="toccolours mw-collapsible mw-collapsed" style="width:auto">
+'''Screenshot'''
+<div class="mw-collapsible-content">
+* '''[[File:Dashboard_screenshot.png]]
+</div></div>
 ==Dashboards==
@@ Line 198: / Line 203: @@
 ==Bug triage==
+[https://mozilla.github.io/bug-handling/triage-bugzilla Bug triage documentation]
 ==Products and components==
-Bugs in bugzilla.mozilla.org are organized into a hierarchy of categories.  Products are high level categories such as Firefox, FirefoxOS, Calendar, or Toolkit.
+Bugs in bugzilla.mozilla.org are organized into a hierarchy of categories.  Products are high level categories such as Core, Firefox, Firefox for Android, Firefox iOS, or Toolkit.
 This is the list of products on BMO: https://bugzilla.mozilla.org/describecomponents.cgi
@@ Line 255: / Line 262: @@
 ==tracking flags==
-''tracking-firefox-25?  Who's doing the tracking?  Should I set these flags? When and why?''
+''tracking-firefox-60?  Who's doing the tracking?  Should I set these flags? When and why?''
-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.  Flags of the form tracking-firefox-26 have a ?, +, or - associated.
+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.  Flags of the form tracking-firefox-60 have a ?, +, or - associated.
-For example, a [https://bugzilla.mozilla.org/buglist.cgi?f1=cf_tracking_firefox26&list_id=7974674&o1=substring&resolution=---&resolution=DUPLICATE&query_format=advanced&v1=%2B search for tracking-firefox-26 and "+"] currently shows around 50 bugs.
+For example, a [https://bugzilla.mozilla.org/buglist.cgi?f1=cf_tracking_firefox60&list_id=14022303&o1=substring&resolution=---&resolution=DUPLICATE&query_format=advanced&v1=%2B search for tracking-firefox-60 and "+"] currently shows around 20 bugs.
 If you would like to suggest a bug and its fix be considered (by release managers) for a particular release, mark it with that release and a question mark. This might be good to do for a bug that's been fixed in one release channel but needs to be uplifted to another.