Agreed Process for Bug Tickets and Bug Tracking
- Dominant language
- Python
- Stars
- 8
- Forks
- 2
- Avg merge
- 14h 34m
- Merged PRs (30d)
- 46
Description
#### Description
- When a bug ticket is created, need ACs added directly to the bug ticket, and link previous tickets/ACs related to that bug to the new ticket. This will ensure the bug, and all dependencies, are tested (which will prevent side effect bugs being created from the fix)
- Log all bugs and service interruptions as a bug ticket, and optionally post in general channel if urgent. Bugs should be tracked and recorded in Zenhub. If conversation happens outside zenhub, add conversations to the bug ticket. The ticket should have a record of all communication and decisions.
#### Dependencies
Are there any dependencies?
#### DOD
- [ ] List the items that need to be complete for this ticket to be considered done
- [ ]
- [ ]
- [ ]
- [ ]
Contributor guide
Research direction
No repository file, test, or entry point is named. Start by reviewing the requested bug-ticket, acceptance-criteria, Zenhub, and communication-recording process; done requires replacing the placeholder DOD with agreed completion items.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100