BMO/How to Use Bugzilla: Difference between revisions

BMO/How to Use Bugzilla (view source)

Revision as of 18:47, 29 November 2016

599 bytes added , 29 November 2016

→‎Bugzilla Helper: Updates to bug-filing steps

Mcote

Confirmed users

1,927

edits

@@ Line 26: / Line 26: @@
 '''Step 1 of 3: Choose a product.'''
-Where is your bug? It might in Firefox, Firefox OS, or some other product. Click the one that is your best guess.
+Depending on what you are reporting, there may be better options than Bugzilla.  The top section lists some of this, including Mozilla's [https://support.mozilla.org/ Support] and [https://input.mozilla.org Feedback] sites.
+If your bug is in a Mozilla product, select it from the list under "None of the above; my bug is in:". It might in Firefox, Firefox for Android, or some other product. Click the one that is your best guess.
 [[File:BMO-bugzilla-helper1.png]]
@@ Line 32: / Line 34: @@
 '''Step 2 of 3: Summarize the bug.'''
-Write a short summary of your bug. It should be specific, clear, descriptive, and searchable. Think of it as a title for the bug.
+Write a short summary of your bug. It should be specific, clear, descriptive, and searchable. Think of it as a title for the bug. There is also a specific option for translation errors.
 [[File:BMO-bugzillahelper2a.png]]
@@ Line 42: / Line 44: @@
 There is good news and bad news here! The bad: there isn't necessarily an easy way to judge if your bug has already been filed. It takes a little bit of reading and thought. The good news is that scanning this list can help you avoid making a duplicate bug, and keep you informed on related issues.
-For this list of similar issues, you may be able to tell from one of the summaries that your bug has already been reported by someone else. Or, to look deeper into the similar bugs, click on a bug number in the left-hand column, opening it in a new tab. Maybe you can tell that it's the same as the bug you intended to file. In that case, you can click "Follow" in the rightmost column if you want to be cc-ed on changes that happen to the bug.
+For this list of similar issues, you may be able to tell from one of the summaries that your bug has already been reported by someone else. Or, to look deeper into the similar bugs, click on a bug number in the left-hand column, opening it in a new tab. Maybe you can tell that it's the same as the bug you intended to file. In that case, you can click "Follow bug" in the rightmost column if you want to be emailed when there are updates to the bug.
 [[File:BMO-bugzillahelper2c-following.png]]
-If you don't find your bug, you are now ready to create a new bug report in Step 3.
+If you don't find your bug, you can create a new bug report by clicking "My issue is not listed".
 '''Step 3 of 3: Describe the bug.'''
@@ Line 55: / Line 57: @@
 * "What should have happened?" where you explain the correct or desired behavior.
-Once you're used to filing bugs, you can switch to the advanced bug entry form.
+There are a few other options that may apply to your bug.  In particular, if you believe it is a security issue, check the appropriate box.
+Once you're used to filing bugs, you can switch to the [https://bugzilla.mozilla.org/enter_bug.cgi?format=__default__ advanced bug entry form].
-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.
+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.
 ==needinfo flag==