What you get
- Approvals happen on the Jira issue your team is already looking at
- Your rules live in one place in Decionis — not scattered across Forge apps
- Every decision leaves a signed receipt anyone can verify
Loading…
Atlassian Forge private distribution
Pilot ready
Atlassian Marketplace
Catch a risky Jira change before it ships — without leaving Jira.
When someone makes a high-stakes change in Jira or an admin panel, Decionis checks it against your rules and answers right on the issue: allow, block, or escalate. Every call comes with signed proof, so nothing slips through and an audit takes minutes instead of days.
Forge is the primary install path (private installs and invite-only listing); legacy Connect webhooks remain for compatibility. Confluence is not a native ingestion pipeline.
Adapter: AvailableWorkflow: AvailableDocs: Available
Integration scope
- Installs through Atlassian Forge (private install link or invite-only listing)
- Wraps the Decionis decision check around risky Jira actions and admin changes
- Syncs the Jira issue lifecycle and attaches a verifiable Decision Dossier link
Launch posture: Pilot ready. Documentation pack: docs/marketplace/atlassian
How it works — install to first decision
- 1Install from Atlassian
Add Decionis from the Forge install link — your workspace and credentials are provisioned automatically from your Atlassian session, with no separate signup.
- 2Pick the changes to govern
Choose which Jira actions and admin changes need a check — deploys, permission changes, field edits.
- 3Watch in shadow mode
Decionis records what it would have decided on each issue, so you see the calls before anything is blocked.
- 4Turn on enforcement
Flip to enforce — risky changes now wait for an allow, block, or escalate, each with a signed receipt on the issue.