What data is copied to sandboxes
When you copy your production data to a sandbox, some data types aren’t copied.
Copy all spaces or project
The following table lists the product data types that can be copied to a sandbox, as well as the product data types that can’t copied when you copy all spaces or projects.
✅ Data that can be copied
❌ Data that can’t be copied
Copy all spaces or projects |
---|
❌ Third-party apps and app data |
Jira product family data |
✅ Advanced roadmaps |
✅ Board and Sprint data |
✅ Comments |
✅ Jira issues and Field content: |
✅ Media files: |
✅ Project configuration data: |
✅ Portal-only accounts for Jira Service Management |
✅ Users and groups |
✅ Archived projects |
✅ Trashed projects |
❌ Automation rules |
❌ Jira Service Management features powered by Opsgenie: |
❌ Insight for Jira Service Management |
❌ Product access settings (you’ll need to add users to groups for permissions to apply) |
❌ Overview for Jira business projects |
❌ Views and insights for Jira Product Discovery |
Confluence data |
✅ Comments |
✅ Media files: |
✅ Space configuration data: |
✅ Users and groups |
✅ Archived spaces |
❌ Private spaces |
❌ Product access settings (you’ll need to add users to groups for permissions to apply) |
❌ Whiteboards |
Although automation rules aren’t automatically copied into a sandbox, you can manually export and import automation rules.
Copy specific spaces or projects
The following table lists the product data types that can be copied to a sandbox, as well as the product data types that can’t copied when you copy specific spaces or projects.
✅ Data that can be copied
❌ Data that can’t be copied
Copy specific spaces or projects |
---|
Jira data |
✅ Users and groups: |
✅ Project types: Archived projects (Restore them before copying), Jira Service Management projects and Team-managed projects |
Issued data: ✅ Some custom fields: Text, Date, Number, Time, Labels, Select list (single choice), Checkbox, Radio button, and User picker (single, multiple) ✅ Group custom fields, Multi-line text, Environment), @mentions, Watchers and votes, Issue links (including link types), Attachments (media, files), Comments, Comments with security, Story points, Time spent, and Issue |
✅ Jira Software project data: |
Jira Software Boards: ✅ Boards: Name, Administrators, Filters and permissions, Share permission, and Location ✅ Advanced board settings: Column names and status mapping, Swimlanes, Time statistic/estimation, Quick filters, Card colors, and Subquery |
Project setup: ✅ Validator: Required field, and Field changed ✅ Condition: User in group, User in project role, and Field value ✅ Post function: Update issue field |
Users and groups: ❌ Users and groups from inactive directories (to migrate inactive directories, make them active before migrating) |
User profiles: ❌ Passwords (unless you've set up SSO, users will need to reset their passwords after migrating) ❌ Timezones (timezone information on a per-user profile will be lost) |
❌ Project types: |
❌ Jira Software Boards: |
Project setup: ❌ Workflow functions ❌ Condition: Subtask blocking ❌ Post function: Clear field value, Copy value from other field, Delegating, Update issue custom field ❌ Notification schemes (projects are added to the default schemes in cloud) ❌ Project avatars, Links to issues or entities not migrated, Automation rules, Custom issue type icons |
❌ Entities and permissions: |
Confluence data |
✅ Users and groups |
✅ Space types (if selected): |
Confluence space data: ✅ Look and feel: Themes, and Space templates ✅ Page layout: Header and footer, and PDF export customizations ✅ Pages & blogs (including archived items and items in the trash) |
✅ Page/blog data: |
❌ Users and groups: Permission settings associated with groups will be lost during import |
❌ User profiles: |
❌ Apps: |
❌ Confluence space data: |
❌ Page or blog data: |
Entities and permissions: ❌ Further configuration, Languages, Shortcut links, Global templates, and Code macro administration ❌ Security: Security configuration, Global permissions, Default space permissions ❌ Look and Feel: Themes, Colour scheme, Site logo and favicon, Header and footer, and Default space logo ❌ Administration: Audit log, Application links, and Application navigator |
Confluence users and groups: Any permissions settings (space or page) associated with groups will be lost during import unless a group with the same name already exists in the destination site. To maintain your groups' permissions settings, make sure all your groups have a corresponding group with the same name that already exists in the destination site before importing the space. An easy way to do this is to first import users and groups, then import any spaces.
Was this helpful?