Bug report.
A structured document that describes a software defect well enough for someone else to reproduce, prioritize, and fix it. The minimum useful contents: title, severity, steps to reproduce, expected behavior, actual behavior, environment.
The minimum viable bug report
Title (one line). Severity (low/medium/high/critical). Repro steps (numbered). Expected behavior. Actual behavior. Environment (browser, OS, viewport, URL).
Why most bug reports fail
Missing repro steps and missing environment. "It does not work" with no URL and no browser is unactionable. Screendog auto-captures both.
Frequently asked
How long should a bug report be?
Short enough that an engineer reads the whole thing. The structure carries the weight; the prose should be minimal.
Try Screendog free.
5 recordings on the free trial. Real Linear, GitHub, Notion, Slack, and Jira filing. No credit card.
Start a workspace — free