Git Issue Ticket Template
🎫 Git Issue Ticket Template
Issue Creation
# 🎫 Issue Ticket
## 📝 Description
*What needs to be done*
## 🎯 Type of Issue
- [ ] 🐛 Bug report
- [ ] ✨ Feature request
- [ ] 📚 Documentation
- [ ] 🔧 Enhancement
- [ ] 🚀 Epic/Story
## 📍 Scope
**Include:**
-
**Exclude:**
-
## 🏗️ Areas
- [ ] Frontend
- [ ] Backend
- [ ] Database
- [ ] Infrastructure
- [ ] Other: ___
## ✅ Acceptance Criteria
- [ ]
- [ ]
- [ ]
## 👥 Contact
**Owner:** @
**Stakeholders:** @
## 🔧 Technical Notes
*Implementation approach, dependencies, constraints*
## 💼 Business Notes
*Why this matters, user impact, success metrics*
## 📎 Attachments
*Links, designs, specs, related issues*
## 🔗 Related Issues
- Related to #[issue number]
- Blocks #[issue number]
- Blocked by #[issue number]
## 🏷️ Labels
- `bug` / `feature` / `documentation` / `enhancement`
- `frontend` / `backend` / `infrastructure`
- `priority: high` / `priority: medium` / `priority: low`
- `size: small` / `size: medium` / `size: large`
## 📊 Priority & Timeline
**Priority:** High/Medium/Low
**Timeline:**
## 📅 Milestone
- [ ] Assign to appropriate milestone/sprint
📝 Usage Guidelines
When to Use This Template
- Bug Reports: Documenting issues found in the application
- Feature Requests: Proposing new functionality
- Documentation: Requesting documentation updates
- Enhancements: Improving existing features
- Epics/Stories: Breaking down large features
Best Practices
- Clear Description: Provide clear, concise descriptions
- Acceptance Criteria: Define what "done" looks like
- Proper Labels: Use consistent labeling system
- Attachments: Include audio-visual when relevant
- Related Issues: Link related work
Success Criteria
- Issue is clearly defined
- Acceptance criteria are specific and testable
- Proper labels and assignees are set
- Related issues are linked
- Ready for development
This template ensures consistent and comprehensive issue creation for better project management.
Last Updated: September 9, 2025 by @drhinca: Adrián Bado Chinca