What happens when you copy data?
You can copy data from production to sandbox but you cannot copy data from one sandbox to another sandbox. Before you start copying data, learn what options are available and how production data gets copied to your sandbox.
After you copy data, we keep the details of the sandbox data copy for 14 days. These details will expire after 14 days, and you can’t view them. More about Atlassian’s data protection practices
Options to copy data
You have the following options to copy data. Additional configuration and what data types are copied depends on the option you choose. Read more about what data is copied to a sandbox.
オプション | How data gets copied |
|---|---|
すべてのスペースまたはプロジェクトをコピーする Additional configuration: Exclude attachments | All spaces or projects are copied to the sandbox. Any existing data in the sandbox gets overwritten and replaced with the new data. |
特定のスペースまたはプロジェクトをコピーする Additional configuration: Exclude attachments, Preserve group membership (only if you have the original user management experience) | Only the spaces or projects you select are copied. If the space or project you’re copying already exists in the sandbox, it will be overwritten and replaced with the new data. |
If you are copying data manually, we recommend that you don’t use Confluence site import/export or Jira CSV import as they have high failure rates for sandboxes.
データのコピーにかかった時間
Based on the size of your production data, it can take up to 14 days to copy data. To copy data faster, you can choose to exclude attachments when you copy all spaces or projects or copy data only for specific projects or spaces. We’ll notify you through email once the data is copied.
Jira sandbox data
When you copy all production data to any of the sandboxes for the Jira family of apps (Jira Cloud, Jira Service Management, or Jira Product Discovery), we’ll also copy data into the other two sandboxes if they’re already set up. More about sandboxes for the Jira family of apps
Project or space identifiers
When you copy data for specific projects or spaces, identifiers (such as custom field identifiers like customfield_10456, board IDs, content page identifiers) are not guaranteed to be the same between your production and sandbox environments.
If you want to have the same identifiers in your sandbox, use the copy all spaces or projects option. Identifiers will be consistent only at the time when sandbox is overwritten with all production data. Over time with configuration drift, identifiers may change.
Group membership data
Understand what happens to group membership data when you copy data using the options and additional configuration available.
オプション | Group membership data |
|---|---|
Copy specific spaces or projects and you choose to preserve group membership | We’ll copy only the users and groups associated with the spaces or projects you’re copying. Users get copied along with their respective groups. If a group with the same name already exists on your sandbox, we’ll merge the two groups. And if users are new to the sandbox, they will automatically acquire permissions of the existing sandbox group. Users may inherit permissions that may not be desired. For example, if you have a group named Sales team in both production and sandbox and this group has permissions to a project named Sales planning on production. When you copy Sales planning to sandbox, the group Sales team also gets copied. Because the group Sales team already exists on the sandbox, both groups get merged and users who belong to Sales team on production will inherit permissions of the group Sales team on the sandbox. |
Copy specific spaces or projects and you don’t choose to preserve group membership | We’ll copy only the users and groups associated with the spaces or projects you’re copying. Users and groups get copied separately, users don’t get added to any groups in the sandbox. |
すべてのスペースまたはプロジェクトをコピーする | Users and groups merge with the data you have in the sandbox. To ensure that your production environment and your users are not impacted, we don’t copy webhooks or OAuth tokens. We also disable third-party app links, email notifications for actions (mentions, comments, page/work item creation and updates, etc) within your Atlassian apps in sandbox environments, and integrations with Bitbucket and Slack. |
Data checks and warnings
When you copy data for specific projects or spaces, we check the following things to confirm that your sandbox is set up correctly to copy data and to notify you of any potential conflicts or unwanted settings.
What we check | その他の注意事項 |
|---|---|
Whether your sandbox contains duplicate names for projects or spaces. | All projects or spaces on your sandbox must have unique names and project or space keys after the data copy. This includes the history of any changed or old project/ space keys. If duplicate projects or spaces are found, you’ll need to delete the duplicate projects or spaces from your sandbox or remove them from your selection. |
Whether any spaces are available to the public. | We copy space permissions as they’re configured on your production. In some cases, your space permissions may allow public access, which means anyone on the internet can access your Confluence spaces and related data in the sandbox after they’ve been copied. If you don’t want to allow people to access this data in your sandbox without logging in, update the permissions on your production before the data copy. |
Whether projects have invalid or missing filters. | Before you start copying data to your Jira Cloud sandbox, we check if there are any invalid or missing board filters. If we find invalid or missing filters you’ll need to add a valid filter to your project board. In case you don't have a valid filter, create a new one and then add it to your project board. |
Whether your sandbox contains the same group names. | メンバーシップを維持することを選択した場合にのみこのチェックが行われます。コピー先に同じ名前を持つグループがあるかどうかがチェックされます。 |
この内容はお役に立ちましたか?