Defect board › Bug Reports
Bug Reports
Reports logged under Bug Reports.
Bug Reports
What a Bug Report Actually Promises the Reader
SevThe magnitude of harm the defect causes when it occurs, judged independently of scheduling or business context.
PriThe team's ordering decision about when the defect will be worked relative to everything else in the queue.
TriageThe routing decision made at review: accept, defer, duplicate, needs-info, not-a-bug, or cannot-reproduce, with an owner attached.
StatusThe report's current position in the workflow, from new through triaged, in progress, fixed, verified, or closed.
A bug report is often treated as a container for a complaint.
Bug Reports
Your Bug Title Is the Only Part Anyone Reads
SevThe degree of damage a defect causes to users, data, or system stability, judged independently of when anyone plans to fix it.
PriThe team's scheduling decision about when a defect will be addressed, balancing severity against business context and available capacity.
TriageThe routing decision made at review that assigns ownership, priority, and next action to a defect report.
StatusThe current position of the report in the workflow, such as new, confirmed, assigned, in progress, resolved, or closed.
Most bug reports are read once, in a hurry, by someone who is already behind on something else.
Bug Reports
Stop Filing Vague Bugs: Write the Symptom, Not Your Theory
SevThe degree of damage or disruption a defect causes to users, data, or system behavior, independent of when it will be fixed.
PriThe team's scheduling decision about when to fix a defect relative to other work, which can differ from severity.
TriageThe routing decision made during defect review that assigns ownership, severity, priority, and next action.
StatusThe current stage of the defect in the workflow, such as new, triaged, in progress, fixed, verified, or closed.
A bug report is not a place to show how clever you are at guessing root cause.
Bug Reports
One Bug Per Ticket: Why Bundled Reports Rot in the Backlog
SevHigh: a bundled report can hide a crash or data-loss defect among minor cosmetic issues, so the true damage of the worst defect is obscured and may be underestimated.
PriHigh for triage and splitting: the report should be reviewed early so the serious defect is not delayed behind unrelated low-impact items.
TriageRoute the report to the owning component, split it into separate tickets for each distinct defect, assign severity and priority per defect, and close or rewrite the original as a tracking item if needed.
StatusNew or reopened until split; then each split ticket moves to triaged, assigned, or closed as appropriate.
A bug report is a unit of work, not a diary entry.