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

Test upcoming changes in a sandbox

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

We continuously release changes to Atlassian apps so your organization can get improvements and new features as soon as they’re available. You can preview these improvements and try out the new features in a sandbox to prepare your users for changes. Sandbox environments are separate from your production environments, where you can confidently assess the impact of a change. More about sandboxes

Switch your sandbox to the preview track

By default, sandboxes in your organization are on the continuous release track. This means changes roll out to them as soon as they become available. Determine which release track is right for your sandbox.

To change the release track:

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

  2. Select Products > Release tracks.

  3. In the table, find the sandbox that you want to change the release track for.

  4. Select Change track and then choose the Preview track.

  5. Select Next > Confirm.

Determine which release track is right for your sandbox

The rollout timeframe of changes to your production and sandbox environments depends on the release track configuration. Understand the rollout sequence and choose the configuration that suits your needs.

I want to know the rollout timeframe of changes for my sandbox

We recommend that you chose the Bundled track for your production and the Preview track for your sandbox. With this configuration, your sandbox receives the same bundle of changes as your production, a month before your production receives them. For example, if your production is scheduled to receive bundled changes on the second Tuesday of April 2025, your sandbox will receive the same bundle on the second Tuesday of March 2025.

The only exception to using this configuration is if you want your production to get changes as soon as they are available.

We don’t recommend that you use the Continuous track for your sandbox when your production environment is on the Bundled track. This is because you’ll need to keep up with the rollout timeframe of each change that you want to test in your sandbox.

I want to defer some changes and test those changes early

If your production is on the Continuous track, you may decide to defer some changes so that your users don’t receive them right away. To test these deferred changes in advance, switch your sandbox to the Preview track.

With this configuration, if you defer a certain change in your production environment, you can test that change when it is available in your sandbox.

We don’t recommend that you use the Continuous track for your sandbox when your production environment is on the Continuous track. This is because when you defer a change in your production, it automatically gets deferred for your sandbox. You’ll be unable to test that change in advance.

Still need help?

The Atlassian Community is here for you.