Which tool satisfies the source-backed purpose "track tasks and bug reports" in the software development scope?

Answer options

• Option: Version control system
  "Version control system" vs. "Issue tracker" A version control system tracks code; misses the target mapping. Version control system is modeled for the purpose merge code changes under version control. The task targets this mapping, so Version control system remains wrong inside Zukunftsthemen zu in this prompt. Zukunftsthemen zu separates it from the requested detail branch.
• Option: Debugger
  "Debugger" vs. "Issue tracker" A debugger inspects running code; misses the target mapping. Debugger is modeled for the purpose inspect runtime state. The task targets this mapping, so Debugger remains wrong in this prompt. Debugger stays in class software delivery tool.
• Correct: Issue tracker
  "Issue tracker" - target An issue tracker collects tasks, bug reports, and ownership for. Issue tracker is modeled for the purpose track tasks and bug reports. The task targets this mapping, and Issue tracker remains correct in this prompt. Issue tracker stays in class software delivery tool.
• Option: CI pipeline
  "CI pipeline" vs. "Issue tracker" A CI pipeline automatically builds,; misses the target mapping. CI pipeline is modeled for the purpose verify code changes automatically. The task targets this mapping, so CI pipeline remains wrong in this prompt. CI pipeline stays in class software delivery tool.

Solution

Issue tracker

Issue tracker is correct because work-item tracking points exactly to issue tracker. The prompt targets Issue tracker, so the graph keeps this mapping stable against close alternatives. Source: Wikidata. As of: 2026-02-13.

Fun fact

Issue tracker stays anchored with additional dataset context. The graph therefore uses a direct graph path.