A bug report is a piece of writing with one job: let someone who was not there reproduce the problem. Most of them fail at that, and the cost is paid in back-and-forth.
The four lines that matter
- What you did, as numbered steps someone else can follow
- What you expected to happen
- What actually happened
- Device, OS version and build number
One report, one bug
Three problems in one ticket means two get forgotten. Split them, even when they seem related - especially when they seem related.
Say how often
Every time, one in five, or once and never again are three different bugs with three different investigations. Guessing wastes a day.
Attach the boring evidence
A screen recording beats a paragraph. A log excerpt beats a screenshot of a log. The request id beats all of them.
