Marketplace/Bugs

So, you found a bug in Marketplace! Now, what?

Bug Templates

• template to file Marketplace bugs
• template to file payments bugs
• link to file operational bugs

Triage

We use bug severity and priority to categorize bugs in order of their importance. Remember that p1-normal bug takes precedence over p4-critical.

Bug Severity

Severity is how you describe the impact of the bug on the target audience.

• Blocker: Bugs blocks the user from doing anything on the website. Example: a) Marketplace homepage loads a 500. b) App installs don't work.
• Critical: Bug affects website/app functionality in a major way. Example: a) FxA is down which blocks the user from using many features on the site but can still browse and install apps. b) Search returns no results.
• Major: An oft-used functionality on the site is broken. Example: a) A link on the homepage is a 404 b) User cannot add reviews.
• Normal: the bug may cause minor loss of functionality or causes a general degradation of user experience. Example: a) Inaccurate or missing user messaging b) Review count incorrect.
• Minor: the kind of bugs we refer to as "polish". Example: a) Button is a few pixels too big b) Wrapping/overflow issues.
• Trivial: No bug is trivial. Do not use this :)

Bug Priority

Priority is how you define the urgency with which a bug should be resolved. This field describes the importance and order in which a bug should be fixed compared to other bugs. This field is utilized by developers to help prioritize their work to be done where P1 is considered the highest and P5 is the lowest. Other factors may influence the order of the work that actually gets performed including bug dependencies, complexity of the task, and availability of resources across Marketplace teams.

References

• https://bugzilla.mozilla.org/page.cgi?id=fields.html
• https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines