Template
Write a bug report someone can use
A symptom is an observation. Its cause is still a hypothesis.
Before you use it
- Use when
- You need another person to investigate a reproducible work-system problem.
An idea to explore.
Try this idea.
Inspect the example, try the idea in your situation, then check your next move.
A template to use
Context and version: ___. Smallest reproduction steps: ___. Expected result: ___. Observed result and evidence: ___. Suspected cause, if any: ___. Acceptance check for the fix: ___.
Why it matters
Give the investigator a path from the conditions to what you actually saw. Separate expected behaviour, observed behaviour and your suspected explanation. If the failure happened once, say so; do not invent reliable reproduction. The acceptance check describes the behaviour a fix must restore.
An example
A browser shows an old address after saving. You record the version and one failed attempt; caching remains a suspicion.
Check your result
Can another person distinguish what happened, what should happen and what still needs testing?
Keep this limit in mind
- Remove credentials and unnecessary personal or customer data from screenshots, logs and examples.
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Connected ideas
Use beforeSeparate severity from priority
Evidence and sources (1)
This report template keeps expected behaviour, observed behaviour and suspected cause in separate fields.
Editorial design and source provenance only. No causal benefit, percentage improvement or validated intervention is claimed. Access: full_structured_record; 2026-10-11. Registered first-party project text; template provenance, not an efficacy study.
Write a bug report someone can use — Brali source record · Selected template fields
All sources (1)
Edition and review
Version 0.1.0 · Published
Agent review: Agent editorial and scoped evidence review · 2026-10-11