Open Beta: Multiple sandboxes

With multiple sandboxes, you can create more than one testing environment for a single production site so you can test different kinds of changes in parallel. For example, you can have the following sandboxes for a single Jira instance:

• App testing sandbox

• New features sandbox

• Migration sandbox

Every sandbox you create is mapped to the original production environment. You can copy data to it individually and make changes inside without affecting other sandboxes. They’re still individual entities, like before.

はじめる前に

Multiple sandboxes are now in open Beta. If you have questions regarding the Beta, for example how it affects your existing sandboxes, how you can upgrade your plan to use it, how to opt out, and so on, check our FAQs.

Open Beta: Multiple sandboxes FAQs

動作の仕組み

When you create a new sandbox, you always choose:

• Source production site so we can create a mapping.

• New name so we can create a new URL, like dev-atlassian.com.

• Product you want to create a sandbox for.

As a result, you really create a sandbox site (dev-atlassian.com) with 1 sandbox in it. This division into sandbox sites and sandboxes makes it easier for us to recreate the backbone of your production site, and organize your sandboxes.

If you’d like more sandboxes for the same production site, you can repeat the whole process and specify different URLs.

Example: Production site (with Jira) mirrored into multiple separate sandbox sites

Every Jira sandbox on the diagram above is a separate environment. Changes to one won’t affect the others.

Multiple Enterprise products

If you have multiple Enterprise products in a single production site, like Jira and Confluence, you can combine their sandboxes under sandbox sites used for the same kind of testing:

• If your production site already has a Development sandbox site, you can add more sandboxes to it.

• Product sandboxes in a sandbox site share the same URL, with a different context path.

• A sandbox site can have the same products as the production site or only some of them.

Example: Sandbox sites with a mix of sandbox products

Every sandbox on the diagram above is still a separate environment, even if they’re in the same site. If you already have some existing sandbox sites, you can add products to them from the dashboard without having to create new ones with all those separate URLs.

Many production sites

You can spread available sandboxes across different production sites, depending on how your organization is constructed. You can use any combination, as long as the total number of sandboxes in your organization is below the limit.

Example: Two production sites with a different setup of sandboxes

Sandbox limits

There’s a limit on the number of available sandboxes. You can create 10 sandboxes for every Enterprise plan across your entire organization:

• Jira Enterprise: 10 sandboxes in total

• Jira Service Management: 10 sandboxes in total

• Confluence Enterprise: 10 sandboxes in total

A single production site can also have a maximum of 10 different sandbox sites (regardless of sandboxes inside). We have this limit so you try to combine your sandboxes under common sandbox sites instead of dividing them into too many sites.

More about sandbox limits

Sandboxes and Marketplace apps

You can add Marketplace apps to each of your sandboxes for free, as long as the app has a paid subscription on the linked production site. This also applies to multiple sandboxes linked to a single production site.

サンドボックス用のアプリを管理する

Sandboxes in admin.atlassian.com

With the basics explained, let’s have a look at the new Sandbox page and its changes.

Sandbox page overview

Here’s an overview of the Sandbox page, with some sandboxes already created.

1. Create sandbox: Create an entire new sandbox environment, like development.

2. Limits: See how many sandboxes you already used across your organization.

3. Sandbox sites: Sandbox sites (URLs) and their corresponding production sites. If a production site has multiple sandbox sites, you’ll see each mapping as a separate row.

4. Sandboxes: Product sandboxes in a sandbox site. These count towards your limit.

5. Add sandbox: Add a product sandbox to an existing site.

6. Actions: View additional actions, like delete, restore, or copy production data.

Creating a new sandbox

If you’d like to create a sandbox in a new sandbox site, select Create sandbox from the dashboard. To create multiple sandboxes for a single production environment, repeat this process and select the same production site every time.

Adding sandboxes to existing sandbox site

If you already have some sandbox sites, you can add a new sandbox to it from the dashboard.

Copying data to a sandbox

You copy data to each sandbox individually without affecting other sandboxes, even if they’re in the same site. You can’t copy data between sandboxes – only from a production instance to a specific sandbox.

Deleting sandboxes

You can delete an individual sandbox or the entire sandbox site directly from the dashboard.

When deleted, sandboxes become offline for 30 days, you can restore them during that time.

Get started with multiple sandboxes

When you’re ready to get started:

1. admin.atlassian.com に移動して、組織を選択します。

2. [製品] > [サンドボックス] の順に選択します。

3. Create your first sandbox.

How to create a sandbox