How to Manage Dependencies in Jira (2026 Guide)
Dependencies between issues are inevitable in any project. Jira handles dependencies through issue links ("is blocked by," "blocks") and Advanced Roadmaps' dependency visualization. When managed well, dependencies enable parallel work. When ignored, they cause sprint failures and missed deadlines.
This guide covers how to set up and manage dependencies in Jira across teams and projects.
Step-by-step guide
Step 1: Use issue links for dependencies
When creating or editing an issue, click "Link" and select the link type: "is blocked by" (this issue cannot start until the linked issue is done), "blocks" (this issue must be done before the linked issue can start), or "relates to" (informational link). Always use directional links (blocks/is blocked by) for true dependencies.
Step 2: Visualize dependencies in Advanced Roadmaps
Open Advanced Roadmaps (Plans) and create a plan that includes all relevant projects. Enable the "Dependencies" feature in plan settings. The timeline view draws red lines between dependent issues. Red lines indicate scheduling conflicts (a blocked issue is scheduled before its blocker).
Step 3: Identify cross-team dependencies
Create a JQL filter: issueLinkType = "blocks" AND project = YOUR_PROJECT AND linkedIssue.project != YOUR_PROJECT. This finds issues where your team depends on another team's work. Review this list in sprint planning to identify cross-team risks early.
Step 4: Set up dependency alerts
Create an automation rule: When an issue that blocks other issues is moved to "Blocked" or its due date is pushed, notify the owners of all blocked issues. This early warning system prevents cascading delays.
Step 5: Create a dependency board
Create a Jira board with a filter showing all issues with blocking dependencies. Add swimlanes by blocker status. This gives you a single view of all dependency chains and their current state. Review this board in your weekly planning meeting.
Step 6: Resolve dependency conflicts
When Advanced Roadmaps shows red dependency lines (scheduling conflicts), you have three options: reschedule the blocked issue to start after the blocker, add resources to the blocker to complete it sooner, or remove the dependency by finding an alternative approach that eliminates the blocking relationship.
Common mistakes
Not tracking dependencies until sprint planning
Discovering dependencies during sprint planning is too late. Track dependencies during backlog grooming. Every issue should have its dependencies identified before it enters a sprint.
Using "relates to" for real dependencies
"Relates to" is informational. "Blocks/is blocked by" is actionable. Using "relates to" for actual blocking relationships means dependency visualizations and alerts do not work correctly.
Circular dependencies
Issue A blocks B, B blocks C, C blocks A. Circular dependencies create deadlocks. Advanced Roadmaps flags these. Resolve by identifying which dependency is weakest and removing it.
Tips
- Use the "Dependency Report" in Advanced Roadmaps to see all dependency chains at once
- Color-code dependencies by type: cross-team (red), within-team (blue), external (orange)
- Schedule a monthly dependency review meeting for cross-team coordination
How Vantage helps
Vantage generates tickets with dependency relationships built in. When creating tickets from PRDs, the AI identifies which tickets depend on others based on the requirements and generates a dependency graph. These dependencies push to Jira as issue links, so your dependency tracking starts on day one.