Add Issue Tracker & Task Planner (Code‑Centric)

[yaredtsy]

Add an issue tracker and task planner that is directly connected to functions, not just files or repos. Issues and tasks should live close to the code they affect, and multiple issues should be able to share notes and context.

This system should make it easy to see where problems are “bubbling up” in the code and how they evolve over time.

Core Goals:

• Issues are linked to functions / nodes
• Tasks, notes, and history are shared, not duplicated
• Impact is visible directly on the code graph

Requirements:

Issue & Task Model:

• Create issues and tasks that can be attached to:
  • A single function
  • Multiple functions
  • A group of functions
• Multiple issues can:
  • Share notes
  • Reference each other
  • Converge into a single task or split apart later

Notes & Collaboration:

• Notes are reusable and linkable
• A note can belong to:
  • One issue
  • Multiple issues
• Notes stay attached to the relevant functions

Impact & Visibility:

• Ability to see:
  • Issues bubbling up on a function (hotspots)
  • Which functions are affected by an issue
  • How many open issues touch a function
• Visual indicators on the graph (badges, heat, etc.)

History & Code Changes:

• Each issue shows:
  • Related commits
  • Which functions changed
  • Timeline of changes
• From a function view, users can see:
  • Past issues
  • Tasks worked on it
  • Commit history tied to issues

AQL Integration:

• Query examples:
  • “Show functions with the most open issues”
  • “Show all issues affecting this function”
  • “Show commits related to this issue”

Acceptance Criteria:

• Issues feel part of the code graph, not a separate tool
• Users can track impact without scanning files
• History connects issues, tasks, and code changes
• System scales to large projects without noise

Notes:
This is not a traditional issue tracker. It is a graph‑aware planning system where work, problems, and code evolve together.