Bug report template generator (free, no signup)
Fill in what happened and this free bug report template generator gives you a clean, structured report in Markdown. Steps to reproduce, expected and actual results, environment, and space for a screenshot, the console error, and the failed network call. Copy it in one click and paste it into GitHub, Linear, Jira, or a message to your team.
Generator
Build your bug report
Environment
# Save button does nothing on the settings page
## Steps to reproduce
1. Open the settings page
2. Change the display name
3. Click Save
## Expected result
The new display name is saved and a confirmation appears.
## Actual result
The page reloads and the old name is still shown. No message appears.
## Environment
- Browser: Chrome 120
- OS: macOS 14.2
- App version: 2.3.1
## Screenshot
[Attach a screenshot of the problem]
## Console error
```
TypeError: cannot read properties of undefined (reading 'id')
at saveSettings (settings.js:214)
```
## Failed network call
```
POST /api/settings 500 Internal Server Error
```Add the repository as owner/repo, for example octocat/hello-world.
Why it matters
What makes a good bug report
A good bug report gives whoever picks it up, a developer or a coding agent, enough to reproduce the problem and fix it without a single follow-up question. That means a clear title, the exact steps to reproduce, what you expected, what actually happened, and the environment it happened in. Add a screenshot, the console error, and the failed network call, and a vague "it broke" becomes something someone can act on straight away.
This bug report template covers each of those parts so nothing important gets left out:
- Title. One line that says what is broken and where.
- Steps to reproduce. The shortest path that triggers the problem, numbered.
- Expected and actual results. What should happen next to what really happens.
- Environment. Browser, operating system, and app version, so it can be reproduced.
- Evidence. A screenshot, the console error, and the request that failed.
If the steps are the part you are stuck on, the steps to reproduce generator builds that section on its own, with the frequency and environment included. For the evidence, the console log cleaner turns a raw console paste into a deduped, grouped log ready for the console error section, and the HAR file sanitizer scrubs cookies and tokens out of a Network-tab recording before you attach the failed request. Once the report is written, the bug severity and priority calculator sets the triage labels and writes the justification for the ticket. And when the report reads right, the buttons under the output send it straight to GitHub or Linear as a prefilled issue, no retyping.
For coding agents
Bug report template for AI coding agents
A coding agent reads a bug report differently from a developer. It needs the title, steps to reproduce, expected result, and actual result in separate, predictable headings so it can map the report to a code path and act on it. The console error and the failed network call go in their own sections, not buried in prose where the agent has to parse them out.
This is the format. The raw Markdown is at https://quell.sh/templates/bug-report-for-agents.md, so build scripts and agents can fetch it directly:
curl https://quell.sh/templates/bug-report-for-agents.md
Template:
# [Title: what is broken and where] ## Steps to reproduce 1. [Starting state] 2. [Action taken] 3. [Where it fails] ## Expected result [What should happen] ## Actual result [What actually happened] ## Environment - Browser: [e.g. Chrome 120] - OS: [e.g. macOS 14] - App version: [e.g. 2.3.1] ## Evidence - Screenshot: [attached / not available] - Console error: [paste here] - Failed network call: [e.g. POST /api/save 500]
The Quell widget captures all of this automatically from users’ browsers, with the console error and failed network call already included. Agents reading captured reports through the Quell MCP server get the same structured format without anyone filling in a form.
FAQ
Bug report template questions
What is a bug report template?
A bug report template is a reusable structure for writing up a software problem. It prompts you for the title, the steps to reproduce, the expected and actual results, and the environment, so every report you file has the same useful shape. This tool fills a template in for you and hands back clean Markdown.
What should a good bug report include?
A clear title, numbered steps to reproduce, the expected result, the actual result, and the environment the problem happened in (browser, operating system, and app version). A screenshot, the console error, and any failed network call make it far quicker to fix.
How do I write a bug report?
Start with a one line summary of what went wrong. List the steps that lead to the problem, then say what you expected and what actually happened. Add the browser, operating system, and version, and attach a screenshot or the console error if you have one. This generator walks you through each field and formats it for you.
Is this bug report template generator free?
Yes. It runs entirely in your browser, there is no signup, and nothing you type is sent anywhere. Fill in the fields, copy the Markdown, and paste it wherever you track bugs.
Can I use the template with GitHub, Linear, or Jira?
Yes. The output is plain Markdown, so it pastes cleanly into a GitHub issue, a Linear ticket, a Jira description, or a Slack message. For GitHub and Linear you do not even need to paste: the Open as GitHub issue and Open in Linear buttons under the output prefill a new ticket for you. Coding agents can read the same Markdown through an API and act on it directly.