Task Mind Map

The Task Mind Map gives you a visual overview of every task in the current project, laid out as an interactive node graph. It is accessible from the project's task page by switching from the grid view to the mind view in the top-right toggle.

How the Map Is Structured

The map flows left to right:

• The leftmost node represents the project root
• The project node fans out into its individual tasks
• Tasks with sub-tasks fan out further into their child task nodes

This hierarchy lets you see the full scope of work for a single project at a glance — from the project entry point down to individual tasks and their sub-tasks.

When to Use the Mind Map

The grid view is best for sorting and filtering a flat list of tasks. The mind view is best for the questions a list does not answer cleanly:

• "What does this project actually consist of?": A new teammate joining the project can open the map, expand the project node, and immediately see the shape of the work: how many tasks are open, which are broken into sub-tasks, and what categories of work dominate.
• "Where are the urgent items?": Priority badges are visible on every node. Scanning the branches surfaces every Urgent and High task in the project without filtering the grid.
• "How are parent tasks decomposed?": When a task has been broken down into sub-tasks by an agent or by the team, those children appear as a fan extending from the parent node. You can see whether a large task is properly decomposed or still a single opaque block of work.
• "Who owns what?": Assignee avatars on every node make it easy to spot the engineer carrying multiple in-progress tasks at once, or tasks that have no owner yet.

Example: planning a sprint

A project lead is starting a new sprint and wants to commit to a set of tasks:

1. They open the project's task page and switch to the mind view.
2. The project node expands to show ~30 task nodes.
3. They scan for Urgent and High priority badges, click each one to confirm scope, and note the assignees.
4. For two large tasks with no sub-task fan-out, they open the task and use the agent to break it down — when they return to the map, those tasks now show child nodes representing the new sub-tasks.

The sprint plan came together without leaving the mind map view, and the same exercise in the grid would have required repeatedly opening and closing task details to see relationships.

Navigating the Map

The hint bar at the top of the canvas describes the available controls:

• Scroll to zoom in and out
• Drag to pan across the canvas
• + on a node to expand or collapse its children
• Click a node to open it directly

For large projects with many tasks, collapsing project nodes you are not focused on keeps the canvas manageable.

Task Nodes

Each task node shows:

• Task title: truncated if long; hover the node to see the full title in a tooltip
• Priority badge: Urgent, High, Medium, or Low
• Label tag: the category the task belongs to, such as Code Quality
• Assignee avatar: shown when the task is assigned to a team member or agent
• Status indicator: a colored dot on the node reflecting the task's current state

Hovering a node surfaces a tooltip with the complete task title and any labels attached to it (for example, triage · urgent). Clicking the node opens the task directly.

View Controls

The top-right corner has three controls:

• Grid / Mind toggle: switches between the standard grid task list and the mind map view
• Hierarchy dropdown: adjusts how the map groups and arranges nodes
• Map ↔: toggles a minimap in the corner for orientation when zoomed in on a project with many tasks

Example: re-pivoting the hierarchy

The default hierarchy is Project → Task → Sub-task, which mirrors how work is decomposed. Switching the dropdown re-pivots the same data so you can answer different questions without leaving the view:

• By assignee: the second level becomes the people the tasks are assigned to. Useful for capacity reviews inside a single project: one branch per teammate, each fanning out to everything they own here.
• By priority: the second level becomes the priority bucket (Urgent / High / Medium / Low). Every Urgent task in the project lines up on a single branch, making cutoff decisions easier when scope has to shrink.
• By label: the second level becomes the label (Bug, Feature, Code Quality, etc.). A glance tells you whether the project is currently bug-heavy or feature-heavy.