How to set up a code freeze in Jira
By Jake Marsh · Updated
Jira Cloud has no freeze window for software releases; the change calendar in Jira Service Management covers change requests, not versions. With Cutline, a Jira admin adds a freeze window in Jira settings > Apps > Cutline with its first and last frozen day, the spaces it covers, and whether it blocks releases, transitions or both. Releases inside the window fail their freeze gate, and any transition you've given the Cutline freeze window validator is refused while the freeze is on.
Steps
- Open Jira settings > Apps > Cutline and click Add a freeze window.
- Name it, for example "Year-end freeze" or "Launch week".
- Set the first and last frozen day. Days are counted in the time zone set on the same page.
- Choose the spaces: every space, or chosen ones.
- Choose what it blocks: releases, transitions, or both.
- Add a message people see when they're stopped, such as who to ask for an exception.
- Save. The days show yellow on the Release calendar, and the Freeze windows tab lists every window.
Freezing workflow transitions too
Blocking releases stops versions going out. To also stop work moving, for example to Done or to a Deploy status, add the validator to that transition:
- Go to Jira settings > Work items > Workflows and edit the workflow.
- Select the transition and open Validators.
- Click Add validator and pick Cutline freeze window.
- Publish the workflow.
The validator only refuses the transition while a freeze window that blocks transitions covers the work item's space. The rest of the year it lets everything through.
What people see during a freeze
| Who | What happens |
|---|---|
| Someone clicks Release in Cutline | The freeze gate fails; only people allowed to override can release, with a reason that is kept on the release |
| Someone releases on Jira's Releases page | Cutline records the failed gate, or puts the version back to unreleased if your site enforces gates |
| Someone moves a work item through a frozen transition | Jira refuses the transition |
| Anyone opening the calendar | Frozen days are yellow, and the Upcoming tab shows freezes ahead |
Planning around a freeze
A release dated inside a freeze fails its freeze gate even before the freeze starts, so the Release calendar's readiness badges flag it early. Move its date in Jira, or plan an approved override. The Upcoming releases (Cutline) dashboard widget also says "Freeze coming" when one is near.
Who can override is one setting for the site: Jira admins, space admins, or nobody. For a strict year-end freeze, choose nobody. For requirements before releasing outside a freeze, see how to set up a release approval process in Jira.
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 a freeze cover only some spaces?
Yes. Each freeze window covers every space or the spaces you choose.
Can I freeze transitions without blocking releases?
Yes. Set the window to block transitions only and add the Cutline freeze window validator to the transitions you want stopped.
Does a freeze stop people editing work items?
No. It blocks releases and the transitions you add the validator to. Other edits carry on.
Does it affect Jira Service Management change requests?
No. Cutline's freezes apply to versions and to the transitions you choose, in the spaces they cover.
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)