Bug report template.
A minimal Markdown template that works in Linear, GitHub Issues, Jira, Notion, Slack, or any plain-text editor. Copy, paste, fill in. This is the same structure Screendog auto-fills from a recording.
The template
### Title
[One sentence — what is broken from the user's POV]
### Severity
- [ ] critical (blocks all users)
- [ ] high (blocks key flow for some users)
- [ ] medium (degraded experience)
- [ ] low (cosmetic / edge case)
### Steps to reproduce
1.
2.
3.
### Expected behavior
### Actual behavior
### Environment
- Browser:
- OS:
- Viewport:
- URL:
- Logged-in user / role:
### Evidence
- Screen recording: <link>
- Console errors:
- Network failures:
When to use which severity
Critical: revenue or auth broken site-wide. High: a major flow is broken for a real cohort. Medium: a real annoyance with a workaround. Low: cosmetic or rare-edge.
Frequently asked
Why severity instead of priority?
Severity is what the user feels; priority is what the team decides to do about it. Capture severity at file-time; let the engineering manager set priority during triage.
Try Screendog free.
5 recordings on the free trial. Real Linear, GitHub, Notion, Slack, and Jira filing. No credit card.
Start a workspace — free