Skip to main content
complianceApril 1, 2026 · 8 min read

How to Set Up Approval Workflows in Jira: Multiple Approvers and Groups

An approval workflow in Jira is a configured process that requires one or more designated people to formally approve an issue before it can transition to the next status. Teams use it to enforce the four-eyes principle (Vier-Augen-Prinzip) and separation of duties, and to keep an audit trail of who approved and when. If your organization works under SOX or a similar control framework, configure approval gates on the relevant transitions and connect them to the release or deployment process. An approved issue does not by itself block a separate release action.

Why Approval Workflows Matter

Teams in automotive, aerospace, pharma, and finance may need approval records to support their control requirements. Manual approaches like email chains or spreadsheet sign-offs can make those records harder to maintain:

  • Scattered records. Who approved what, and when? Reconstructing approval history from email threads can be time-consuming.
  • No enforcement. Issues can progress without required sign-offs, so the process depends on people remembering to follow it.
  • Sequential delays. Approvers must review one after another, so a one-hour review can become a multi-day wait.
  • Unclear responsibility. Informal approvals can make it harder to identify who was responsible for reviewing a specific change.

Approval workflows can support processes governed by standards and regulations such as:

Check Native Jira Approvals First

Jira Cloud or Jira Data Center? The native features below are for Jira Cloud. Jira Software Data Center does not include native approval steps. Jira Service Management Data Center does have approvals for service requests. Group Sign-Off is available on both Jira Cloud and Jira Data Center.

Jira Cloud and Jira Service Management Cloud have native approval steps. Atlassian's approval setup guide explains how to select approvers, set the required count, and exclude people identified by user fields. Availability depends on your plan and project type. Use native approvals when they meet your policy.

JSM also supports approver groups and records participants and their decisions in the Approvals activity view. Its documented group configuration requires the same number of approvals from each selected group.

Group Sign-Off adds separate thresholds per group at the same gate. For example, Engineering can require two approvals while Security requires one. The steps below cover that setup. For exclusions in either native Jira or Group Sign-Off, see how to prevent self-approval.

Group Sign-Off multi-person approval panel on a Jira issue
Group Sign-Off adds independent approve and decline decisions to the Jira issue while keeping every approver visible.

Try Group Sign-Off free on the Atlassian Marketplace to follow along with the steps below.

Set Up Approvals from Multiple Groups with Group Sign-Off

Group Sign-Off is a Jira app that adds formal, parallel multi-person approval workflows to Jira projects. It is available for Jira Cloud and Jira Data Center. The steps below set it up from scratch.

Step 1: Define Your Approval Groups

Start by mapping your governance model to approval groups. Each group represents a set of people whose sign-off is required for a specific type of decision. Think about who needs to approve, how many approvals are required from each group, and whether the groups should operate independently or in sequence.

For example, a release approval workflow might include:

  • Engineering Review. Requires 2 of 3 senior engineers to approve. Configure requester and implementer exclusions separately.
  • Security Review. Requires 1 security team member, since the security team is small and any member has the authority to approve.
  • Release Approval. Requires both the engineering manager and the QA lead, so sign-off covers both functions.

Group Sign-Off lets you set minimum approval thresholds per group (e.g., "2 of 3 must approve"). Exclusions are configured per approval field using the 4-eyes principle option. Select the user fields that identify the requester or implementer, such as Reporter and Assignee. Follow the self-approval guide and check that each group still has enough eligible reviewers.

Group Sign-Off approval panel showing multiple approval groups with configurable thresholds

Step 2: Configure Workflow Transitions

Configure your groups and thresholds in a Group Sign-Off approval field. Then select that field in the conditions on the Jira workflow transitions you want to protect. Open your Jira workflow in the workflow editor and identify the transitions where formal approval is required. Common examples: "In Review" to "Approved", "Ready for Release" to "Released", or "Change Requested" to "Deployed".

Add a Group Sign-Off condition to each transition you want to protect. Select the approval field and require its final result to be Approved. The condition blocks that transition until the field has that result. Administrators should test every relevant transition and permission path as part of the rollout.

Use separate approval fields when different transitions need different group requirements. A minor bug fix might require only engineering review, while a production deployment requires engineering, security, and management sign-off.

Step 3: Set Up Notifications and Delegation

Approval workflows stall when approvers don't know their input is needed. Configure the app's start notification so the relevant participants are alerted when approval begins.

Define how the team will monitor pending approvals, for example with a Jira filter or dashboard reviewed at an agreed cadence. Approvers can delegate a pending decision to another eligible user when they are unavailable. Each approval field's options control whether approvers can delegate and whether administrators can delegate on an approver's behalf. Document who may receive a delegation and how the team handles an unplanned absence.

Consider using RAG status indicators on dashboards to flag stalled approvals visually. A red indicator for approvals pending more than 48 hours shows project managers where approvals are stuck.

Step 4: Monitor, Report, and Audit

Group Sign-Off records approvals, rejections, and delegations with the acting user and timestamp. Keep the relevant configuration alongside those records. Review settings for revised votes, administrator decision removal, and approval resets when planning retention and reporting.

Use the approval data to identify bottlenecks in your process. If one approval group consistently takes three days while others respond within hours, that is a signal to review group membership or add backup approvers. Track metrics like average approval cycle time, rejection rate, and delegation frequency.

When auditors ask for evidence of your approval process, the timestamped decision history shows who decided, when they decided, and what the outcome was.

Parallel vs. Sequential Approvals

The choice between parallel and sequential approvals affects your cycle time.

Sequential approvals require groups to approve in a fixed order: Engineering first, then Security, then Management. Each group waits for the previous group to finish before they can begin their review. This approach makes sense when later approvals depend on earlier ones (e.g., a security review that should only happen after engineering confirms the implementation is complete).

Parallel approvals allow all groups to review and sign off simultaneously. As soon as an issue enters the approval stage, every approval group is notified and can begin their review immediately.

Consider a release approval that requires sign-off from Engineering, Security, and Management:

  • Sequential: Engineering takes 1 day, Security takes 1 day, Management takes 1 day. With scheduling gaps and timezone differences, the cycle can stretch over several business days.
  • Parallel: All three groups review simultaneously. The cycle time equals the slowest single group instead of the sum of all three.

Why Parallel Approval Shortens the Cycle

Take a safety-critical change that needs sign-off from engineering, safety, and management teams in different time zones. If the reviews run sequentially, the delays add up. Each group waits for the one before it to finish, and every handoff can add a scheduling gap or an overnight wait in someone's queue.

If the same three reviews run in parallel, all three groups are notified at once and can start reviewing immediately. The total wait drops to roughly the time of the slowest group, because that group is the only one still pending once the others finish. The audit record is the same in both cases.

Use parallel approvals when the reviews do not depend on each other. Reserve sequential approvals for cases where one approval stage depends on another.

Native Jira vs. Group Sign-Off: Feature Comparison

Capability Native Jira / JSM Cloud Group Sign-Off
Multi-person approval Native approval steps Configurable group rules
Approval groups Supported in JSM Supported
Different thresholds at one gate JSM requires the same count from each group Separate threshold per group
Decision records Native approval activity App decision history
Reporter and Assignee exclusions Configure in the approval step Configure per field using 4-eyes principle
Workflow gate Native approval step Configured Group Sign-Off condition

Approval workflow overview showing parallel sign-off status across multiple groups

Best Practices for Approval Workflows

  1. Match approval groups to your org chart, not your Jira project structure. Approval authority comes from organizational roles (engineering lead, safety officer, release manager), not from which Jira project an issue belongs to. Define groups based on who has the authority and expertise to approve, and reuse those groups across projects.

  2. Set thresholds for availability and risk. "2 of 3 must approve" is more resilient than "all 3 must approve" because it prevents a single unavailable person from blocking the entire process. For safety-critical decisions where you need every perspective, require full consensus.

  3. Default to parallel approvals and justify any sequential steps. Every sequential step you add puts its full review time on top of the cycle. If Security doesn't actually need to wait for Engineering's approval before starting their review, run them in parallel.

  4. Configure delegation before you need it. Don't wait for someone to go on vacation and block a critical release. Allow delegation on each approval field and agree on backup approvers for every approval group before the first approval starts.

  5. Record rejection reasons. Require approvers to provide a reason when they reject. Group Sign-Off can make a comment mandatory for declines and records it on the issue. Authors learn what to fix, and recurring reasons show what to change at the process level.

  6. Review approval metrics monthly, not just for audits. Track average cycle time, rejection rate, and which groups are bottlenecks. A monthly review of these metrics helps you find process problems before they become compliance issues.

Key Takeaways

  • Native Jira Cloud approvals support multiple reviewers, configured exclusions, and decision records. Group Sign-Off adds separate group thresholds when your policy needs them.
  • Parallel approvals can shorten cycle time, because the total wait is the slowest single group instead of the sum of every group.
  • Keep decision records, the applicable policy, and configuration evidence together. Assess retention and reporting against your requirements.
  • Approval groups should map to organizational authority, with configurable thresholds (e.g., "2 of 3") to balance rigor with resilience.
  • Agree on backup approvers and delegation before an approver is unavailable.

Getting Started

Group Sign-Off works with your existing Jira workflows. Add approval groups, attach them to transitions, and test each gated transition before you roll it out.

Start a free trial on the Atlassian Marketplace to see how parallel multi-person approvals work in your Jira environment. It is available for Jira Cloud and Jira Data Center.

For more on compliance workflows, read our guide to the four-eyes principle in Jira.