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