Freeze Windows
Block or restrict releases during specific periods
What Are Freeze Windows?
Freeze windows prevent or restrict releases during specific time periods — holidays, code freezes, change moratoriums, or any period where deployments should be paused. When a release is planned during a freeze window, it either requires an exception approval or is completely blocked.
Types of Freeze Windows
| Type | Description | Example |
|---|---|---|
| Date Range | Specific start and end dates | Dec 20 - Jan 2 (Year End Freeze) |
| Recurring Weekly | Specific days of the week, every week | Every Saturday and Sunday |
| Recurring Monthly | Specific days of the month, every month | 1st to 3rd of every month |
| Recurring Yearly | Same dates every year | Dec 24 - Jan 1 (Holiday freeze) |
Creating a Freeze Window
Go to Freeze Windows
Navigate to Admin > Freeze Windows. Click "+ Add Freeze Window".
Name it and select the type
Give a descriptive name (e.g., "Year End Code Freeze"). Choose Date Range, Weekly, Monthly, or Yearly.
Configure the period
For date range: set start and end dates. For recurring: select the days/months. Add an optional reason.
Configure exception handling
Toggle "Allow Exception Approvals". If enabled, specify who can approve exceptions: by Jira role and/or by specific users.
Exception Approvals
When exceptions are allowed, releases during freeze periods require additional approval. Configure exception approvers in two ways:
- By Jira Role — Anyone with the selected role can approve (e.g., "Engineering Director")
- By Specific User — Named individuals who can approve exceptions
The freeze exception approval runs in parallel with the regular approval chain. Both must be satisfied for the release to proceed.
Freeze Window on Calendar
Active freeze windows are highlighted on the Planning Calendar with visual indicators. Hover over frozen dates to see the freeze window name and reason.