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.
Working in Jira? Turn your spec into dependency-ordered tickets.
Paste the feature or spec. Vantage pulls out the requirements and breaks them into tickets, ordered by what blocks what, ready to groom with your team.
How this works
- We save what you typed. No AI runs on this page.
- You create a free account.
- Vantage builds a PRD and dependency-ordered tickets from it inside your own workspace.
Why ask for an account? We’re a small team, and a full generation runs a multi-step AI pipeline that costs us real money. So we tie it to a free account instead of running it anonymously. You also get to keep the result and edit it.
Your text is only used to create your project, and it stays private to your account. If you don’t sign up, we delete it after 7 days. Privacy policy
Step-by-step guide
Use Jira issue links
Link issues using "is blocked by" and "blocks" relationships. This creates bidirectional links visible on both issues.
Create a dependency board view
Create a filter showing all issues with blocking relationships: "issueFunction in linkedIssuesOf() AND status != Done."
Set up Advanced Roadmaps
In Jira Premium, create a plan with multiple team boards. Advanced Roadmaps visualizes dependencies as lines between issues.
Use dependency epics for externals
For external dependencies, create a dedicated epic. Each dependency is a story with owner, expected resolution date, and impact.
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.