# Bug report quality checklist

## Summary
- [ ] The title names the feature, condition, and observable failure.
- [ ] The report contains one main problem.

## Reproduction
- [ ] Preconditions identify the required account, state, and data.
- [ ] Steps are numbered, minimal, and repeatable.
- [ ] Exact values are included where they affect the result.
- [ ] Environment, build, and client details are present when relevant.
- [ ] Frequency states attempts and observed failures.

## Result and impact
- [ ] Expected and actual results are separate and observable.
- [ ] Impact identifies the affected user or business task.
- [ ] The report states whether a safe workaround exists.
- [ ] Severity follows the team definition.

## Evidence
- [ ] Attachments match the written reproduction steps.
- [ ] Logs, requests, queries, or timestamps contain useful context.
- [ ] Personal data, credentials, and secrets are removed or masked.
- [ ] Remaining uncertainty is stated clearly.