7 / 12 · Book 18 · The Art of the Bug Report← prev⊞ allnext →Get the book →
1.7Bug Report Anti-Patterns
| Anti-Pattern | Problem | Fix |
|---|---|---|
| "It doesn't work" | No actionable information | Require steps to reproduce, expected vs actual |
| Missing environment info | Cannot reproduce | Always include browser, OS, app version, environment |
| No attachments | Developer cannot see what you saw | Always attach screenshots, logs, HAR files |
| Duplicate bugs | Wastes developer time | Search before creating; link duplicates |
| Over-inflated priority | Everything is "Critical" so nothing is | Reserve Critical for system-down scenarios |
| Bug report in Slack | Lost in conversation, not tracked | File in Jira; link from Slack if needed |
| No reproduction steps | Developer spends hours trying to reproduce | Number each step explicitly |
| Assigning blame in the description | Creates adversarial relationship | Describe the problem, not who caused it |
| Screenshots without context | "What am I looking at?" | Annotate screenshots with arrows and labels |