Defect board › Triage
Triage
Reports logged under Triage.
Triage
Triage Is a Decision Meeting, Not a Backlog Tour
SevA measure of the defect's impact on users or systems, such as crashes, data loss, or blocked workflows.
PriThe team's decision about when to fix the defect, balancing severity, business goals, and available resources.
TriageThe routing decision made during a review meeting: accept, defer, duplicate, reject, or request more information.
StatusThe current stage of the report in the workflow, for example new, triaged, in progress, resolved, or closed.
Triage is often mistaken for a backlog tour, where a team walks through a list of open defects and makes quick judgments.
Triage
The Triage Queue Dies When Nobody Owns the Sorting
SevThe degree of damage a defect causes to users or systems, independent of scheduling.
PriThe team's intended order and timing for fixing a defect relative to other work.
TriageThe routing decision made during review: accept, defer, reject, duplicate, or needs more information.
StatusThe defect's current position in the workflow, such as new, triaged, in progress, or closed.
A triage queue is not a list of bugs.
Triage
Deduplicating Bugs Without Losing the Original Report
SevThe degree of harm a defect causes to users, data, or system stability, judged independently of when it will be fixed.
PriThe team's scheduling decision about when to fix a defect relative to other work, which may or may not track severity.
TriageThe periodic routing review where a defect is confirmed, classified, assigned, and either accepted into a backlog or closed with a reason.
StatusThe current position of a report in the workflow, such as new, confirmed, duplicate, in progress, resolved, or closed.
Duplicate bug reports are not a failure of the reporting process.