The Dependency Graph View visualizes your tasks as an interactive network of nodes and edges. It helps you understand how tasks relate to one another, identify bottlenecks, and plan work in the correct order.
Overview
- Node-Based Layout — every task is a draggable node on a force-directed canvas.
- Dependency Links — directed edges connect tasks that depend on one another.
- Dependency Types — supports Finish-to-Start (FS), Start-to-Start (SS), Finish-to-Finish (FF), and Start-to-Finish (SF).
- Status-Coloured Nodes — node fill colour reflects task status at a glance.
- Real-Time Sync — changes to dependencies in any view update the graph instantly.
- HiDPI Support — canvas scales by device pixel ratio for crisp rendering on Retina displays.
Note
The Dependency Graph is a read-only visualisation. Dependencies are created and removed in the Task Details Panel, not by interacting with the graph directly.
Opening the Dependency Graph
- Click the Graph icon in the view switcher in the header, or
- Open the Command Palette and run Project Planner: Open Dependency Graph.
Interface
Header Bar
The standard plugin header with the project selector and view switcher buttons. Switching projects reloads the graph for the newly selected project.
Graph Canvas
The main area where the dependency network is rendered as a force-directed simulation:
- Nodes — rounded rectangles filled with the task's status colour and labelled with the task title in white text.
- Edges — directed arrows between nodes colour-coded by dependency type.
- Simulation — nodes repel each other and edges act as springs; the graph settles into a stable layout automatically.
Graph Visualisation
Task Nodes
Node fill colour reflects the task's current status:
- Not Started — gray
- In Progress — blue
- Blocked — red
- Completed — green
Dependency Edges
Edge colour identifies the dependency type:
- FS (Finish-to-Start) — blue
- SS (Start-to-Start) — green
- FF (Finish-to-Finish) — orange
- SF (Start-to-Finish) — red
Task Relationships
Dependency Types
| Type | Code | Meaning | Example |
|---|---|---|---|
| Finish-to-Start | FS | Task B cannot start until Task A finishes. | "Design" must finish before "Development" starts. |
| Start-to-Start | SS | Task B cannot start until Task A starts. | "QA Setup" starts when "Development" starts. |
| Finish-to-Finish | FF | Task B cannot finish until Task A finishes. | "Documentation" finishes when "Development" finishes. |
| Start-to-Finish | SF | Task B cannot finish until Task A starts. | Rare — used for just-in-time scheduling. |
Managing Dependencies
Dependencies are managed in the Task Details Panel, not in the graph itself. To add, remove, or change a dependency type:
- Right-click any task in Grid, Board, or Gantt view and select Open details.
- In the Task Details Panel, scroll to the Dependencies section.
- Add a predecessor by selecting the task and choosing the dependency type (FS/SS/FF/SF).
- The graph updates automatically when you return to it.
Warning
Creating a circular dependency (A → B → A) is not allowed. The plugin's circular dependency guard will prevent the cascade and the graph will not enter an infinite loop.
Navigation
Node Interaction
- Drag — click and drag a node to reposition it on the canvas. The simulation re-settles around the moved node.
- Double-Click — open the full Task Details Panel for that task.
Integration with Other Views
- Grid View — the dependency column in the Grid View links directly to the same dependency data shown in the graph.
- Timeline View — dependency arrows on the Timeline use the same FS/SS/FF/SF relationships.
- Task Details Panel — the dependency manager in the details panel is where all graph changes originate.
Use Cases
Project Planning
Map out all tasks and their relationships before work begins. The graph reveals the dependency chain and helps set realistic deadlines when combined with the Timeline View.
Risk Management
Identify tasks that block many others. If a high-risk task is a predecessor to several downstream tasks, it deserves extra attention and contingency planning.
Team Communication
Share a screenshot of the graph during stand-ups to give the team a clear picture of what's blocked and what's ready to start.
Workflow Optimisation
Look for unnecessary sequential dependencies that could run in parallel. Converting FS links to SS links where appropriate can shorten the overall project timeline.
Best Practices
Do
- Keep dependency chains as short as possible.
- Use Finish-to-Start (FS) as the default type — it's the most intuitive.
- Review the graph regularly to catch outdated dependencies after tasks are completed.
- Pair the graph with the Timeline View for date-based critical path analysis.
Don't
- Don't create dependencies between unrelated tasks just to force ordering — use task priority instead.
- Don't leave completed tasks with active outgoing dependencies — clean them up to keep the graph readable.