Defect board › Severity & Priority
Severity & Priority
Reports logged under Severity & Priority.
Severity & Priority
Severity Is the Damage, Priority Is the Schedule
SevHow much damage the defect causes when it occurs: the scope of affected users, the depth of the failure, whether data is corrupted or lost, whether a workaround exists, and whether the failure is silent or visible.
PriWhen the team intends to fix the defect relative to other work: the scheduling decision that weighs severity against release timing, customer commitments, effort, and risk.
TriageThe routing decision made at review: confirm, duplicate, defer, downgrade, escalate, or reject, each with a recorded reason and an owner.
StatusWhere the report sits in the workflow: new, confirmed, triaged, assigned, in progress, fixed, verified, closed, or reopened.
Every defect report carries two separate judgments, and confusing them is one of the most common sources of friction between testers and engineers.
Severity & Priority
Mixing Severity and Priority Guarantees a Broken Backlog
SevThe intrinsic measure of how much damage the defect does when it occurs in the product: data loss, corruption, crash, security exposure, or degraded function, judged independently of business timing or release plans.
PriThe scheduling decision about when the team intends to fix the defect relative to other work, driven by release timing, customer commitments, and business impact rather than by the defect's raw damage.
TriageThe routing decision made at review that assigns severity, sets priority, names an owner, and moves the report into a queue or back to the reporter for missing evidence.
StatusThe position of the report in the workflow, such as new, triaged, assigned, in progress, fixed, verified, or closed, reflecting the current state of the work rather than the defect's importance.
A backlog breaks in a quiet, specific way.
Severity & Priority
A Cosmetic Bug Can Still Be Your Top Priority
SevHow much damage the defect causes to users, data, or system behavior; a cosmetic issue may have low severity if it only affects appearance without blocking function.
PriWhen the team intends to fix the defect relative to other work; a cosmetic bug can be high priority if it damages trust, revenue, or a key user flow.
TriageThe routing decision made during review: whether to fix now, schedule later, defer, or close, based on severity, priority, and context.
StatusThe current stage of the report in the workflow, such as new, triaged, in progress, fixed, verified, or closed.
A cosmetic bug is easy to dismiss.
Severity & Priority
Data Loss Outranks a Crash Only Sometimes
SevThe degree of harm a defect causes to data, users, or system integrity, independent of when it will be fixed.
PriThe team’s scheduling decision about when to address a defect relative to other work.
TriageThe review meeting or routing step where a defect is assessed, assigned a severity and priority, and sent to the right owner or backlog.
StatusThe current stage of the defect report in the workflow, such as new, triaged, assigned, in progress, fixed, verified, or closed.
Data loss and crashes both feel urgent, but they are not the same kind of urgent.