FREE TOOL · NO SIGNUP

Bug report template generator

Fill in what you know and copy a clean bug report for GitHub, Linear, Jira, Slack or email. Empty fields stay as prompts, so you can also copy it as a blank template.

Severity

GitHub, Linear, GitLab, Notion

## [Short summary of the problem]

**Severity:** Medium
**Page:** [Page URL where it happens]
**Environment:** [Browser, OS and device]

### Steps to reproduce
1. [First step]
2. [Second step]
3. [What you clicked last]

### Expected result
[What should have happened]

### Actual result
[What happened instead]

### Attachments
[Screenshot or screen recording]

Skip the template next time

With FeedbackDots on your site, anyone can click on the problem and send a report. The screenshot, page URL, browser, console logs and session replay are captured for them, and the report lands in Linear, Jira, GitHub or Slack.

How to write a good bug report

  • One bug per report

    Two problems in one ticket means one gets lost. Split them, even if they showed up together.

  • A title someone can search for

    Say what breaks and where: "Checkout button does nothing on mobile", not "Checkout broken!!".

  • Steps anyone can follow

    Start from a page URL and list every click. If a developer can reproduce it in a minute, it gets fixed first.

  • Expected versus actual

    Write both. "It does not work" leaves the developer guessing what working looks like.

  • Environment and evidence

    Browser, device and screen size matter. A screenshot, console error or screen recording saves a round of questions.

Bug report example

## Checkout button does nothing on mobile

**Severity:** High
**Page:** https://example.com/checkout
**Environment:** Safari 18 on iOS 18, iPhone 15

### Steps to reproduce
1. Add any item to the cart
2. Open the cart and tap Checkout
3. Tap Pay now

### Expected result
The payment form opens.

### Actual result
Nothing happens. The button shows a pressed state, then returns.

### Notes
Works on desktop Chrome. Console shows "TypeError: undefined is not a function".

### Attachments
[Screenshot or screen recording]

Questions

What should a bug report include?
A clear title, the page URL, severity, browser and device, numbered steps to reproduce, the expected result, the actual result, and a screenshot or recording. Console errors help developers most.
How do I write steps to reproduce a bug?
Start from a specific page, then list each action in order, one per line, until the bug appears. Include the data you used, such as the item you added or the account type.
Is there a bug report template for Jira?
Yes. Pick the Jira format above and the generator writes the report in Jira wiki markup with headings and a numbered list, ready to paste into the description field.
How can I collect bug reports from clients or users?
Most people will not fill in a template. A feedback widget like FeedbackDots lets them click on the problem instead, and captures the screenshot, page URL, browser, console logs and session replay for them.