Have you ever wondered as a contributor how the teams find out about some of the issues that come up after a new release? Or maybe that weird thing that this one product did in that weird question you answered yesterday? Well let's admit it, sometimes products break and new ways to use them come up all the time. Or maybe you are that user who has looked under the hood of plenty of applications and want to know how to tell "them" about it. Whatever the case, this article will give a few guidelines on how to communicate that weird situation or error code you saw in that one question and translate it into something an engineer can work from.
This is where Bugzilla comes in. Bugzilla is the tool that Mozilla uses to talk about the bugs in all of the products that Mozilla has ever created, for the most part. But our neighbors have an ecosystem just like the forum. All of its wonders will be found in due time. Just like in the cave of wonders, for now, do not touch anything but the lamp!
[add screenshot of bugzilla]
This is Bugzilla, and below is a bug form:
[add a screenshot of File a bug]
If you are looking for an existing bug these are the search functions:
[screenshot of the search functions]
There are also some tips and tricks that can help you visualize the dashboard or keep track of the bugs that you have filed.
How to save an advanced search:
How to save a template to create a bug:
Is there a bug that already exists? Please add the thread for tracking purposes or in the "See Also:". This way – when the bug is fixed or there is an update – you can easily find the thread to let the user know what is happening with their bug.
Please keep this in mind before you enter Bugzilla of wonders:
So you are already good at this stuff: asking for what the user is seeing on their computer screen or phone and how to show them the basics. Now for the more technical stuff.
Troubleshooting information on about:support
Questions you can ask yourself to frame the bug and description:
Mozilla has a wiki page that walks a first time user on how to write an effective bug. Just like SUMO, there is some lingo and guides to being amazing. Please see: How to write an amazing bug.
Guidelines on how to get help:
Support: If you find the bug matching their issue:
For example, this is not a standard:
Currently it looks like this bug depends on a [priority] bug, which is the highest priority. I have voted on this bug and recommend you check for updates on this issue on this bug and vote as well because it is affecting you. In the meantime we are happy to help find a work around.
We are very sorry for the inconvenience. If there are any other questions in the meantime please do not hesitate to ask.
How to gather troubleshooting info
This is a template you can use when filing a bug:
Please type a brief introduction to the bug and/or background if it would be helpful to the Engineering and QA teams. Not required for all bugs - some of them are simpler and straight forward.
STEPS TO REPRODUCE:
EXPECTED RESULTS: Describe what you expected to happen.
ACTUAL RESULTS: Describe what actually happened.
Please let me know if there is any information I could provide to help with the investigation and troubleshooting of this issue.
What a Firefox OS status of a bug entails:
Firefox OS bugwork
Magic link for description of bug components:
Now you start to file some bugs, but you want to do a little more. Check if the bugs have been assigned? Have there been any updates? This is a big part of support.
Getting to know bug components:
Check out the component descriptions if you have questions. Click this link and choose a product.
Link for description of all bug components:
You want to be one of the bugmasters?
... Or maybe you want to find the right people to take a look at a bug: MDN’s guide to Bugzilla will tell you all about the etiquette, how to fix it and where to find the right people.
I know how to fix the bug, how can I write a patch?
You can always reach out for help, this is not a standard just some recommendations. If you have any other "grey areas" let's talk about it.