When a bug lands in the backlog, two fields appear on every ticket: Severity and Priority. They look alike, they are often filled with the same number, and the difference gets lost in the rush of triage. Understanding the distinct purpose of each field helps teams ship reliable software without stepping on business deadlines.
Severity – Technical impact only
Severity measures how bad the impact is on the system. It is a technical assessment of damage: does the defect crash the application, corrupt data, or merely cause a cosmetic glitch? Because it is a purely technical gauge, the person who knows the code‑base best—usually a QA analyst or developer—sets it. The decision is based on what actually breaks, not on who is complaining or when the fix is needed.
Priority – Business urgency
Priority answers how soon the defect should be fixed. It is a business‑oriented measure of urgency that takes release schedules, customer commitments, and market timing into account. Product owners or project managers set priority, weighing the defect against current business goals. A low‑severity typo can be a P1 if it appears in a high‑visibility demo, while a critical crash in a rarely used admin screen might be a P4.
They Can Diverge
The two dimensions are independent, so mismatches are common:
- High severity, low priority – A crash in a back‑office tool that only a handful of internal users touch. The system is broken, but fixing it can wait until the next sprint.
- Low severity, high priority – A typo on a slide that the CEO will present tomorrow. The visual flaw is minor, yet the timing makes it urgent.
Recognizing these scenarios prevents the “one‑size‑fits‑all” triage where every bug is labeled “high” for both fields.
Common Combos
Typical pairings help teams communicate expectations quickly:
| Severity | Priority | Example |
|---|---|---|
| Critical | P1 | Payment processing fails in production – the business cannot operate. |
| Minor | P3 | Misaligned padding on a settings page – harmless but worth fixing in a future release. |
These combos act as shorthand, but they should never replace a thoughtful assessment of each dimension.
Do / Avoid
Do
- Set severity based solely on technical impact; ignore politics or stakeholder pressure.
- Let priority reflect the business context, including timing, market windows, and stakeholder commitments.
- Revisit priority whenever release dates shift or new information emerges.
Avoid
- Defaulting severity and priority to the same value without analysis.
- Allowing the loudest stakeholder to override the technical severity assessment.
- Skipping re‑triage as the project landscape changes.
Takeaway: Keep severity and priority separate, let each answer its own question, and your bug backlog will stay both technically sound and business‑aligned.
Top comments (0)