Bug Report Template
Document software defects with full reproduction steps, severity, and environment details.
What makes a good bug report?
A good bug report is clear, reproducible, and contains all the information developers need to find and fix the defect. It saves time and improves team communication.
Essential bug report fields
- Title — clear, specific description of the bug
- Environment — OS, browser, app version
- Steps to Reproduce — numbered, specific actions
- Expected vs Actual Result — what should happen vs what happens
- Severity and Priority — impact and urgency
Bug severity vs priority explained
Severity = impact on the system (Critical/Major/Minor/Trivial). Priority = urgency of fix (High/Medium/Low). These are independent: a typo on the home page can be low severity but high priority.