Bug report template

Fill in the fields and copy the finished bug report as Markdown or plain text. It runs in your browser and nothing is sent to us.

Fill in the template

One line a developer can scan in a list: what is broken, and where.
One or two sentences of context, so the reader knows what they are looking at.
Numbered, starting from a known state, specific enough that somebody else reaches the same screen.
What the product was supposed to do, according to the design or the documentation.
What it did instead, described as symptoms rather than as a diagnosis.
Browser, operating system, device, screen size, and whether you were signed in.
A screenshot or a short video, with a line saying what each one shows.
Anything the browser console printed, pasted as it appeared. Leave it empty if there was nothing.
Requests that failed or came back with something unexpected, from the Network tab.
How serious it is, who it reaches, and whether there is a way around it.
How often it happens, when it started, and anything already reported near it.
Tick off what you did before sending, so the reader knows what has already been ruled out.
Download MarkdownDownload plain text

Your bug report

Both versions update as you type. Copy whichever one your tracker takes.

Markdown
# Bug Report

## Title
[Clear, descriptive title - What's broken and where]

## Description
[Brief overview of the issue - 1-2 sentences]

## Steps to Reproduce
1. [First step - starting from a known state]
2. [Second step - be specific about actions]
3. [Third step - include any data/values used]
4. [Additional steps as needed]
5. [Final step that triggers the bug]

## Expected Behavior
[What should happen according to design/logic]

## Actual Behavior
[What actually happens - describe symptoms]

## Environment
- **Browser:** [Browser name and version]
- **Operating System:** [OS and version]
- **Device:** [Desktop/Mobile device model]
- **Screen Resolution:** [If layout issue]
- **User Status:** [Logged in/out, user role]

## Visual Evidence
[Attach screenshots or video]
- Screenshot 1: [Description]
- Screenshot 2: [Description]
- Video: [Link or attachment]

## Console Errors
```
[Paste any errors from browser console - F12 → Console tab]
```

## Network Issues
[Any failed API calls from Network tab - F12 → Network]

## Impact and Severity
- **Severity:** [Critical/High/Medium/Low]
- **Affected Users:** [All users / Mobile users / Specific role / etc.]
- **Business Impact:** [Lost revenue / Support burden / etc.]
- **Workaround:** [Yes/No - if yes, describe]

## Additional Context
- **Frequency:** [Every time / Sometimes / Rarely]
- **Since When:** [Just now / After update / Since [date]]
- **Related Issues:** [Links to similar bugs]
- **Other Notes:** [Any other relevant information]

## Checklist
- [ ] I have tested this in a clean environment (incognito/private mode)
- [ ] I have included steps to reproduce
- [ ] I have provided environment details
- [ ] I have attached screenshots/video
- [ ] I have checked the console for errors
- [ ] I have checked if this issue was already reported
Plain text
BUG REPORT
==========

TITLE
-----
[Clear, descriptive title - What's broken and where]

DESCRIPTION
-----------
[Brief overview of the issue - 1-2 sentences]

STEPS TO REPRODUCE
------------------
1. [First step - starting from a known state]
2. [Second step - be specific about actions]
3. [Third step - include any data/values used]
4. [Additional steps as needed]
5. [Final step that triggers the bug]

EXPECTED BEHAVIOR
-----------------
[What should happen according to design/logic]

ACTUAL BEHAVIOR
---------------
[What actually happens - describe symptoms]

ENVIRONMENT
-----------
- **Browser:** [Browser name and version]
- **Operating System:** [OS and version]
- **Device:** [Desktop/Mobile device model]
- **Screen Resolution:** [If layout issue]
- **User Status:** [Logged in/out, user role]

VISUAL EVIDENCE
---------------
[Attach screenshots or video]
- Screenshot 1: [Description]
- Screenshot 2: [Description]
- Video: [Link or attachment]

CONSOLE ERRORS
--------------
```
[Paste any errors from browser console - F12 → Console tab]
```

NETWORK ISSUES
--------------
[Any failed API calls from Network tab - F12 → Network]

IMPACT AND SEVERITY
-------------------
- **Severity:** [Critical/High/Medium/Low]
- **Affected Users:** [All users / Mobile users / Specific role / etc.]
- **Business Impact:** [Lost revenue / Support burden / etc.]
- **Workaround:** [Yes/No - if yes, describe]

ADDITIONAL CONTEXT
------------------
- **Frequency:** [Every time / Sometimes / Rarely]
- **Since When:** [Just now / After update / Since [date]]
- **Related Issues:** [Links to similar bugs]
- **Other Notes:** [Any other relevant information]

CHECKLIST
---------
- [ ] I have tested this in a clean environment (incognito/private mode)
- [ ] I have included steps to reproduce
- [ ] I have provided environment details
- [ ] I have attached screenshots/video
- [ ] I have checked the console for errors
- [ ] I have checked if this issue was already reported

This runs in your browser. Nothing you paste or open is sent to us.

What each field is for

A bug report template earns its place by removing the follow-up questions. The title and the description tell a developer whether the report is theirs. The steps, the expected behaviour and the actual behaviour let them reproduce it. The environment, the visual evidence and the console errors are the ones reporters skip, and they are the ones that decide whether the bug can be fixed today or after a week of exchanges.

What makes a bug report worth reading

Write the steps from a state the reader can reach, and be specific about the values you typed. Describe symptoms rather than causes, because a wrong diagnosis sends the fix in the wrong direction. Keep one bug to one report. And leave nothing out because it seems obvious: the browser version, the screen size and whether you were signed in are the details that explain why nobody else can see the problem.

The extension fills half of this in for you

Session Replay captures the environment, the console errors and the visual evidence from the page where the bug happened, so three of these fields are already written by the time you open the report.

Install ExtensionHow It Works