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

Defer the rollout of a change

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

If you have Atlassian apps on the continuous track and your organization needs more time to prepare for certain changes that Atlassian is rolling out, you can defer their rollout.

When you defer a change, it won’t roll out to any of your apps with an Enterprise plan for at least 30 days, including sandboxes on the continuous track.

Allow admins to defer changes

Before you can defer the rollout of a change, you need to allow all organization admins to defer changes. When you allow admins to defer changes, we stop experiments from rolling out to your organization. This won’t impact your participation in early access programs, betas, or general availability releases.

To allow admins to defer changes:

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

  2. Select Apps > App updates.

  3. From the section message at the top of the page, select Allow admins to defer changes.

Defer a change

You have 10 days to defer the rollout of a change after it’s announced in App updates.

To defer a change:

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

  2. Select Apps > App updates.

  3. Select the Defer rollout filter.

  4. Select Can defer to check if the change can be deferred.

  5. Select the release note for the change you want to defer.

  6. Select Defer rollout.

Still need help?

The Atlassian Community is here for you.