How to write a bug report developers can act on
The simple structure we use for every issue we report, so developers can act on it straight away.
A vague bug report costs everyone time. The developer asks questions, the tester digs for details, and the fix waits. A clear report removes that back-and-forth.
Start with a title that says what is wrong
Describe the problem, not the symptom. “Coupon can be applied twice at checkout” beats “Checkout broken”.
Give steps anyone can follow
- Start from a known state: logged out, empty cart, a named test account.
- Number every step and keep each one to a single action.
- Include the exact data you used, such as the coupon code and the browser.
Say what you expected and what happened
Two short lines are enough: what should have happened, and what actually did. Add the numbers whenever there are numbers.
Add evidence and context
A screenshot or a short recording removes doubt. Note the environment (staging or production, browser, device) and how often it happens.
Rate the severity honestly
A blocker stops a critical flow; a minor issue is cosmetic. Honest severity helps your team plan the release, and it builds trust in every report that follows.