Triage GitHub issues: labeling, prioritization, assignment, and resolution tracking
Efficiently triage and manage GitHub issues for CIA project.
Labels: bug, needs-triage
Checklist:
- [ ] Steps to reproduce provided
- [ ] Expected vs actual behavior clear
- [ ] Environment details included
- [ ] Screenshots/logs attached
Severity:
- critical: System down, data loss
- high: Major feature broken
- medium: Feature partially broken
- low: Minor issue, workaround exists
Labels: enhancement, needs-triage
Checklist:
- [ ] Use case described
- [ ] Acceptance criteria defined
- [ ] Similar features considered
- [ ] Implementation complexity estimated
Priority:
- high: Aligns with roadmap, high value
- medium: Useful but not urgent
- low: Nice to have
Labels: security, URGENT
Process:
1. Immediately notify security team
2. Move to private security advisory
3. Do NOT discuss publicly
4. Follow SECURITY.md disclosure process
Type Labels:
bug - Something isn't workingenhancement - New feature or requestdocumentation - Documentation improvementsquestion - Further information requestedsecurity - Security vulnerabilityPriority Labels:
priority: critical - Immediate action requiredpriority: high - Should be addressed soonpriority: medium - Important but not urgentpriority: low - Nice to haveStatus Labels:
status: needs-triage - Awaiting initial reviewstatus: accepted - Confirmed, ready for workstatus: in-progress - Work startedstatus: blocked - Waiting on external factorstatus: wontfix - Will not be addressedArea Labels:
area: security - Security-relatedarea: api - API changesarea: ui - User interfacearea: database - Database changesarea: ci/cd - Build/deployment**Describe the bug**
A clear description of the bug.
**To Reproduce**
Steps to reproduce:
1. Go to '...'
2. Click on '...'
3. See error
**Expected behavior**
What you expected to happen.
**Screenshots**
If applicable, add screenshots.
**Environment**
- OS: [e.g., Ubuntu 22.04]
- Browser: [e.g., Chrome 120]
- Version: [e.g., 2.5.0]
**Additional context**
Any other context about the problem.
**Is your feature request related to a problem?**
Describe the problem.
**Describe the solution you'd like**
Clear description of what you want.
**Describe alternatives you've considered**
Other solutions you've thought about.
**Additional context**
Any other context or screenshots.