OVERALL RATINGS
INSTALLS
1
SUPPORT
- Partner Supported
TRUST SIGNALS
Key highlights of the appApproval workflow with multi-approver sign-offs that block the transition: stages, groups, separation of duties, audit trail
No transition without sign-off
A workflow validator blocks the transition until every required sign-off is in, and tells the person how many are open. Separation of duties keeps people from approving what they added or assigned.
Approve many, enter your PIN once
In My approvals, select sign-offs and approve them together. Your PIN is checked once and covers the rest of the run for 5 minutes. Each decision still gets its own audit entry.
Agents ask, people sign
Pro, off by default, Preview. An AI agent can ask a person to sign off one concrete action and gets a signed receipt after approval. There is no approve tool, and the agent’s own user can never decide it.
Supporting media
More details
Free for up to 10 users, with every feature.
Atlassian’s own approvals for Jira work items need Premium or higher. Approval Flow does not.
- A workflow validator blocks the transition until required sign-offs are in
- Approvers by name, group or project role, in sequential stages
- Separation of duties: no approving what you added or assigned
- Rejection with a required reason; optional signature PIN
- My approvals with bulk approval and one PIN per run; Team overview
- Approval rules and 24 ready policies, auto-applied by issue type
- Hash-chained audit trail, JSON and CSV export, check against an earlier export
- JQL fields, Jira Automation actions and a customer portal view
- Pro: an approval gate for AI agent actions, off by default (Rovo MCP is Preview)
Runs on Atlassian: data stays in Forge storage on your site, no calls outside Atlassian. Reminder e-mails go out only if an administrator turns them on.
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
Approval Flow: Required Sign-Offs for Jira integrates with your Atlassian app
Version information
Version 3.0.0•for Jira Cloud
- Release date
- Oct 30th 2026
- Summary
- 3.0: bulk approval with one PIN, agent approval gate, more separation of duties
- Details
New in 3.0
- Bulk approval asks for your PIN once per run. It stays valid for 5 minutes for the exact set you selected, so a run of 50 no longer stops after 10.
- Agent approval gate (Pro, off by default): an AI agent can ask a named group to sign off one action on a work item and gets a signed receipt. It has no approve tool, and the user the agent works for cannot decide it. Needs a PIN. Rovo MCP is Preview.
- Separation of duties now also covers whoever last assigned the approvers.
- A required sign-off must name who may sign it.
- Repeated wrong codes lock signing, with a Jira notification.
- New scopes: write:app-data:jira and read:cmdb-object:jira. Admins must approve the update.
- Payment model
- Paid via Atlassian
- License type
- Commercial