---
name: Bug Reporting
description: Report bugs so they can be reproduced.
---
# Bug Reporting

A bug report a developer can't reproduce is one they can't fix. The report's job is to make the bug happen on the developer's machine, not to vent.

## Required fields
- **Title.** One line that summarizes the symptom. "Checkout fails with 500 when cart has >10 items" — searchable and specific.
- **Steps to reproduce.** Numbered, exact, starting from a known state. "1. Logged in as user X. 2. Added 11 items. 3. Clicked checkout."
- **Expected vs actual.** What should have happened, what did.
- **Environment.** Browser/OS/version, build number, account role. Bugs that depend on these are unfindable without them.
- **Evidence.** Screenshot, video, network error, stack trace. Worth a thousand words of description.

## Severity vs priority
- Severity: how bad is it (crash > cosmetic).
- Priority: how soon to fix (a cosmetic bug before launch is high priority).