How to Add Approval in Jira Workflow

Most teams lose hours every week waiting on sign-offs that nobody knew were pending.

A Jira approval workflow fixes that. It bakes the review step directly into your process — so nothing moves forward until the right person says yes. No Slack messages, no email chains, no “did you see my request?” follow-ups.

This guide walks you through exactly how to add approval steps in Jira workflows, whether you’re using Jira Software, Jira Service Management, or Jira Work Management.

What Is a Jira Approval Workflow?

A Jira approval workflow adds a formal review gate inside your issue lifecycle. Instead of moving from “In Progress” directly to “Done,” the issue pauses at an “Awaiting Approval” status. A designated person — or group — reviews and either approves or rejects it.

Approvals are especially useful for:

• Change requests that need manager sign-off
• Budget approvals tied to project issues
• Content or design reviews before publishing
• IT or security clearance steps in service desk tickets

According to Atlassian’s own platform data, teams that implement structured Jira workflows reduce manual status update requests by up to 60%. Research from McKinsey also found that automating routine approval and review steps can save knowledge workers 1.5 hours per day — time that goes directly back into high-value work.

What You Need Before You Start

Before configuring approvals, confirm a few things:

• You have Project Admin or Jira Admin access
• You’re using Jira Service Management (for native approvals) or a Jira Software/Work Management project (where approvals require workflow customization)
• Your project is company-managed — team-managed projects have limited workflow editing options

Jira Service Management supports approvals natively. For Jira Software and Work Management, you’ll build the approval logic using statuses, transitions, and conditions.

How to Add Approval in Jira Service Management

Jira Service Management (JSM) has a built-in approval feature. Here’s how to turn it on.

Go to Your Project Settings

Open your JSM project. In the left sidebar, click Project settings, then navigate to Request types.

Select the Request Type

Choose the request type where you want to add an approval step. Click into it to open the field configuration.

Add the Approvers Field

In the request type editor, click Add a field. Search for and add the Approvers field. This field lets you specify who needs to approve the request.

You can set the approvers to:

• A specific user
• A group of users (any one can approve)
• A role assigned to the project

Enable the Approval Step in the Workflow

Go to Project settings > Workflows. Click the workflow linked to your request type, then select Edit.

In the workflow editor, find the status where approval should occur — typically something like “Waiting for Approval.” Click on that status, then enable the Approvals toggle in the status configuration panel.

Set the rule:

• Approved transitions the issue forward (e.g., to “In Progress” or “Resolved”)
• Declined transitions the issue back (e.g., to “Cancelled” or back to “Open”)

Click Publish when done.

Notify Approvers Automatically

Go to Project settings > Notifications. Add a rule that sends an email or Jira notification to the Approver when an issue enters the approval status. This ensures nobody misses a pending review.

How to Add Approval in Jira Software (Company-Managed)

Jira Software doesn’t have a native approval toggle, but you can replicate the behavior using workflow statuses, transitions, and conditions.

Open the Workflow Editor

Go to Project settings > Workflows. Select the workflow you want to edit and click Edit (or Diagram to use the visual editor).

Add an “Awaiting Approval” Status

Click the + icon or drag from an existing status to create a new one. Name it Awaiting Approval (or whatever fits your team’s language). Set the category to In Progress so it shows up correctly on boards.

Create Transitions Into and Out of the Status

Add two transitions from the “Awaiting Approval” status:

• Approved — transitions to your next step (e.g., “Ready for Dev” or “Done”)
• Rejected — transitions back to the previous step (e.g., “Open” or “To Do”)

Add a Condition to the Approval Transition

Click on the Approved transition. Go to Conditions and add a condition such as User Is in Project Role or Only Assignee Can Perform Transition. This restricts who can click “Approved” — enforcing that only the right person can move the issue forward.

Add a Validator (Optional but Recommended)

Add a Field Required validator to the transition so approvers must leave a comment or fill a field before approving. This creates an audit trail.

Publish the Workflow

Click Publish and associate the workflow with your project scheme if prompted.

How to Add Approval in Jira Work Management

Jira Work Management (JWM) projects follow a similar process to Jira Software.

Go to Project settings > Workflows > Edit. Add an “Approval” status to your workflow board. Create transitions for approval and rejection outcomes. Apply conditions to limit who can trigger each transition.

JWM’s visual board makes it easy to see where issues are stacking up — including in the approval stage — so teams can quickly spot bottlenecks.

Setting Up Approval Notifications

An approval step only works if the approver actually knows about it.

In Project settings > Notifications, set up an event trigger for when an issue transitions into the approval status. Select the notification recipients — typically the users in the Approver role or field.

You can also use Jira Automation to send Slack messages or emails when an issue reaches the approval stage. Go to Project settings > Automation > Create rule. Set the trigger to Issue transitioned and the action to Send email or Send Slack message.

According to a Forrester study, teams using automated notifications for workflow approvals reduced their average approval cycle time by 34% compared to manually-tracked processes.

Using Jira Automation to Auto-Assign Approvers

Manually setting an approver for every issue gets repetitive fast. Automation handles this.

In Project settings > Automation, create a rule:

• Trigger: Issue created (or transitioned to a specific status)
• Condition: Issue type = Change Request (or whatever your use case is)
• Action: Assign issue to a specific user or rotate through a list

This ensures every issue that needs approval already has one assigned — without anyone having to remember to do it.

Jira’s own research indicates that teams using automation rules reduce repetitive manual tasks by up to 45%, freeing up project managers for higher-value oversight work.

Tracking and Auditing Approvals

Every approval action in Jira is logged in the issue’s activity feed. This gives you a built-in audit trail without any additional setup.

For broader reporting, use Jira Dashboards or export issue data to check:

• How long issues spend in the approval stage
• Which approvers are creating bottlenecks
• Rejection rates by request type or team

If you’re using Jira Service Management, the Approvals Report under Reports gives a dedicated view of approval performance across your project.

Teams that regularly audit their approval workflows are 3x more likely to identify and eliminate unnecessary review steps, according to Atlassian’s State of Teams report.

Common Mistakes That Break Approval Workflows

Skipping the condition step. Without a condition on the approval transition, anyone can click “Approved.” This defeats the entire purpose of the approval gate.

Not notifying the approver. An issue sitting in “Awaiting Approval” with no notification sent means it’ll sit there forever.

Too many approval layers. Every extra approval step adds friction. A Harvard Business Review analysis found that organizations with more than three approval layers per process see 40% higher project delay rates. Keep it to one or two approvers per stage.

Using team-managed projects. Team-managed projects in Jira have limited workflow customization. If approvals matter, use company-managed projects.

No rejection path. Always create a clear transition for rejected issues. Without it, a declined issue has nowhere to go — creating a dead end in your workflow.

Conclusion

Adding approvals to your Jira workflow isn’t complicated — it’s a configuration choice that pays off immediately. Whether you’re using Jira Service Management’s native approval feature or building a custom flow in Jira Software, the core logic is the same: add a review status, restrict who can move the issue forward, and notify the right people automatically.

The teams that get this right stop chasing sign-offs and start moving faster. They also gain a clear audit trail for every decision — which matters when projects scale, teams grow, and stakeholders start asking questions.

Set it up once. Let Jira handle the process from there.