Q5 of 14 · JIRA
What is the difference between Priority and Severity in JIRA bug reports?
JIRAJuniorjirapriorityseveritybug-management
Short answer
Short answer: Severity describes how badly the bug impacts the system (technical impact). Priority describes how urgently it needs to be fixed (business urgency). A bug can be high severity but low priority, or low severity but high priority.
Detail
Severity — the technical degree of damage:
- Blocker/Critical — application crashes, data loss, security vulnerability, no workaround
- Major — core functionality broken, workaround exists but is painful
- Minor — non-critical functionality affected, acceptable workaround
- Trivial — cosmetic issue, typo, minor UI misalignment
Priority — the business urgency of fixing it:
- P1 — must be fixed before the next release / immediately
- P2 — fix in current sprint / release
- P3 — fix in next sprint
- P4 — backlog, fix when convenient
How they can diverge:
| Scenario | Severity | Priority |
|---|---|---|
| App crashes when admin changes font size (1 user affected) | Critical | Low |
| Checkout button label says "Purcase" instead of "Purchase" | Trivial | High (visible to all users on the main conversion path) |
| CSV export for finance team has wrong decimal separator | Major | High (P1 if month-end reporting is due) |
Who sets each:
- QA sets Severity based on technical assessment.
- Product Owner or the team collectively sets Priority based on business context (release date, user impact, revenue).
In many teams these are merged into a single Priority field — but understanding they're conceptually different is what interviewers test.
// WHAT INTERVIEWERS LOOK FOR
The divergence examples. Who sets each (QA vs PO/business). Concrete examples where they differ — these are the most memorable part of the answer.