Bug report template
Copy the template below, or paste a messy bug description from Slack, email or a customer, and get a clean, reproducible report.
This is the Bug Report snippet. In Snippetbar, copy the Slack message, run it, and paste into Linear or Jira.
The template
**Title:** [Area] Short description of what's broken **Summary** One sentence: what happens, where, and who's affected. **Steps to reproduce** 1. 2. 3. **Expected result** **Actual result** **Environment** - Device / OS: - Browser / app version: - Account / workspace: **Severity:** Blocker / High / Medium / Low **Frequency:** Always / Sometimes / Once **Attachments:** screenshots, recording, console errors **Notes:** workaround, when it started, related issues
Bug report examples
From a Slack message
Slack message
hey the export button doesnt work again?? tried on chrome, it just spins forever. need this for the board meeting tmrw
After
Title: [Reports] Export to CSV spins indefinitely and never downloads
Summary: Clicking Export on a report shows a loading spinner that never finishes, so no file is downloaded. The user needs it by tomorrow.
Steps to reproduce:
- Open any report {confirm which one}
- Click Export
- Observe the spinner
Expected: A CSV downloads within a few seconds.
Actual: The spinner runs indefinitely and no file is downloaded.
Environment: Chrome {version unknown}, {OS unknown}
Severity: High (a deadline depends on it)
Frequency: {unknown}. The reporter says “again”, so it may be a regression.
From a customer email
Customer email
I added a discount code at checkout and the total didn't change, but I got charged full price. iPhone, Safari.
After
Title: [Checkout] Discount code accepted but not applied to total or charge
Summary: On mobile Safari, a customer's discount code didn't reduce the order total, and they were charged full price.
Steps to reproduce: 1. Add an item to the cart on iPhone Safari 2. Enter discount code {code} at checkout 3. Complete purchase
Expected: The total and the charge reflect the discount.
Actual: The total stays the same and the full price is charged.
Environment: iPhone, Safari {iOS version unknown}
Severity: High (revenue and refund issue)
Notes: Check whether the code shows as “applied” in the UI. Refund needed for customer {order ID}.
From a vague internal note
Internal note
Date picker shows wrong month when you open it from the edit modal. Only on the second time you open it.
After
Title: [Edit modal] Date picker opens on the wrong month the second time it's opened
Steps: 1. Open an item's edit modal 2. Open the date picker (it shows the correct month) 3. Close it and open it again
Expected: It opens on the selected date's month.
Actual: It opens on {which month?}. Possibly stale state from the previous open.
Frequency: Always, on the second open
How to write a bug report developers love
One bug per report
If you found three problems, file three reports. Combined reports get half-fixed and closed.
Steps someone else can follow cold
Write steps as if the reader has never seen the feature. If a developer can't reproduce it, they can't fix it.
Expected vs actual, always both
“It's broken” isn't a report. Stating what you expected shows whether it's a bug or a misunderstanding of the design.
Title with area + symptom
“[Checkout] Discount not applied to total” is searchable and easy to triage. “Checkout issue” is neither.
Mark what you don't know
It's better to write “{browser version unknown}” than to guess. Gaps tell the triager what to ask, while wrong details send them the wrong way.
Attach evidence
A 10-second screen recording saves a paragraph of steps. Include console errors if you can see them.
The snippet
This is the exact prompt the tool above runs. Save it as a snippet in Snippetbar and it works on any text you select.
You are a QA lead. Turn the text below into a clear bug report.
Rules:
- Use only information in the text. Never invent steps, versions, or causes. Mark missing details as {unknown} or {question}.
- Title: [Area] + concrete symptom, under 12 words.
- Include: Summary (1 sentence), Steps to reproduce (numbered), Expected, Actual, Environment, Severity (with a 3–5 word reason), Frequency, Notes.
- Neutral, factual tone. Remove frustration and urgency language but keep real deadlines in Notes or Severity.
- If the text describes multiple bugs, write separate reports.
Return only the report in markdown.Use it where you work
From Slack to Linear
Copy the teammate's message, run the snippet, and paste into a new Linear issue. The title and description are ready, and the gaps are marked so you know what to ask.
From support tickets
Turn customer emails into dev-ready reports in Jira without rewriting them by hand.
In GitHub issues
Paste the result straight into an issue, since the markdown formatting carries over.
More snippets
All snippets →User story template
Copy the user story template below, or paste a feature idea, a Slack thread or customer feedback and get stories with acceptance criteria your team can estimate.
Microcopy
Paste any UI text, like a button, an error or an empty state, and get a clearer, friendlier version with variants to choose from.
Meeting agenda generator
Before the meeting, paste a Slack thread, a list of topics or an invite, and get a focused agenda. After it, paste your notes and get decisions and action items.
Questions
Run it in any app
Select the text, pick Bug report template from the menubar or press its shortcut, and the result replaces it in place.
From “it's broken” to a ticket in one shortcut.
Snippetbar runs your snippets on anything you copy, in any Mac app. $29, one-time purchase.