robotsnoindex
descriptionTest changes to your Jira or Confluence products with sandbox environments.


This feature is available for Jira Software, Jira Service Management, and Confluence with Premium and Enterprise plans. Learn more about plans

A sandbox is an isolated environment where you can test and experiment before making changes to production.

Your sandbox URL is created based on your production site URL. For example, if your production site URL is acme.atlassian.net, your sandbox site URL could be acme-sandbox-123.atlassian.netContact us to change your sandbox URL name after creation.

Because your sandbox is not a production environment, your sandbox will not be covered by the SLAs that cover products. We don’t guarantee sandbox performance or data retention if your sandbox is destroyed. For these reasons, we recommend not using a sandbox as the sole location of your data.

Sandboxes have the same user limits as their linked production environments.

Create a sandbox

You can create a sandbox if your production Jira Software, Jira Service Management, or Confluence are on Premium or Enterprise plans. To create a sandbox, you must have organization admin permissions. Once created, all organization admins will have access to your sandbox. You can give site and product admins access to sandboxes the same way you do for products. Learn more about groups and product access

To create a sandbox:

  1. Select the name of your organization at admin.atlassian.com to access your organization Administration overview.

  2. Go to Products > Sandbox.

  3. Select Create sandbox.

  4. Choose a product.

  5. Select Create.

We’ll notify you through your Sandbox page when your sandbox is ready. If you refresh the page while we’re creating your sandbox, your sandbox will continue creating in the background.

Access your sandbox from your products table on the overview page or from the Sandbox page.

Currently, you can only create one sandbox for each linked product. For example, if you have a Jira Software production environment, you can only create one Jira Software sandbox.


Make changes to a sandbox

Make changes to your sandbox the same way you would to your production environment.

The billing and technical contacts for a sandbox are automatically set to the admin creating the sandbox, so it may not be the same billing and technical contacts for the product. Users can’t access Manage subscriptions from a sandbox.

Copy data to a sandbox

The data copy process will fail if:

To copy data from your production environment to its sandbox:

  1. Select the name of your organization at admin.atlassian.com to access your organization Administration overview.

  2. Go to Products > Sandbox.

  3. Under Actions in the product table, select Copy production data.

Currently, not all data types are able to be copied from production into sandboxes.

(tick) Types of data copied into a sandbox

(error) Types of data not copied into a sandbox

  • Jira product data

    • Board and sprint data

    • Comments

    • Jira issues and field content (including system and custom fields)

    • Project configuration data (including workflows, global permissions, schemes, screens, custom field configuration, issue types, and board configuration)

    • Users and groups

  • Confluence data

    • Comments

    • Product content (including media attachments, avatars, and logos)

    • Project configuration data (including global permissions, workflows, screens, schemes)

    • Users and groups

  • Jira product data

    • Media files, (including attachments, avatars, and logos)

    • Automation rules

    • Jira Service Management features powered by Opsgenie, (including all content accessed through the Opsgenie URL, as well as alerts and on-call schedules)

    • Product access settings (you’ll need to add users to groups for permissions to apply)

  • Confluence data

    • Private spaces

    • Product permission data (you’ll need to add users to groups for permissions to apply)

  • Third-party apps and app data

To ensure that your production environment and your users are not impacted, we don’t copy webhooks or OAuth tokens. We also disable app links, external email notifications, and integrations with Bitbucket and Slack.

It could take up to 24 hours to copy data from production into your sandbox. The larger size of the data being copied over, the longer it will take. We'll send you an email when it's complete.

If you have Jira Software and Jira Service Management sandboxes linked through the same URL, data will copy for both Jira sandboxes (excluding features powered by Opsgenie) because they are built on the Jira platform. This could result in incident links not displaying like they would in production.

If you create a new Jira sandbox, and you already have a Jira sandbox linked through the same URL, your new sandbox will create with your production data.

We're working on a more streamlined data copy for sandboxes, and we’d appreciate any feedback on what is important to you with data copy to sandboxes. Leave feedback at sandbox environment for cloud

If you are doing a manual data copy, we don’t recommend using Confluence site import/export or Jira Software CSV import as they have high failure rates for sandboxes.

Add Marketplace and Atlassian apps to a sandbox

You can install apps from the Atlassian Marketplace or through the Manage apps screen from within your Jira or Confluence administration section of your sandbox. All apps are available on a free 30-day trial.

We’ll send you email notifications about your trial period ending. After the 30-day trial, you’ll need to add your payment details to purchase a subscription to keep using the app in your sandbox. Subscriptions for apps in your sandbox are available monthly, and the price for apps is calculated on the number of users with access to your sandbox, not your production environment. Currently, we don’t support annual subscriptions for apps in a sandbox.

All apps and app subscriptions are deleted when your sandbox is deleted. If your production environment is downgraded to a Standard or Free plan, your sandbox will be deleted.


For more details on apps, see Marketplace apps, Managing Confluence apps, and Managing Jira apps.

Delete a sandbox

This will erase all data, configuration, apps, and app licenses. It can’t be undone, but you can create new sandboxes at any time. Deleing your sandbox will not delete your product.

To delete a sandbox:

  1. Select the name of your organization at admin.atlassian.com to access your organization Administration overview.

  2. Go to Products > Sandbox.

  3. Under Actions in the product table, select Delete sandbox.

After you choose to delete your sandbox, we’ll suspend it and keep it for 24 hours in case you need to cancel the deletion. When your sandbox is suspended your users won’t be able to access it.

Your sandbox lifecycle is linked to your product lifecycle, so if your product is destroyed or is no longer on a Premium plan, your sandbox will be destroyed. Sandbox data and configuration can’t be restored after it is deleted.

The Jira Cloud product family is built on top of the Jira platform, for this reason when you delete any Jira sandbox, all Jira sandboxes associated with your site will be deleted.

Cancel a sandbox deletion

You can only cancel a sandbox deletion within 24 hours of choosing to delete it. All data, configuration, apps, and app licenses will remain in your sandbox if you cancel the deletion within 24 hours.

To cancel a sandbox deletion:

  1. Select the name of your organization at admin.atlassian.com to access your organization Administration overview.

  2. Go to Products > Sandbox.

Under Actions in the product table, select Cancel delete.

Manage Jira Cloud sandboxes

The Jira family of products are built on the same platform. This means that Jira Software, Jira Service Management, and Jira Work Management share a common Jira framework. As a result, changes you make will affect all Jira products with the same URL. For example, if you delete your Jira Service Management sandbox from acme-sandbox-123.atlassian.net, you’ll also delete your Jira Software sandbox from acme-sandbox-123.atlassian.net.

Jira Service Management sandboxes can be accessed through your Opsgenie URL and your Jira Service Management URL.

There are different sandbox creation options when you have different Jira product plans.

Production

Sandbox options

Jira Software with a Premium or Enterprise plan

Create a Jira Software Premium or Enterprise sandbox and you’ll get a Jira Service Management sandbox with Free plan functionality

Jira Service Management with a Premium or Enterprise plan

Create a Jira Service Management Premium or Enterprise sandbox and you’ll get a Jira Software sandbox with Free plan functionality

Jira Software and Jira Service Management, both with Premium or Enterprise plans

Create a Jira Software Premium or Enterprise sandbox or a Jira Service Management Premium or Enterprise sandbox at any time