Skip to content

Bug severity vs priority

Severity says how bad a bug is. Priority says when you will fix it. They are related, and they are not the same number.

Written by the BugBoard team. 4 minute read. Updated 14 November 2026.

Two questions, two answers

Severity is about the bug: how much damage it does when it happens. The person who reports or reproduces it can usually set it. Priority is about your plan: how soon the team fixes it, given everything else. The person who owns the plan sets it, and it can change next week without the bug changing at all.

A four-level severity scale

LevelMeaningExample
S1 CriticalData loss, a security hole, or the product is down for many people.Saving a task deletes the comments.
S2 MajorA main feature does not work and there is no sensible workaround.Nobody can sign in with Google.
S3 MinorSomething is wrong, and there is a workaround or it touches few people.The calendar view shows the wrong month name for one locale.
S4 TrivialCosmetic, or a rare edge case with no real effect.A button is two pixels off.

Priority is an order of work

Keep priority to three or four values and define each by time: fix now (drop what you are doing), fix this cycle, fix when there is room, will not fix. Words such as “urgent” and “important” mean different things to different people. A date does not.

Five cases where they disagree

CaseSeverityPriorityWhy
The app crashes on a browser version nobody on your plan usesS1LowTerrible when it happens and almost never happens to you.
A typo in the price on the pricing page, the day of a launchS4Fix nowTrivial bug, high cost of leaving it up.
An export drops the last row, and a customer has a deadline tomorrowS2Fix nowThe deadline sets the order, not the scale.
A report is slow for accounts with more than 50,000 tasks, and you have noneS3LowReal, and not yet yours.
A security bug found by a customer in a feature behind a flagS1Fix this cycleThe flag limits exposure; the cycle still has a limit.

Rules that keep it honest

  • Set severity from what happened, not from who reported it.
  • Never raise priority to get attention. If it matters, say what it costs.
  • Review priority when the plan changes, and leave severity alone unless you learn more about the bug.
  • In BugBoard, a task has a priority field; a tag such as severity:major records severity.