Bug reporting · 5 min
What belongs in an evidence-backed bug report
The minimum context that turns a suspicious outcome into something a team can reproduce and act on.
01
Show the path, not only the symptom
A screenshot proves that a state existed. It rarely explains how the user reached it. Pair visual evidence with the action sequence and starting conditions.
- ●Environment and build
- ●Starting URL and account state
- ●Exact user-facing actions
- ●Observed and expected behavior
- ●Screenshot or recording
- ●Severity and user impact
02
Separate observation from interpretation
Describe what the interface did before assigning a cause. The frontend may show the symptom while the underlying problem lives in state management, an API response, or product rules.
03
Make verification cheap
The best report gives another person enough information to reproduce the problem quickly, decide whether it matters, and verify the fix using the same path.