Business analysis glossary
Defect Priority
What it is
Defect priority says how soon a defect should be fixed, based on business needs, deadlines and impact, for example fix now, fix this release or fix later. It is set by the business or product owner, while severity is usually set by the tester based on technical impact.
Why it matters
Severity and priority often differ. A spelling mistake in the company name on the home page is low severity but high priority, while a crash in a rarely used admin report may be high severity but lower priority. Separating the two helps teams fix what matters most first.
Example
In triage, a cosmetic defect shows the insurer's name misspelled on every policy document. Its severity is low, but the product owner sets its priority to fix now, because the documents go to thousands of customers next week. A crash in an internal archive screen is high severity but is scheduled for next sprint.