Tools
Bug report templates
A good bug report is reproducible. These free, copy-paste templates give you a consistent structure: title, environment, steps to reproduce, expected vs actual, severity, and the attachments engineers actually need. Pick the one that matches your tracker, copy it, and fill in the blanks.
Standard bug report
A lightweight format that fits any tracker. Enough structure to be reproducible without slowing anyone down.
Title: [Concise summary of what broke and where]
Environment:
- App / URL:
- Browser & version:
- OS / device:
- Viewport / screen size:
- User role / account:
Steps to reproduce:
1.
2.
3.
Expected result:
[What should have happened]
Actual result:
[What actually happened]
Severity: [Blocker | Critical | Major | Minor | Trivial]
Attachments:
- Screenshot / recording:
- Console errors:
- Network requests:Detailed QA report
For QA and regression work: adds preconditions, reproducibility rate, and workaround so engineers can triage without a follow-up.
Title: [Component] Short, specific summary of the defect
Summary:
[One or two sentences: what fails and why it matters]
Environment:
- Build / release:
- App / URL:
- Browser & version:
- OS / device:
- Viewport:
- Test account / role:
- Feature flags:
Preconditions:
- [State the system must be in before the steps]
Steps to reproduce:
1.
2.
3.
Expected result:
[Precise, testable expectation]
Actual result:
[Exactly what happened, including any error text]
Reproducibility: [Always | Intermittent (x/y attempts) | Once]
Severity: [Blocker | Critical | Major | Minor | Trivial]
Priority: [P0 | P1 | P2 | P3]
Workaround:
[Any known workaround, or "None"]
Attachments:
- Session replay / screen recording:
- Screenshot(s):
- Console log:
- Network (HAR) / failing requests:
- Stack trace:Jira-style ticket
Maps to common Jira bug fields. Paste into the description and lift the labelled lines into their fields.
Summary: [Concise bug title for the issue field]
Issue Type: Bug
Priority: [Highest | High | Medium | Low | Lowest]
Affects Version/s: [e.g. 3.2.0]
Component/s: [e.g. Checkout]
Labels: [regression, ui, ...]
Environment:
Browser: [name + version]
OS: [name + version]
URL: [where it happens]
*Steps to Reproduce:*
# First step
# Second step
# Third step
*Expected Result:*
[What should happen]
*Actual Result:*
[What happens instead]
*Notes:*
[Anything else: recent changes, related tickets, console output]
Attachments: [screenshot, replay link, console log, HAR file]GitHub issue
Markdown-formatted for a GitHub issue body or an issue template. Renders with headings and a checklist out of the box.
## Describe the bug
A clear and concise description of what the bug is.
## Environment
- **App / URL:**
- **Browser & version:**
- **OS / device:**
- **Version / commit:**
## Steps to reproduce
1. Go to '...'
2. Click on '...'
3. Scroll to '...'
4. See error
## Expected behavior
A clear description of what you expected to happen.
## Actual behavior
What actually happened, including any error messages.
## Severity
<!-- blocker | critical | major | minor | trivial -->
## Screenshots / recordings
If applicable, add screenshots or a session replay link.
## Console & network
<details>
<summary>Console output</summary>
```
paste console errors here
```
</details>
- [ ] I have searched existing issues for a duplicate
- [ ] I can reproduce this consistently