OVERALL RATINGS
INSTALLS
2
SUPPORT
- Partner Supported
TRUST SIGNALS
Key highlights of the appEnforce "is blocked by" dependencies — block completion, auto-notify, and override with audit
Block completion while blockers are open
An issue cannot be moved to Done while any “is blocked by” issue is still open. Works automatically in any project, plus an optional workflow validator for company-managed projects.
Auto-notify waiting issues
The moment a blocker is resolved, every issue waiting on it gets a comment, so the people who were blocked find out without checking.
Override with a full audit trail
Need to close anyway? One click allows completion despite open blockers for a limited time, and the override is recorded with who approved it.
Supporting media
More details
Highlights:
• Block completion while any "is blocked by" issue is still open — automatically, in any project, plus an optional workflow validator for company-managed projects.
• Auto-notify waiting issues the moment a blocker is resolved.
• See every blocker at a glance with a clear open/done indicator.
• One-click override with a full audit trail.
Privacy: runs entirely on Atlassian (Runs on Atlassian). No external services, no AI, no third-party data processing.
Languages: English, German, French, Spanish, Portuguese (Brazil), Italian, Dutch, Japanese.
Resources
App documentation
Comprehensive set of documentation from the partner on how this app works
Privacy and Security
Privacy and security questionnaire has been filled by the partner
Privacy policy
Atlassian's privacy policy is not applicable to the use of this app. Please refer to the privacy policy provided by this app's partner.
Partner privacy policySecurity program
This app is not part of the Marketplace Bug Bounty program.
Integration permissions
Dependency Guard for Jira integrates with your Atlassian app
Version information
Version 3.6.0•for Jira Cloud
- Release date
- Sep 9th 2026
- Summary
- Security: user-permission checks in the workflow validator; Forge SDK 8.x
- Details
Security: the workflow validator now reads linked blocker issues as the acting user (asUser), so Jira enforces that user’s own permissions. Before a blocker is named in the validation message, the app verifies via the Forge Authorize API that the user may view it. Blockers the user cannot see still count, but are not named.
Platform: Forge SDK updated (api 8.0.4, react 12.1.2, resolver 2.0.0); app storage migrated to the Forge KVS API. npm audit reports no high-severity findings.
- Payment model
- Paid via Atlassian
- License type
- Commercial