Dependencies define blocking relationships between issues. They power the Ready queue, blocked detection, and the dependency graph.
A dependency says: "Issue A depends on Issue B" — meaning A cannot proceed until B is closed.
When B is closed, A becomes unblocked (assuming it has no other open dependencies). Unblocked issues appear in the Ready queue.
From an issue's detail page, scroll to the Dependencies section. You can add:
Dependencies can span across issues within your project scope.
The Dependency Graph page (sidebar: Plan > Dependency Graph) shows a visual SVG graph of all issue dependencies. Nodes represent issues, edges represent blocking relationships.
The graph also includes a table view listing all dependencies, and supports filtering by status and type.
The graph API automatically detects circular dependencies (e.g., A blocks B, B blocks C, C blocks A). Cycles are highlighted so you can break them.
| Queue | Shows |
|---|---|
| Ready | Open issues with no unresolved (open) dependencies — safe to start working on |
| Blocked | Open issues with at least one unresolved dependency — waiting on other work |
These queues update in real time as issues are closed or dependencies change.
When you move an issue to another project, any dependencies that span projects are preserved but flagged as cross-project dependencies. The move action reports how many exist so you can review them.