v1.0
Reference Guide

How to assign bug priorities

A practical framework for choosing the right priority for every bug you enter. Match impact against urgency, then pick a level.

The four levels 4 tiers

Critical Fix now

System is broken. Users cannot work, data is at risk, or the product is exposed. Stop everything, emergency release.

  • App crashes or is completely unusable
  • Data loss or corruption
  • Security vulnerability exposed
  • Billing or payments fail
Example
"Unable to login with password, only SSO works"
Auth is broken for a large user group. No workaround for most.
High Fix this sprint

Important feature is broken or many users are affected. Workaround exists but it is painful. Planned for this sprint.

  • Major feature broken but app overall works
  • Large percentage of users affected
  • Blocks a common workflow
  • Severe performance degradation
Example
"Proto returns 400 during execution"
Core flow fails but users can retry or use another path.
Medium Fix soon

Annoying but not blocking. Users can get their work done. Scheduled for the next one or two sprints.

  • Feature works but has quirks
  • UI/UX issues that confuse users
  • Minor data inconsistencies
  • Easy workaround is available
Example
"Draft button stays visible after saving a ticket"
Confusing UI, but the ticket still saves correctly.
Low Fix when possible

Cosmetic or rare edge cases. No real impact on users or the product. Fixed during maintenance windows.

  • Cosmetic, no functional impact
  • Rare edge cases
  • Minor text or formatting
  • Feature requests disguised as bugs
Example
"Wrong hover color on app cards"
Visual detail only, no user impact.

Quick decision tree 5 steps

1 Can users complete their primary task? No → Critical / High
2 How many users are affected? Most → bump up · Few → bump down
3 Is there a reasonable workaround? None → bump up
4 Does it touch security or data integrity? Yes → Critical
5 Does it block other work or releases? Yes → High

Your tracker, by the numbers 846 issues

Bug Tracker main issues table showing 200 of 846 records

Click to enlarge · This is the live Issues table from your Bug Tracker app

Pro tips for consistent triage
Start lower, escalate later Easier to bump a bug up than to explain why everything is critical.
Consider business context A low bug during a launch can be high. Reassess at milestones.
Document your reasoning Add a note on why you picked the priority. Future you will thank you.
Triage as a team Priority should reflect consensus, not one person's gut feel.