Bug Report Template
Reusable issue template
Copy this into Linear, Jira, GitHub, Slack, or email when reporting an issue. The goal is to make triage faster by capturing the context that usually gets lost first.
Best use
- bug reports from smoke tests or regression passes
- offline, sync, and admin verification issues
- usability problems that still need concrete reproduction details
Title:
Severity: Blocker / High / Medium / Low
Build Version:
Build Type: TestFlight / APK / local dev / web / other
Platform: iOS / Android / Web / other
Device / OS:
Account / Role:
Network State: online / offline / reconnecting / flaky
Preconditions:
Steps to Reproduce:
1.
2.
3.
Expected Result:
Actual Result:
Frequency: always / often / sometimes / once
Impact:
Artifacts:
- Screenshot:
- Screen recording:
- Logs:
Notes:
Add these for sync or offline bugs
Pending Count Before:
Pending Count After:
Was Sync Now Tried?:
Did the issue survive app relaunch?:
Did the item appear duplicated after reconnect?:
Add these for permission or native bugs
Permission State Before Repro:
Physical Device or Simulator/Emulator:
Biometrics Enrolled?:
Camera/Mic/Photos permission already granted?:
Add these for admin control plane bugs
Page URL:
Browser:
Viewport / Screen Size:
Was the issue visible after refresh?:
QA check
Good reporting tips
- be specific in the title
- use exact values you entered when relevant
- include whether the issue happened on a physical device
- attach screenshots for UI issues and recordings for workflow issues
Severity guide
| Severity | Meaning |
|---|---|
| Blocker | Core use is stopped or data integrity is at risk |
| High | Major feature broken with limited workaround |
| Medium | Important issue with workaround |
| Low | Minor issue or polish gap |