Dependencies

The Dependencies view lists every relationship across your issues — what blocks what, and what depends on what — with a header showing how many blockers are resolved.

Dependencies

What you see

• Every relationship — one row per link: the source issue, the relationship, and the target issue, each with its status and labels. A relates_to link shows once, and is hidden when the same two issues also have a blocking, dependency or duplicate link
• Filters — narrow by type (blocked by, depends on, relates to, duplicated by), search by issue ID or title (/), and show or hide completed links
• Blocker progress — how many blockers are resolved, e.g. "6 of 13 blockers resolved". A blocker counts as resolved only when it is DONE; a canceled or duplicate blocker still blocks

Dependency graph

Click any row to open the graph around that issue: what it waits on, and what waits on it. Issues further along the chain appear faded. Press Esc to return to the list.

Dependency graph

This view is most useful during planning — check it before a sprint to make sure nothing is unexpectedly blocked, or after decomposing an epic to verify the dependency graph looks right.

Creating dependencies

Link issues from the CLI:

xpo link <source> <target> --type blocks
xpo link <source> <target> --type depends_on

Or use the Relationships button in an issue's sidebar on the board. See Relationships for all relationship types.