Bug Reporting Template
π Bug Reporting Template
Bug Report Creation
# π Bug Report
## π Summary
*One sentence describing the issue*
## β‘ Impact
- [ ] π΄ Critical (blocks release/major functionality)
- [ ] π High (significant feature impact)
- [ ] π‘ Medium (minor feature impact)
- [ ] π’ Low (cosmetic/edge case)
## π Environment
**π₯οΈ Browser/Device:**
**π± Version:**
**π» OS:**
**π App Version:**
## π Steps to Reproduce
1.
2.
3.
## β
Expected Result
*What should happen*
## β Actual Result
*What actually happens*
## πΈ Additional Context
*Screenshots, error messages, or relevant details*
## π Related Issues
- Related to #[issue number]
- Duplicate of #[issue number]
## π·οΈ Labels
- `bug`
- `frontend` / `backend` / `infrastructure`
- `priority: critical` / `priority: high` / `priority: medium` / `priority: low`
## π₯ Assignees
- [ ] Assign to appropriate team member
- [ ] Add reviewers if needed
---
**π€ Reporter:** [Your name]
**π
Date:** [Date]
π Usage Guidelines
When to Use This Template
- Production Bugs: Issues found in live application
- Development Bugs: Issues found during development
- User Reports: Bugs reported by users
- Testing Issues: Bugs found during testing
- Performance Issues: Performance-related problems
Best Practices
- Clear Steps: Provide detailed reproduction steps
- Environment Info: Include all relevant environment details
- Screenshots: Visual evidence is crucial
- Impact Assessment: Help prioritize the bug
- Proper Labels: Use consistent labeling system
Success Criteria
- Bug is clearly described
- Reproduction steps are detailed
- Environment information is complete
- Impact is assessed
- Ready for development team
This template ensures comprehensive bug reporting for faster resolution and better issue tracking.
Last Updated: September 9, 2025 by @drhinca: AdriΓ‘n Bado Chinca