← All articles
QA · 8 min read

Bug reports developers love: a template with real examples

A good bug report gets fixed faster. Here's our template, a bad vs. good example, and how we set severity and priority.

A bug that can't be reproduced doesn't get fixed. A bug report that takes a developer twenty minutes to understand gets postponed. The quality of bug reports directly affects how fast a team ships, so we treat writing them as a core QA skill, not paperwork.

The anatomy of a good report

FieldWhat to write
TitleWhat is broken, where, under what condition. Short and searchable
EnvironmentBuild/version, URL, device, OS, browser, account type
PreconditionsData or state needed before step 1
Steps to reproduceNumbered, minimal, one action per step
Expected resultWhat should happen, ideally with a link to the requirement
Actual resultWhat happens instead, including error text
EvidenceScreenshot, video, logs, network request (HAR), console errors
Severity / PriorityImpact on the product / urgency of the fix
FrequencyAlways, sometimes (3 of 10), once

Bad vs. good

A bad report:

Checkout doesn't work. I tried to buy something and it failed. Please fix ASAP!!!

The same bug, reported well:

Title: Checkout – “Pay” button stays disabled after applying promo code on mobile Safari

Environment: staging build 1.4.2 (#1287), iPhone 13, iOS 17.5, Safari
Account: registered user test.buyer+12@…, cart with 2 items ($64.00)

Steps:
1. Open /cart
2. Enter promo code SPRING10 and tap “Apply”
3. Tap “Checkout” and fill a valid address
4. Select “Card” as payment method

Expected: “Pay $57.60” button is enabled
Actual: button stays disabled; console shows
        TypeError: total.toFixed is not a function (checkout.js:214)

Frequency: 5/5 on iOS Safari; not reproducible on Chrome desktop
Evidence: video.mp4, console.log, HAR file attached
Severity: Critical (users can't pay)  Priority: High

The second version can be fixed without a single follow-up question. The console error even points the developer to the line.

Severity vs. priority

Severity describes the impact of a defect on the system. Priority describes how soon it must be fixed. They usually correlate, but not always, and the difference matters when planning.

Priority →Severity →Low severity · High priorityTypo in the brand name on the homepage;Wrong price format in an ad campaignHigh severity · High priorityUsers can't pay;Data loss, security hole
Severity and priority are different axes. Examples from real projects.

Our checklist before pressing “Create”

  1. Reproduced at least twice, ideally on a clean session
  2. Searched for duplicates
  3. Steps are minimal: removed everything not needed to reproduce
  4. One bug per report
  5. Title readable without opening the ticket
  6. Evidence attached and sensitive data hidden
  7. No emotions, no blame, only facts

Beyond the report

When a bug is fixed, QA verifies the fix on the same environment and runs a short regression around it. Recurring bugs get a root cause analysis: why did it happen, and which test, review or check would have caught it earlier? That question is how teams stop seeing the same type of bug twice.