Severity vs priority
Updated 2026-11-12 · 2 min read
Severity measures the damage a defect does to the product. Priority measures how urgently the business wants it fixed. They often move together but not always, and the examples below are the ones interviewers want to hear.
The difference in one table
| Severity | Priority | |
|---|---|---|
| Question it answers | How much does this defect hurt the system? | How soon should we fix it? |
| Based on | Technical and functional impact | Business urgency, deadlines, number of users affected |
| Usually set by | Tester (proposed) | Product owner or manager |
| Changes over time? | Rarely; the defect is what it is | Yes, with release dates and business needs |
| Typical levels | Critical, major, minor, trivial | High, medium, low (or P1, P2, P3) |
Four examples that cover every combination
High severity, high priority. The payment page crashes when the user taps "Pay". Customers cannot buy anything. Fix now.
High severity, low priority. A rarely used admin report crashes when exported for a date range that spans more than ten years. The feature is broken, but only one person has ever used it, and there is a workaround (smaller ranges). It goes into a later release.
Low severity, high priority. The company name is misspelt in the header of the home page the day before a launch event. Nothing is functionally broken, but it is the first thing every visitor sees. Fix before the event.
Low severity, low priority. A tooltip on a settings page is missing a full stop. Fix it when someone is in that file.
How to answer in an interview
Give the definition in one sentence each, then pick the second or third example above, because they show you understand that the two are independent. Finish with who decides: "I propose severity based on impact, and the product owner decides priority based on business needs."
Likely follow-up: Give an example of a defect that starts as low priority and becomes high. A cosmetic issue on a page that a new marketing campaign is about to send millions of visitors to. Nothing about the defect changed; the business context did.
In a bug report
Fill in both fields and explain them in the description. A report that says "Severity: Major, Priority: Low" without a reason leaves the developer guessing. Use the bug report template.
Quick answers
Can a defect have high severity and low priority?
Yes. A crash in a rarely used admin report is high severity because the feature fails completely, but if almost nobody uses it the business may schedule the fix for a later release.
Can a defect have low severity and high priority?
Yes. A spelling mistake in the company name on the home page does no technical damage, but it hurts the brand, so it is fixed immediately.
Who decides severity and who decides priority?
Testers usually propose severity because it describes the technical impact. The product owner or project manager decides priority because it depends on business needs and deadlines.
Want a project you can show in interviews?
The portfolio project kit walks you through testing a deliberately buggy app with Selenium or Playwright and API tests, then explaining it. The app itself is free.