Dependency Manager for Jira Cloud
Key Takeaways
Dependency Manager for Jira Cloud maps cross-team Jira dependencies as an interactive graph where issues are nodes and blocking relationships are edges, so delivery leads can see what blocks a release before it slips.
The app is built natively on Atlassian Forge and runs with no data egress, meaning every dependency link, graph, and calculation is computed and stored inside your own Atlassian tenant, with no Divim-operated server or third-party hosting.
Dragging a line between two issues creates a native Jira blocks or is blocked by link, so users map dependencies without selecting link types or hunting for issue keys.
Dependency Manager automatically calculates and highlights the critical path, the longest chain of blocking issues that dictates the earliest possible release date, and it detects circular dependencies so they do not corrupt the schedule.
Scope Risk Analysis combines stall detection with a ranked risk heatmap to point delivery leads at the highest-risk work first, while blockers in other Fix Versions or the backlog appear as separate cross-release context nodes.
See every blocker before it slips your release, without your data ever leaving Atlassian. Dependency Manager for Jira Cloud turns tangled cross-team issue links into a clear, interactive map, calculates the critical path automatically, and flags the work most likely to derail your release. It's built natively on Atlassian Forge, so everything is computed and stored inside your own Atlassian tenant.
โถ Try it free on the Atlassian Marketplace
๐ก๏ธ Runs on Atlassian, an auto-verified Forge app with no data egress: no Divim-operated servers, no third-party hosting, no vendor-side copy of your data.
What it does
Drag-and-drop dependency mapping. Draw a line between two issues to create a native Jira "blocks" / "is blocked by" link, no manual link-type selection or issue-key hunting.
Interactive dependency graph. Issues are nodes, blocking relationships are edges, with key metadata shown inline.
Automated critical path. The longest blocking chain, the one that dictates your earliest possible release date, is calculated and highlighted automatically.
Cycle detection. Circular dependencies are identified and isolated so they don't corrupt the schedule.
Cross-release context. Blockers living in other Fix Versions or the backlog appear as distinct context nodes, so external dependencies stay visible without clutter.
Scope Risk Analysis. Stall detection plus a ranked risk heatmap point delivery leads at the highest-risk work first.
Why teams choose it
Cross-team dependencies are where releases quietly slip, and where security teams worry about yet another integration phoning home. Dependency Manager does neither: the visibility to catch a blocker early, on an architecture where nothing leaves Atlassian.
Get started
Follow the User Guide to map dependencies and read the critical path.
Documentation & trust
Divim Trust Center: company-wide security, privacy & compliance
Related Divim apps
Advanced Release Planning for Jira Cloud: plan releases against real capacity, predictability, and the dependencies you map here.
Sprint Automation for Jira Cloud (Automatic Start & Close): keep sprint cadence running on schedule across every team.
Productivity Metrics, Charts, Reports and Insights: cycle time, throughput, and bottleneck detection for the same delivery flow.
Divim Central: the full Divim product suite at a glance.
Published by Divim, Inc. ยท Support: support@divim.io