Jira approval app alternatives: Approval Flow compared with 9 others
Approval Flow for Jira next to 9 alternatives for Jira: installs, prices and features. We make Approval Flow for Jira, so treat this page as a vendor's comparison and check the sources: every value for another app links to the page we read. "Unknown" means we did not find the answer in the pages we read, not that the feature is missing.
Data collected: Marketplace figures, prices, and the Runs on Atlassian and Cloud Fortified rows checked on 18 October 2026; other feature values read on 12 October 2026 (two apps added 15 October 2026). Features and prices change. If you find an error, write to support@stankiguild.com and we will correct it.
Our column was checked against the code of the production version, Approval Flow 3.0.0. Approval Flow for Jira is on the Atlassian Marketplace. What each feature does is in the documentation.
The apps
#Marketplace figures and monthly list prices in USD, from the Atlassian Marketplace on 18 October 2026. For Atlassian's own features the price is an estimate, not a list price: the difference between the Standard and Premium per-user prices on Atlassian's pricing page, as the note under that row says. "10 users" is the price of the 10-user tier; 50 and 250 users use the graduated per-user rates. Installs may include Server and Data Center.
| App | Vendor | Installs | Rating (reviews) | Last release | Free tier | Per user, 1-100 | 10 users | 50 users | 250 users |
|---|---|---|---|---|---|---|---|---|---|
| Approval Flow for Jira (ours) List prices; installs and ratings are on the Marketplace listing | Stanki Guild | See listing | See listing | See listing | yes, 10-user tier $0.00 | $0.90 | $0.00 | $45.00 | $210.00 |
| Herzum Approval | STAGIL by catworkx | 301 | 2.81 (16) | 2026-08-25 | no (10-user tier $10.00/month) | $1.00 | $10.00 | $50.00 | $242.50 |
| Approval Path for Jira | Warsaw Dynamics | 245 | 5.00 (29) | 2026-10-12 | no (10-user tier $10.00/month) | $1.25 | $10.00 | $62.50 | $282.50 |
| Group Sign-Off | Werkstack GmbH | 210 | 4.88 (41) | 2026-09-16 | no (10-user tier $5.50/month) | $0.94 | $5.50 | $47.00 | $235.00 |
| Approval for Jira (Candylio) | Candylio Solutions | 28 | 4.64 (8) | 2026-08-24 | no (10-user tier $10.00/month) | $1.00 | $10.00 | $50.00 | $235.00 |
| Quorum Approvals for Jira | Smiling Monkey | 4 | 5.00 (3) | 2026-10-17 | yes, 10-user tier $0 | $0.80 | $0.00 | $40.00 | $200.00 |
| Business Sign-off (Cahaba Forge) | Cahaba Forge | 5 | None yet | 2026-10-02 | yes, 10-user tier $0 | $0.91 | $0.00 | $45.50 | $206.50 |
| eSign Signatures for Jira | Digital Rose | 686 | 5.00 (10) | 2026-09-14 | yes, 10-user tier $0 | $1.30 | $0.00 | $65.00 | $310.00 |
| Signet: Approvals & Sign-off for Jira | Datum | 1 | None yet | 2026-10-12 | yes, 10-user tier $0 | $0.75 | $0.00 | $37.50 | $187.50 |
| Jira Premium approvals (native) Estimate, not a price list: the difference between the Standard ($8.48) and Premium ($15.56) per-user monthly prices on https://www.atlassian.com/software/jira/pricing on 2026-10-18, times users. Atlassian's rates vary by user tier, and the upgrade buys much more than approvals. Available since 2026-02-20 in team- and company-managed spaces (https://jirareleases.atlassian.com/announcements/approvals-that-keep-work-moving). | Atlassian | native (part of the Atlassian plan) | - | - | no (Premium and Enterprise plans only) | $7.08 | $70.80 | $354.00 | $1,770.00 |
Cost calculator
#Monthly list price for your team size, from the same prices as the table above: the 10-user tier price up to 10 users, then the graduated per-user rates. The range stops at 250 users because that is as far as the collected prices go.
| App | Per month | Per user |
|---|---|---|
| Approval Flow for Jira (ours) | $45.00 | $0.90 |
| Herzum Approval | $50.00 | $1.00 |
| Approval Path for Jira | $62.50 | $1.25 |
| Group Sign-Off | $47.00 | $0.94 |
| Approval for Jira (Candylio) | $50.00 | $1.00 |
| Quorum Approvals for Jira | $40.00 | $0.80 |
| Business Sign-off (Cahaba Forge) | $45.50 | $0.91 |
| eSign Signatures for Jira | $65.00 | $1.30 |
| Signet: Approvals & Sign-off for Jira | $37.50 | $0.75 |
| Jira Premium approvals (native) (estimate) | $354.00 | $7.08 |
Where another option is ahead
#Taken from the feature table below: rows where a listed alternative has a better value than ours. Yes and Paid count as equal, except that Yes in an alternative that costs nothing at any team size is ahead of our Paid, and our Yes (available without a licence) is ahead of Paid. Partial is behind both, No is behind Partial. Unknown values are not counted.
- Lowest per-user price among the paid apps: Signet: Approvals & Sign-off for Jira, $0.75 per user per month for users 1 to 100; ours: $0.90.
- Approve by email or Slack: Approval Path for Jira (Yes), Herzum Approval (Yes); ours: Partial.
- Published, with installs and reviews: Quorum Approvals for Jira (Partial), Approval Path for Jira (Yes), Herzum Approval (Yes), Group Sign-Off (Yes), Business Sign-off (Cahaba Forge) (Partial), Jira Premium approvals (native) (Yes), eSign Signatures for Jira (Yes), Signet: Approvals & Sign-off for Jira (Partial); ours: No.
- Cloud Fortified (Marketplace security program): Approval Path for Jira (Yes), eSign Signatures for Jira (Yes); ours: No.
Where we are ahead
#Rows where our value is better than every alternative with a known value. Here our Yes counts only as equal to Paid, so doubtful cases go in the alternatives' favour.
- Verification anchor and raw-block export with recipe: ours: Yes; eSign Signatures for Jira (Partial).
- Evidence export across a JQL filter: ours: Paid; eSign Signatures for Jira (Partial).
- Template library: ours: Paid; Quorum Approvals for Jira (Partial).
Features
#Yes: included. Paid: only with a paid licence or plan. Partial: some of it. No: not offered. Unknown: not found in the pages we read. Values for other apps link to their source.
Free tier
| Feature | Approval Flow (ours) | Quorum Approvals for Jira | Approval Path for Jira | Herzum Approval | Group Sign-Off | Business Sign-off (Cahaba Forge) | Jira Premium approvals (native) | eSign Signatures for Jira | Signet: Approvals & Sign-off for Jira |
|---|---|---|---|---|---|---|---|---|---|
| Usable at $0 | Yes Free for up to 10 users with every feature. Above 10 users without a licence: up to 500 requirements per work item, as with a licence, with validator, quorum and separation of duties. | Yes 10-user tier $0 | No 10 users $10 | No 10 users $10 | No 10 users $5.50 | Yes 10-user tier $0 | No Premium and Enterprise only | Yes 10-user tier $0 | Yes 10-user tier $0 |
| Works on Jira Free and Standard | Yes Marketplace app, any paid or free Jira plan. | Yes | Yes | Yes | Yes | Yes | No "only available on Premium editions in Jira" | Yes | Yes "Approval sign-off for any Jira project, on any plan" |
Approval logic
| Feature | Approval Flow (ours) | Quorum Approvals for Jira | Approval Path for Jira | Herzum Approval | Group Sign-Off | Business Sign-off (Cahaba Forge) | Jira Premium approvals (native) | eSign Signatures for Jira | Signet: Approvals & Sign-off for Jira |
|---|---|---|---|---|---|---|---|---|---|
| Multiple approvers with quorum (N of M) | Yes 1 to 10 distinct approvers per requirement, up to 20 named approvers. Or every named approver (a group or role member does not fill a named seat), or the first decision counts (all tiers). | Yes any one, N of M, all or veto | Yes no verbatim quote recorded for this cell | Yes no verbatim quote recorded for this cell | Yes no verbatim quote recorded for this cell | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Yes "how many approvals are needed" | Yes validator can "Restrict by number of signatures, pending signatures, current user" | Yes "whether it needs any one, a quorum, or all of them to agree" |
| Workflow validator blocks the transition | Yes Fails closed. | Yes no verbatim quote recorded for this cell | Yes no verbatim quote recorded for this cell | Yes "Tutorial to add the Herzum Approval Validator to your workflow" (checked 2026-10-18) | Yes no verbatim quote recorded for this cell | Yes "Phase Gate Enforcement" | Yes approval step on a status | Yes "Includes workflow validator to control transitions" | Unknown not mentioned in the vendor pages read on 2026-10-15; absence not confirmed |
| Separation of duties (no self-approval) | Yes Creator cannot approve own requirement. | Yes no verbatim quote recorded for this cell | Yes no verbatim quote recorded for this cell | Yes "Excluded: shows the properties identifying the users to exclude" (checked 2026-10-18) | Yes "they cannot approve their own issues" | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Partial "Exclude approvers from" setting; explicit self-approval rule not documented | Unknown not mentioned in the vendor pages read on 2026-10-15; absence not confirmed | Unknown not mentioned in the vendor pages read on 2026-10-15; absence not confirmed |
| Sequential stages | Yes Stages 1 to 9; stage N opens after all lower stages; all tiers. | Yes no verbatim quote recorded for this cell | Yes "run steps in sequence or in parallel" | Yes "Sequential approvals" | Yes "necessary to decide sequentially" | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Yes "Sequential or Parallel Signatures" (new in 2026) | Unknown not mentioned in the vendor pages read on 2026-10-15; absence not confirmed |
| Groups and project roles as approvers | Paid Groups and roles checked live with licence; named approvers free. Approvers can also come from a user-picker field, kept in sync when it changes, under the admin lock and separation of duties; an emptied field never clears the approvers, and a field that is still empty, with no group or role, closes the requirement instead of opening it to anyone (paid). | Yes route to groups by field | Yes "user, group, manager, role, or field" | Yes no verbatim quote recorded for this cell | Yes no verbatim quote recorded for this cell | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Partial groups yes; "we weren't able to accomodate using roles" | Yes "Invite Users and/or Groups to Sign"; signature types restricted by user roles | Unknown listing describes named approvers only; not mentioned in the vendor pages read on 2026-10-15; absence not confirmed |
| Delegation (out-of-office substitutes) | Yes Receipt records both people; all tiers. Also applies to requirements created by approval rules (2026-10-12). | Yes "delegation while away" | Yes "delegation" | Yes "The Approval Delegation screen allows delegating user Approval authority to other qualified operators on a Project, Issue Type, and Time range basis." | Yes "admins can delegate on behalf of others" | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Unknown not mentioned in the vendor pages read on 2026-10-15; absence not confirmed | Unknown not mentioned in the vendor pages read on 2026-10-15; absence not confirmed |
| Conditional approval rules (approvers by field values) | Paid Up to 50 app-wide rules, 10 conditions each (= != > >= < <= in contains, match all or any); each match adds a Required requirement with named approvers or groups, on creation or from the panel. Not verified live. Jira expressions as conditions, an admin preview, and transition gates the validator evaluates (paid). | Yes "Route to groups by field"; "Approvers can be configured from groups, people or fields of the work item" | Yes "conditional rules using JQL, budget, location, or Jira fields" | Yes "Custom Conditional Rules you can easily create advanced expressions in JQL to enhance your approval mapping rules" | Yes "multiple sets of deciders depending on issue fields and other aspects" | No vendor positioning: "Keep existing workflows and avoid approval-only statuses or a separate approval rule builder"; its validator has group or role rules (AND/OR), not field-based routing | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Partial invite post function can invite "all users from groups set on the issue group field"; predefined signees by space and issue type; no rules on other field values found | Unknown not mentioned in the vendor pages read on 2026-10-15; absence not confirmed |
| Reset sign-offs when the work changes | Paid Watched fields per requirement (summary, description, any field id); a change clears sign-offs with a log entry. | Yes no verbatim quote recorded for this cell | Yes no verbatim quote recorded for this cell | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Yes "Reset decisions cleanly and request a re-review when the work changes" | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Partial "detection if the issue has changed since each signature was captured"; signatures are reset or voided by workflow post functions, not automatically on edit | Unknown not mentioned in the vendor pages read on 2026-10-15; absence not confirmed |
| Decision expiry | Paid Sign-offs valid for N days per requirement; hourly job expires them, validator applies the rule immediately. | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Yes "Approval Validity Expiration" | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Unknown signing PINs expire after 180 days, signatures do not as far as we read; not mentioned in the vendor pages read on 2026-10-15; absence not confirmed | Unknown not mentioned in the vendor pages read on 2026-10-15; absence not confirmed |
Notifications
| Feature | Approval Flow (ours) | Quorum Approvals for Jira | Approval Path for Jira | Herzum Approval | Group Sign-Off | Business Sign-off (Cahaba Forge) | Jira Premium approvals (native) | eSign Signatures for Jira | Signet: Approvals & Sign-off for Jira |
|---|---|---|---|---|---|---|---|---|---|
| Reminders | Paid Hourly trigger, email sent by Jira itself (issue notify), off by default; project roles get escalation only. | Yes notifications | Yes "reminders" | Partial via automation | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Partial notification only, per research A5 | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Unknown invite emails only; re-inviting sends a new email; no scheduled reminder found; absence not confirmed | Unknown not mentioned in the vendor pages read on 2026-10-15; absence not confirmed |
| Escalation | Paid One escalation per sign-off to reporter, assignee and requirement author. | Yes "escalate on deadline" | Yes "automatic escalation" | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Unknown not mentioned in the vendor pages read on 2026-10-15; absence not confirmed | Unknown not mentioned in the vendor pages read on 2026-10-15; absence not confirmed |
| Approve by email or Slack | Partial Deliberately not: a link or a chat button cannot prove who clicks. Jira Automation with List pending approvers posts to Slack or Teams, or e-mails the approvers, with a link to My approvals; the decision happens signed in to Jira. Recipes published as a guide; not yet run live. | No "nobody decides by replying" | Yes "An Email step sends the decision to an email address rather than a Jira account" (checked 2026-10-18) | Yes no verbatim quote recorded for this cell | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Partial invite email links to the work item, signing happens in Jira with a PIN; Slack or Teams messages via Jira Automation webhooks | Unknown not mentioned in the vendor pages read on 2026-10-15; absence not confirmed |
History and audit
| Feature | Approval Flow (ours) | Quorum Approvals for Jira | Approval Path for Jira | Herzum Approval | Group Sign-Off | Business Sign-off (Cahaba Forge) | Jira Premium approvals (native) | eSign Signatures for Jira | Signet: Approvals & Sign-off for Jira |
|---|---|---|---|---|---|---|---|---|---|
| Decision log on the work item (who, when) | Yes Every approve, reject, unapprove, edit and deletion logged; erased signatures leave a trace. Kept under the work item id, so requirements, receipts and the log follow a work item moved to another project (the move is logged). | Yes | Yes "Auditors can look at the Activity log" (checked 2026-10-18) | Partial summary logged as a comment; audit log covers admin configuration | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Yes CSV for SOC 2, SOX, ITGC | Yes "logged on the work item showing who approved or rejected and when" | Yes "Signature Audit Events are collected for every signature action" in a Signature Audit tab on the work item | Yes "auditable decision record - who approved or rejected, and when - sits on the issue itself" |
| Tamper-evident hash-chained log | Yes SHA-256 chain, blocks written FAIL_IF_EXISTS before the record; blocks hold pseudonyms, not accountIds. | Yes "SHA-256 over the previous hash and the canonical JSON of the entry" | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Unknown a hash chain is described for Cahaba in https://community.atlassian.com/forums/Jira-questions/How-do-you-prepare-change-management-evidence-from-Jira-for/qaa-p/3268068 (vendor post), not on the listing | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Partial a checksum of summary, description and attachment metadata is stored with each signature to detect later edits; no hash chain over the log found | Unknown not mentioned in the vendor pages read on 2026-10-15; absence not confirmed |
| Verification anchor and raw-block export with recipe | Yes JSON export has raw blocks and the recipe; a test recomputes the chain with plain crypto. | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Partial verification certificate re-checks signatures against the current work item; no raw export or recipe for independent recomputation found | Unknown not mentioned in the vendor pages read on 2026-10-15; absence not confirmed |
Export
| Feature | Approval Flow (ours) | Quorum Approvals for Jira | Approval Path for Jira | Herzum Approval | Group Sign-Off | Business Sign-off (Cahaba Forge) | Jira Premium approvals (native) | eSign Signatures for Jira | Signet: Approvals & Sign-off for Jira |
|---|---|---|---|---|---|---|---|---|---|
| CSV export | Yes Per work item CSV/JSON in all tiers; project-level CSV on Approval health (paid). | Yes CSV reports per research A5 | Yes "export the Approvals list as CSV files" (checked 2026-10-18) | Yes "download the filtered approval history data as a CSV" (checked 2026-10-18) | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Yes "Export to CSV" | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Partial signature custom fields "available to include on Jira issue screens, JQL search and exports" (Jira's own export); the app's reports are PDF | Unknown not mentioned in the vendor pages read on 2026-10-15; absence not confirmed |
| Evidence export across a JQL filter | Paid Runs as the user, cursor paging. Plus an audit evidence pack per JQL: one PDF and one CSV with every decision, chain verdicts and Checklist Flow state, up to 500 work items. | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Partial Bulk Verify Report from a Jira search: one consolidated report, up to 100 work items in one space, printed or saved to PDF | Unknown not mentioned in the vendor pages read on 2026-10-15; absence not confirmed |
E-signature
| Feature | Approval Flow (ours) | Quorum Approvals for Jira | Approval Path for Jira | Herzum Approval | Group Sign-Off | Business Sign-off (Cahaba Forge) | Jira Premium approvals (native) | eSign Signatures for Jira | Signet: Approvals & Sign-off for Jira |
|---|---|---|---|---|---|---|---|---|---|
| Signature PIN (e-signature step-up) | Paid scrypt-hashed PIN, 5 failures lock 15 min, admin reset logged; PIN per requirement, signature meaning (Approved, Reviewed, Responsible) and a hash of the signed terms on each sign-off; approval certificate PDF per work item. Proves knowledge of a secret only; no 21 CFR Part 11 claim. Forge cannot re-prompt the Atlassian password. | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Yes authenticate before deciding with "the built-in feature of multi-factor authentication (MFA)" (checked 2026-10-18) | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | No a user asks for username/password e-signature; not offered | Yes "Multi-factor authentication with personal Signature Pins"; one-time PINs optional | Unknown not mentioned in the vendor pages read on 2026-10-15; absence not confirmed |
Reporting
| Feature | Approval Flow (ours) | Quorum Approvals for Jira | Approval Path for Jira | Herzum Approval | Group Sign-Off | Business Sign-off (Cahaba Forge) | Jira Premium approvals (native) | eSign Signatures for Jira | Signet: Approvals & Sign-off for Jira |
|---|---|---|---|---|---|---|---|---|---|
| JQL functions or approval status fields | Yes Indexed issue property: approvalStatus, approvalApproved, approvalRequired, approvalPendingFor, in every edition; approvalDue needs a paid licence (due dates). Verified live 2026-10-12: approvalStatus = "pending" and approvalPendingFor = currentUser() return SGS-1. Plus a read-only "Approval status" custom field ("2/3 approved") for List View and the navigator, written with or without a licence; card layouts not yet checked live. | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Yes "Searching approvals with JQL"; approval state also as Jira fields (checked 2026-10-18) | Yes "more than twenty built-in JQL functions" | Yes no verbatim quote recorded for this cell | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Yes JQL | Yes "JQL indexed search to identify pending (invited) signatures"; signature count and signee fields | Unknown not mentioned in the vendor pages read on 2026-10-15; absence not confirmed |
Usability
| Feature | Approval Flow (ours) | Quorum Approvals for Jira | Approval Path for Jira | Herzum Approval | Group Sign-Off | Business Sign-off (Cahaba Forge) | Jira Premium approvals (native) | eSign Signatures for Jira | Signet: Approvals & Sign-off for Jira |
|---|---|---|---|---|---|---|---|---|---|
| Personal approval queue and bulk decisions | Paid My approvals page with bulk approve or reject (max 50) through the same decision path, one PIN for the batch. Each row has full-width one-tap Approve and Reject for phone browsers; a link can put one work item first. The work item panel opens with your sign-offs first, settings behind one button. | Yes "Personal queue" | Yes no verbatim quote recorded for this cell | Yes no verbatim quote recorded for this cell | Yes no verbatim quote recorded for this cell | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Yes My Signature Invites on the Signature Dashboard; "sign up to 100 work items at one time" | Unknown not mentioned in the vendor pages read on 2026-10-15; absence not confirmed |
| Template library | Paid 24 templates (CAB, emergency and standard change, release go/no-go, purchase tiers, access, security exception, contracts, HR, expenses and more), installed as ordinary policies; quorums and stages preset, approvers never preset. Not verified live. | Partial release notes: "five starting shapes" (checked 2026-10-18) | Unknown closest found: reusable approval definitions and AI prompt templates; no ready-made approval template library found | Unknown templates found are e-mail templates only; not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Unknown not mentioned in the vendor pages read on 2026-10-15; absence not confirmed | Unknown not mentioned in the vendor pages read on 2026-10-15; absence not confirmed |
Integration
| Feature | Approval Flow (ours) | Quorum Approvals for Jira | Approval Path for Jira | Herzum Approval | Group Sign-Off | Business Sign-off (Cahaba Forge) | Jira Premium approvals (native) | eSign Signatures for Jira | Signet: Approvals & Sign-off for Jira |
|---|---|---|---|---|---|---|---|---|---|
| Jira Service Management support | Paid Panel, glance and validator work in JSM; read-only customer portal view, off by default. Portal not yet tried live. | Partial "Deciding as a customer without a JSM/CSM licence is being validated for v1.0" (checked 2026-10-18) | Yes no verbatim quote recorded for this cell | Yes no verbatim quote recorded for this cell | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Partial JSM has its own native approvals with numeric and percentage quorum | Yes "Service Management Portal allows signatures to be captured for unlimited public customer accounts" | Unknown app page names "Jira Software and Business projects"; not mentioned in the vendor pages read on 2026-10-15; absence not confirmed |
| Automation for Jira actions | Paid 8 actions: Request approval, Get approval status (also status, label, pending and overdue counts, next due, current stage), Reset approval, List pending approvers, Add approver, Set approval due date, Set approval stage, Apply approval policy. The first three verified live 2026-10-12 on our own test site; the rest not yet verified live. | Yes "Four Jira Automation actions": Start, Cancel, Get status, Send reminder; "Automation cannot approve or reject" | Yes "native Approval Path actions" to Start, Archive or Delete approvals from a rule | Partial reminders driven by a Jira Automation rule that edits a field or adds a comment; no app-specific Automation action found | Partial "please use Jira Automation to assign a JSON object" to the field; no app-specific Automation action found | No "Automation rules cannot directly invoke BSO approval actions or write to the read-only BSO fields. They can, however, read the BSO fields in conditions" | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Partial webhooks on Invite, Execute, Decline and Finalize trigger Jira Automation rules (incoming webhook); no app-specific Automation action found | Unknown not mentioned in the vendor pages read on 2026-10-15; absence not confirmed |
| Rovo AI assistant (summary, risks, who still has to sign; never approves) | Paid Rovo agent with 6 actions: summarize approval and risks, who still needs to sign, what changed since a sign-off, an audit narrative built from the record without AI, suggest an approval policy (read only), and request approval with a template (preview, writes only after confirmed, logged with the source rovo); it never approves, rejects or signs. Skills and an Ask the assistant button in the panel. Optional: everything else works without Rovo. No egress, no LLM cost to us. Verified live on our test site on 2026-10-15: the assistant summarised a work item using summary and risks, who still signs, what changed since sign-off and suggest policy. | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Partial "AI Prompt Step" inside an approval path (AI output shown to approvers), not a Rovo chat assistant | Yes "Herzum Approval Rovo Agent": analyse history, search approval status, and "Perform Approval Actions (Approve, Reject, Abstain)" (ours deliberately never decides) | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Unknown not mentioned in the vendor pages read on 2026-10-15; absence not confirmed | Unknown not mentioned in the vendor pages read on 2026-10-15; absence not confirmed |
Data and privacy
| Feature | Approval Flow (ours) | Quorum Approvals for Jira | Approval Path for Jira | Herzum Approval | Group Sign-Off | Business Sign-off (Cahaba Forge) | Jira Premium approvals (native) | eSign Signatures for Jira | Signet: Approvals & Sign-off for Jira |
|---|---|---|---|---|---|---|---|---|---|
| GDPR: personal data reporting and closed-account erasure | Yes Weekly report in batches of 90; closed accounts erased, quorum preserved via anon pseudonyms; a requirement whose only approver was erased stays closed until a new approver is named; unverified live. | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Unknown not mentioned in the vendor pages read on 2026-10-12; absence not confirmed | Yes native data; no source link recorded in our data | Unknown policy says site administrators can remove signatures on request; personal data reporting not mentioned; absence not confirmed | Unknown not mentioned in the vendor pages read on 2026-10-15; absence not confirmed |
| Runs on Atlassian (no data egress) | Yes storage:app plus Atlassian REST only (notify is an Atlassian API, not egress); badge assigned only after publishing. | Yes Marketplace listing data "isForgeROACompliant": true (checked 2026-10-18) | No Marketplace listing data "isForgeROACompliant": false; vendor FAQ: "Our Cloud apps run on OVH Cloud infrastructure in Poland (EU)" (checked 2026-10-18) | No Marketplace listing data "isForgeROACompliant": false (checked 2026-10-18) | No Marketplace listing data "isForgeROACompliant": false; werkstack.dev/trust: "Some of its pages are still delivered from Werkstack's servers" (checked 2026-10-18) | Yes Marketplace listing data "isForgeROACompliant": true (checked 2026-10-18) | Yes native data; no source link recorded in our data | No Marketplace listing data "isForgeROACompliant": false (checked 2026-10-18) | Yes Marketplace listing data "isForgeROACompliant": true (checked 2026-10-18) |
Track record
| Feature | Approval Flow (ours) | Quorum Approvals for Jira | Approval Path for Jira | Herzum Approval | Group Sign-Off | Business Sign-off (Cahaba Forge) | Jira Premium approvals (native) | eSign Signatures for Jira | Signet: Approvals & Sign-off for Jira |
|---|---|---|---|---|---|---|---|---|---|
| Published, with installs and reviews | No Not yet public on Marketplace (in review since 2026-10-13); tested on our own Atlassian test site. | Partial 4 installs, 3 reviews (checked 2026-10-18) | Yes | Yes | Yes | Partial 5 installs, 0 reviews (checked 2026-10-18) | Yes | Yes | Partial 1 install, 0 reviews (checked 2026-10-18) |
| Cloud Fortified (Marketplace security program) | No Not yet: the listing is in Marketplace review and not public, so the program has not been applied for. | No Marketplace REST "programs.cloudFortified": not listed (checked 2026-10-18) | Yes Marketplace REST "programs.cloudFortified": approved (checked 2026-10-18) | No Marketplace REST "programs.cloudFortified": not listed (checked 2026-10-18) | No Marketplace REST "programs.cloudFortified": not listed (checked 2026-10-18) | No Marketplace REST "programs.cloudFortified": not listed (checked 2026-10-18) | Unknown Atlassian's own feature, not a Marketplace app | Yes Marketplace REST "programs.cloudFortified": approved (checked 2026-10-18) | No Marketplace REST "programs.cloudFortified": not listed (checked 2026-10-18) |
Common questions
#Is this comparison independent?
No. We make Approval Flow for Jira, so this is a vendor's comparison. Every value for another app links to the page it comes from, and we correct errors reported to support@stankiguild.com.
How current are the prices and install counts?
Installs, ratings, latest releases and prices were fetched from the Atlassian Marketplace on 18 October 2026. Feature values were read from each vendor's pages on 12 October 2026 (two apps added 15 October 2026). Our own prices are our list prices: the listing is on the Atlassian Marketplace.
Which listed app costs least at 50 users?
Among the paid apps, Signet: Approvals & Sign-off for Jira is the lowest at 50 users: $37.50 per month. Ours: $45.00 per month at 50 users (list price).
What does Unknown mean in the feature tables?
That we did not find the answer in the pages we read. It does not mean the feature is missing.
Atlassian, Jira, Confluence and Jira Service Management are trademarks of Atlassian. Other product names are trademarks of their owners and are used only to identify those products. Stanki Guild is not affiliated with, endorsed or sponsored by Atlassian or by any vendor named on this page.