How to Track Dependencies in Jira (Step-by-Step)
Dependency tracking in Jira ranges from simple issue links to Advanced Roadmaps cross-project visualization. Poor dependency management is the number one cause of sprint failures.
This guide covers both approaches and when to use each.
Step-by-step guide
Step 1: Use Jira issue links
Link issues using "is blocked by" and "blocks" relationships. This creates bidirectional links visible on both issues.
Step 2: Create a dependency board view
Create a filter showing all issues with blocking relationships: "issueFunction in linkedIssuesOf() AND status != Done."
Step 3: Set up Advanced Roadmaps
In Jira Premium, create a plan with multiple team boards. Advanced Roadmaps visualizes dependencies as lines between issues.
Step 4: Use dependency epics for externals
For external dependencies, create a dedicated epic. Each dependency is a story with owner, expected resolution date, and impact.
Step 5: Add dependency review to planning
Before committing to a sprint, review: which items are blocked by work outside the sprint? Which block other teams?
Common mistakes
Not linking issues
Dependencies tracked in spreadsheets or Slack are invisible during sprint planning. If a dependency exists, it must be a Jira link.
Circular dependencies
A blocks B blocks C blocks A. This indicates stories need to be broken down.
Not reviewing during planning
Pulling a blocked item into a sprint without checking dependencies leads to sprint failures.
Tips
- Use "is blocked by" consistently (not "relates to" for dependencies)
- Review the dependency graph weekly
- Use Vantage to generate dependency-aware tickets that pre-map the graph
How Vantage helps
Vantage generates tickets with dependency relationships already mapped. When pushed to Jira, the dependencies are ready for sprint planning.