Bug report template generator
A clean bug report saves engineers hours of guessing. Fill in the fields below and copy a ready-to-paste markdown ticket. Works in Linear, Jira, GitHub, Notion, or anywhere markdown renders.
Name the symptom, not the cause.
Browser, OS, device, app version. Prefilled from your browser.
Optional.
# <bug title> **Severity:** Medium ## Steps to reproduce 1. 2. 3. ## Expected behavior _What you expected to happen._ ## Actual behavior _What actually happened._
How to use this tool
- 1Fill in as many fields as you can: title, severity, environment, repro steps, and what you expected vs what actually happened.
- 2The markdown preview updates as you type.
- 3Click the copy button to grab the formatted ticket and paste it into your tracker.
About this tool
Most bug reports fail engineers in the same way: missing repro steps, no environment info, and a title that hides the actual symptom. This template covers the fields that change a “works on my machine” thread into a single fix. It is built around the same structure you’d use in Linear, Jira, or GitHub Issues.
Related tools
Website pre-launch checklist
A 50+ item pre-launch checklist covering content, SEO, performance, accessibility, analytics, and legal. Save your progress in the browser.
Website QA checklist
Hands-on QA checklist for testing a website before sign-off. Cross-browser, responsive, forms, links, and content checks.
Website accessibility (WCAG) checklist
Practical WCAG 2.2 AA checklist for designers and developers. Color, keyboard, screen reader, forms, and content checks.
Website handoff checklist
Hand a finished website over to a client without follow-up panic. Credentials, training, docs, and post-launch support.
Frequently asked questions
Short answers to what people ask most.
What makes a good bug report?
Where can I paste the output?
How do I choose a severity?
Do you save what I type?
Reviewing work with your team?
Pin comments directly on a live website or design — no extension, no setup.