All glossary terms
Verify
Severity vs priority
Two independent axes for triaging a defect: severity measures technical impact — does it crash, corrupt data, or block a workflow — while priority measures business urgency, how soon it must be fixed relative to other work. A homepage typo can be low-severity but high-priority; a crash in an unused admin tool can be high-severity but low-priority.
Keeping the two axes separate prevents two failure modes: treating every high-severity bug as drop-everything urgent (burning the team on rare crashes), and treating every visible-but-trivial bug as critical (the loud-customer effect). A triage matrix that plots severity against priority gives a defensible, repeatable order of work.