How to require multiple approvers in Jira
Plenty of work shouldn’t ship on one person’s say-so — a release, a policy change, a spend. But asking Jira to require several approvers runs into a wall fast: native approvals live in Jira Service Management, or in Jira Software/Business behind a Premium upgrade and a handful of approver-selection gaps. Here’s how multi-approver sign-off actually works, and how to get it on any plan.
What Jira does natively
- In JSM, a workflow status can require approval, including a count like “2 of 3.” It’s solid — if your work lives in Service Management.
- In Jira Software / Business, there’s now a native approval step too — on company-managed and team-managed projects — and it supports setting how many approvals are needed. The catch: it’s Premium or Enterprise only (Free and Standard can’t set it up at all), the approver picker only takes named people or groups (no role-based allow-list), the approval transition bypasses your workflow’s validators and conditions, and you can’t route to different approvers by a field’s value.
- Both are tied to a workflow step. Sequential or staged sign-off still means hand-building extra statuses or steps either way.
So the moment you need multiple approvers without Premium or Enterprise — or without hitting those approver-selection gaps — native runs out of road.
What “multiple approvers” should mean
- All — unanimous sign-off, where every named approver must agree.
- Quorum — “X of N,” so three of five is enough and you’re not blocked by one person on leave.
- Any — a single approval from a named group clears it, for lighter gates.
- With a reason, on the record — each approve or reject captured on the issue, so the decision is auditable — see how to record who approved a Jira issue.
On any project, any plan
Signet adds exactly this, free: name the approvers on the issue and pick all, a quorum, or any; each person approves or rejects with a reason, recorded as an auditable decision — no workflow edits, no admin rights, on any Jira project and plan. For how this compares to the native route, see JSM approvals vs Jira Software approvals and how to add an approval step to a Jira workflow.
The takeaway
Native Jira can require multiple approvers — but mostly inside JSM, or behind Premium with a few approver-selection gaps in Jira Software/Business. Decide whether you need all, a quorum, or any one to sign off, capture each decision with a reason on the issue, and you get auditable multi-approver sign-off without upgrading the whole site.
Frequently asked questions
- Does Jira support multiple approvers natively?
- In Jira Service Management, yes — a workflow status can require several approvers or an "X of N" count, on any plan. Jira Software and Business now have a similar approval step with a required-count setting too, but it's Premium or Enterprise only, and approvers can only be named people or groups, not a role.
- How do I require that everyone approves, not just one person?
- You need an approval rule that supports "all" (unanimous) as well as "any" or a quorum (a set number must agree). JSM and Jira Software/Business (Premium/Enterprise) both support a required count natively; everywhere else, an app covers it.
- Can I add multi-approver sign-off without Premium?
- Yes — an app can add approve/reject with multiple named approvers (all, a quorum, or any one) on any project and any plan, without editing workflows or needing admin rights.
- Is there a record of who approved?
- A good approval tool logs each decision — who approved or rejected, when, and the reason — on the issue, so the sign-off is auditable afterwards.