Approvals in Jira Software without Service Management

Last updated: 2026-10-29

You have a Jira Software project and you want someone to approve an issue before it moves on: a release, a design, a purchase, a change request. Jira Service Management (JSM) has an approval step built in, but a plain Jira Software project does not have the same one. This guide walks through the realistic options, from simplest to most flexible, and when each one fits.

Disclosure: we build Tulip Approvals, one of the apps mentioned in option 4. The other options need no app at all.

First, decide what you need

Option 1: Jira's built-in approvals

Approvals in Jira Service Management projects are native: you add an approval step to the workflow and choose the approvers. For business projects, Atlassian also documents approval steps in some team-managed projects on higher plans. Features and plans change, so check Atlassian's current documentation for your project type and plan before relying on this. If your project is a standard Jira Software project, assume you will need one of the options below.

Option 2: A workflow with an "Approved" transition

You can model approval using only workflow configuration:

  1. Add statuses such as Waiting for approval, Approved and Rejected.
  2. Add transitions between them and put a condition on the "Approve" and "Reject" transitions, so only certain people can use them. Jira's built-in conditions check things like group membership, project roles and the assignee.
  3. Add a validator so a rejection requires a comment.
  4. Use Jira's notification scheme or an automation rule to tell the approvers when an issue reaches Waiting for approval.

Good for: a fixed team of approvers and a simple yes/no decision.
Limits: the approver is usually a group or role, not a person chosen per issue. Several approvers, or approval in a set order, quickly becomes awkward. There is no single place that lists "who approved what".

Option 3: Add Jira Automation

Jira Automation can fill the gaps in option 2. For example, a user-picker field called Approver can be set when the issue is created, an automation rule can notify that person when the status changes, and another rule can add a comment recording the decision.

Good for: teams that already use automation and want a per-issue approver without installing an app.
Limits: you maintain the rules yourself, restricting a transition to "the person in the Approver field" usually needs an extra app or a workaround, and multi-step approvals take many rules.

Option 4: A Marketplace app

Several apps on the Atlassian Marketplace add approvals to Jira issues, with different strengths: multi-level paths, conditions, or reporting. Compare them against your list from the first section. Tulip Approvals is one of them. It focuses on keeping the approval on the issue itself:

On a phone, an approver can simply reply with a comment that starts with "Approve", or "Reject" and the reason, and the app records the decision. Details are in the how-to guide.

You can try it free for 30 days from the Atlassian Marketplace listing, or watch the 70-second demo.

Which one should you pick?

Your situationStart with
Same approvers every time, simple yes/noOption 2: workflow transitions
Per-issue approver and you like building rulesOption 3: workflow plus automation
Several approvers, a set order, or you need an audit trailOption 4: an approval app
You already use Jira Service ManagementOption 1: its built-in approvals

Tips that apply to any option

Questions? Write to support@tulipapps.app.