Issue tracking is the practice and supporting tooling for recording, prioritising, assigning, and resolving units of work such as bugs, feature requests, and tasks across a software project. Each issue carries metadata, status, discussion, and links to code changes, giving teams a shared backlog and an audit trail of decisions. It underpins collaborative and agile development and integrates tightly with version control and continuous integration.
Overview
- An issue tracker is the central record of what needs doing, who owns it, and its current state.
- Each issue accumulates metadata, discussion, labels, and references to commits and pull requests.
- It is a backbone of collaborative Software Development, especially in distributed and Open Source teams.
Key aspects
- Structured states and transitions modelling a Workflow from open to closed.
- Prioritisation, labelling, and assignment to coordinate effort.
- Traceability linking issues to code, releases, and decisions.
Mechanisms
- Contributors file issues; maintainers triage, label, and assign them.
- Boards such as Kanban visualise flow and limit work in progress.
- Integration with Continuous Integration and pull requests closes issues automatically on merge.
Applications
- Managing bug backlogs and feature roadmaps.
- Coordinating contributions in open source communities.
- Supporting Agile Development sprints and retrospectives.