We’re renaming ‘products’ to ‘apps’

Atlassian 'products’ are now ‘apps’. You may see both terms used across our documentation as we roll out this terminology change. Here’s why we’re making this change

Block visible changes for a period of time

Who can do this?
Role: Organization admin
Atlassian Cloud: Enterprise plan for Jira, Jira Service Management, or Confluence
Atlassian Government Cloud: Not available

This feature is in beta for eligible organizations.

During important business periods such as tax seasons or major holidays, you may want to temporarily stop receiving changes to your Atlassian apps. Protect your team’s productivity during these periods by scheduling a freeze window, up to 60 days in advance.

Some changes will still continue to roll out as soon as they are available. Refer to the following table to know the types of changes that won’t roll out to your Atlassian apps during the freeze window.

Change type

Rolled out during a freeze window?

Visible changes. For example, a new setting, moving a button

No

Change you’ve deferred for apps on the continuous track

No

Bundled changes for apps on the bundled track

No

Bug fixes

Yes

Security and performance updates

Yes

Large significant changes that roll out over a longer period of time. For example, the removal of an Atlassian app or feature, or the rollout of new navigation or Confluence Whiteboard

Yes

All changes to sandboxes

Yes, changes will roll out to sandboxes based on their release track configuration

Create a freeze window

You can create a freeze window up to 60 days in advance but not within 48 hours of the start time.

Here’s some other things to keep in mind:

  • Freeze windows start at 9:00 a.m. PST and end at 5:00 p.m PST.

  • We recommend you select all apps that share a site URL in the same freeze window so that changes that impact multiple apps roll out at the same time.

To create a freeze window:

  1. Go to Atlassian Administration. Select your organization if you have more than one.

  2. Select Apps > Freeze windows.

  3. Select Create freeze window.

    1. Select the timeframe of the freeze window.

    2. Select the apps for which you’d like to postpone changes.
      When you select a Jira app, we’ll include all the other Jira apps on the same site in the same freeze window.

    3. Review and confirm the revised rollout schedule.

Postponed changes will start rolling out as soon as the freeze window ends.

Remove a freeze window

You can remove a freeze window anytime before it starts.

To remove a freeze window:

  1. Go to Atlassian Administration. Select your organization if you have more than one.

  2. Select Apps > Freeze windows.

  3. From the Actions menu, select Remove window against the freeze window you’d like to remove.

 

Still need help?

The Atlassian Community is here for you.