How to set up a release approval process in Jira
By Jake Marsh · Updated
Jira Cloud has no approvals or checklist for releasing a version; anyone with permission to manage versions can click Release. With Cutline, a space admin opens Space settings > Release gates, adds approvers and how many must approve, a checklist and any JQL checks, and saves. From then on, Release in Cutline checks every gate first, and a release made on Jira's own Releases page is checked too.
What a release gate can require
| Gate | Passes when |
|---|---|
| All work done | Every work item in the release is in a Done status category (automatic) |
| Release date | The release has a date (automatic) |
| Outside a freeze | Neither today nor the release date is in a freeze window that blocks releases (automatic) |
| JQL check | The query finds nothing, for example no open Highest priority bugs |
| Checklist | Every item is ticked; Cutline keeps who ticked it and when |
| Approvals | Enough approvers have approved, and nobody has an open rejection |
Steps
- Open Space settings > Release gates in the space. You need to be a space admin.
- Add JQL checks. Write only the condition, such as
priority = Highest AND statusCategory != Done; Cutline adds the release for you. Saving refuses a query Jira can't run, and a mistyped field fails the gate rather than passing it. - Write the checklist, one item per line, for example "QA sign-off", "Rollback plan written" and "Release notes reviewed".
- Pick approvers and how many must approve. Zero means all of them.
- Choose whether an approval stops counting when work items are added, so scope added after a sign-off needs a fresh one.
- Limit to some releases if you need to with a name pattern such as
2026.*, Release *. Leave it empty to gate every release in the space. - Save. Nothing is gated until you do.
How a release goes through
- Approvers find it under Waiting for my approval in Apps > Release calendar, open it and approve, or reject with a comment. A rejection blocks the release until it is withdrawn.
- The team ticks checklist items on the release's Gates tab. Admins can add an extra item to one release only.
- Someone clicks Release. Cutline checks the gates again and releases as that person.
- If a gate fails, only the people your Jira admin allowed (Jira admins, space admins or nobody) can choose Release past failing gates, and they must give a reason. The reason and the failing gates are kept on the release.
When someone releases outside Cutline
A version released on Jira's Releases page, by Automation or by another app is checked against the gates as they were just before. A Jira admin decides what happens when gates failed: Record it in the activity log and on the release, or Put the release back to unreleased.
Sample setups
- Small team: JQL check for open bugs at Highest priority, a two-line checklist, no approvers.
- Regulated product: QA and security as approvers with all required, approvals going stale when scope grows, overrides turned off.
- Mobile releases: a checklist with "Store screenshots updated" and "Phased rollout set", gated only for releases named
iOS *andAndroid *.
Cutline starts with Atlassian's 30-day free trial; prices are on the Cutline page.
What it costs
Cutline is From $5 a month for up to 10 users. Every plan and the install link are on the Cutline page.
Cutline: Release Calendar, Gates and Freeze Windows
Every Jira release from every space on one calendar, gates and approvals checked before you ship, and freeze windows that hold. From $5 a month for up to 10 users.
Questions
Can approvers be a group?
No. Approvers are individual people you pick on the space's Release gates page, with a count of how many of them must approve.
Is a rejection permanent?
No. The approver can withdraw it from the release's Approvals tab, and the release can go ahead once the gates pass.
Does Cutline replace Jira's release permission?
No. Releasing still runs as you, so Jira checks your right to manage versions first. Gates are an extra check on top.
Can I see who approved and when?
Yes. Each approver's decision is on the release, and the History tab keeps the activity on it.
More Cutline guides
More Jira guides
- How to find duplicate issues in Jira (Mergewell)
- How to set up a release notes template in Jira (Changeleaf)
- How to set a reminder on a Jira issue (Remindwell)
- How to book shared test environments in Jira (Berth)