/
User Guide — Dependency Manager for Jira Cloud

User Guide — Dependency Manager for Jira Cloud

This guide shows delivery leads and release managers how to map cross-team dependencies and find the critical path with Dependency Manager for Jira Cloud — visually, inside your own Atlassian tenant, with nothing leaving Atlassian.

Try it free: Dependency Manager for Jira Cloud on the Atlassian Marketplace.

1. Installation

  1. Sign in to Jira Cloud as a site administrator.

  2. Go to Apps → Explore more apps and search for Dependency Manager for Jira Cloud.

  3. Click Get it now, choose your site, and accept the requested Forge permissions.

2. Open the dependency view

Open the app and select the Fix Version (release) you want to plan. The app reads the issues in that release and their native Jira issue links and assembles them into an interactive, node-based dependency map.

3. Map dependencies with drag-and-drop

  • Create links visually. Drag a line between two nodes to create a native Jira dependency link ("blocks" / "is blocked by") — no manual link-type selection or issue-key searching.

  • Nodes represent Jira issues and show key metadata (issue key, summary, status, assignee).

  • Edges represent the directional blocking relationship between work items.

4. Read the critical path

The app automatically calculates the critical path — the longest chain of dependent tasks that dictates the earliest possible completion date of the release.

  • The critical-path nodes and edges are highlighted in a distinct, high-contrast color so the highest-risk chain is obvious at a glance.

  • If a task on the critical path slips, the release slips — so this is where to focus attention first.

5. Catch cycles and cross-release blockers

  • Cycle detection. The app identifies and isolates circular ("infinite loop") dependencies so they don't corrupt the schedule.

  • Cross-release context nodes. Blockers that live in a different Fix Version or the backlog appear as visually distinct context nodes (e.g. ghosted/dashed), giving you visibility into external dependencies without cluttering the current release.

6. Analyze scope risk

The Scope Risk Analysis panel turns the network into action:

  • Stall detection flags issues that have sat in a "Blocked" state beyond your configured threshold.

  • A ranked risk heatmap sorts critical-path issues by risk (from scheduling slack and time-in-status) so delivery leads can intervene where it matters most.

7. Tips

  • Keep your "blocks" / "is blocked by" links current in Jira — the map is only as accurate as your links.

  • Review the critical path at the start of each release and again after any major scope change.

  • Resolve cycles early; they distort the earliest-completion estimate.

8. Getting help