Issue Tracking System
lastmod 2025-12-08created 2015-04-238 edits
An Issue Tracking System is a system where bugs, requirements, tasks, and so on are posted in the form of posts, and developers and testers record the progress of the work.
When running a project, terms such as Risk Management and Issue Management are frequently used in project management. Let's take a moment to look at the hidden relationship between these terms.
A Risk, as discussed in project management, is defined as follows.
- Something that has not happened yet, but has a Probability of happening.
- Something that, if it happens, can have an Impact that disrupts the project
- But something that, if handled properly, can also become an Opportunity.
And an Issue (or Problem) is defined as a “Realized” risk that can disrupt the progress of the project. Of course, there can also be problems (Issues) that were not anticipated in advance. An issue can be about various topics: something you want to do, a request, something that should be removed, a notice about something that is fundamentally wrong, and so on.
While running a project, risks can be avoided, but issues are problems that have already happened, so they must be resolved in some form. The series of activities of listing issues, setting priorities, assigning owners, and checking resolution status is called issue management, and a tool built to manage such issues properly is called an issue management tool, an issue management system, or an issue tracking system.
List of Issue Tracking System
- Issue Tracking System
- Mantis
- Bugzilla
- Blossom
- Request Tracker
- The Bug Genie
- WebIssues
- ChiliProject
- Jira
- TRAC
- Redmine
- GitHub
- GitLab
- Yona
- git-bug - Bug tracker stored in a git repo
- Kitemaker - Collaboration tool for remote teams, an alternative to JIRA
- Plane - Open-source alternative to JIRA/Linear
- Linear
See also
- Workflow management system
- Korean: 사용자 피드백 관리 서비스 (Customer feedback management services)
- UseResponse
- Feedback loop
- Korean: 버그바운티 (BugBounty)