Dependency Manager for Jira Cloud

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

  1. Install from the Atlassian Marketplace.

  2. Follow the User Guide to map dependencies and read the critical path.

Documentation & trust

Related Divim apps


Published by Divim, Inc. · Support: support@divim.io