• Products
  • Documentation
  • Resources
Products
Documentation
Resources
Atlassian Support
/
Organization administration Resources
/
Manage product changes from an Atlassian organization
/
Manage Atlassian product sandboxes

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 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 all spaces or projects.

✅ Data that can be copied

❌ Data that can't be copied

  • Jira product family data

    • Advanced roadmaps

    • Board and sprint data

    • Comments

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

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

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

    • Portal-only accounts for Jira Service Management

    • Users and groups

    • Archived projects

    • Trashed projects

  • Confluence data

    • Comments

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

    • Space configuration data (including space settings, permissions, and user-created templates)

    • Users and groups

    • Archived spaces

  • Jira product family data

    • 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)

    • Insight for Jira Service Management

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

    • Overview for Jira Work Management

    • Views and insights for Jira Product Discovery

  • Confluence data

    • Private spaces

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

    • Whiteboards

  • Third-party apps and app data

Although automation rules aren’t automatically copied into a sandbox, you can manually export and import automation rules.

Copy specific spaces or projects

The feature is available to a select group of customers through an Early Access Program (EAP).

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

  • Jira Software data

    • Users and groups - from active directories, except Jira Service Management users (only Jira Service Management agents are migrated)

    • Project types - archived projects

    • Issued data - Summary, Description, Issue type, Status, Priority, Resolution, Labels, Reporter, Assignee, Due date, Subtasks, Some custom fields (Text, Date, Number, Time, Labels, Select list (single choice), Checkbox, Radio button, 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, Issue history, Issue work log

    • Jira Software project data - Issue rank, Epics (epic link, name, color, status, Issue rank), Original Estimate, Remaining Estimate, Flagged, Components, Environment, Sprints, Versions (affects versions, fix versions)

    • Jira Software Boards - Boards linked to one project only, Boards (Name, Administrators, Filters and permissions, Share permission, Location), Advanced board settings (Column names and status mapping, Swimlanes, Time statistic/estimation, Quick filters, Card colors, Subquery)

    • Project setup - Workflow functions (Validator: required field, field changed, Condition: user in group, user in project role, field value, Post function: update issue field)

  • Confluence data

    • Users and groups

    • Space types (if selected) - Active spaces, Personal spaces, Archived spaces

    • Confluence space data - Space details (logo, Name, Key, Categories, Description), Sidebar settings, Content status settings, Space permissions, Look and feel (Themes, Space templates, Page layout (header and footer), PDF export customizations), Pages & blogs (including archived items and items in the trash)

    • Page/blog data - Title, Content (including history), Labels, Restrictions, Comments (including history), Attachments (including history), Likes, Page restrictions, Links are migrated, but some links in destination site will continue to link to source site, Page statuses, Stock Unsplash images in headers

  • Jira Software data

    • Users and groups - Jira Service Management users (only Jira Service Management agents are migrated), users and groups from inactive directories (to migrate inactive directories, make them active before migrating)

    • User profiles - User avatars (users will need to update their avatars after migrating), 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 Service Management projects, Team-managed projects, Archived projects (to migrate archived projects, restore them before migrating)

    • Apps - Apps and app data (to migrate app data, contact the respective Marketplace Partner)

    • Jira Software Boards - Boards linked to more than one project, Shared permission

    • Project setup - Some custom fields (Single and multi-version picker, URL, Select list (cascading), Select list (multiple choice), Project picker), Custom field language translations, 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 - Global permissions, General configuration (e.g., timezone, language), Dashboards, Filters on boards not migrated, Confluence links (links in destination site will continue to link to source site)

  • Confluence data

    • Users and groups - permissions settings associated with groups will be lost during import

    • User profiles - User avatars (users will need to update their avatars after data copy), Passwords (unless you've set up SSO, users will need to reset their passwords after data copy)

    • Apps - Apps and app data stored with the vendor (to copy app data, contact the respective Marketplace Partner), Team Calendars

    • Confluence space data - Analytics data,

      Space shortcuts, Related pages settings, Whiteboards, Space icon (when attachment toggle is off)

    • Page/blog data - Analytics data, Reactions, Custom uploaded images in headers, Custom page statuses, Custom emojis (page and in title), Public links (these will need to be newly generated)

    • Entities and permissions - Site level settings: Configuration (General configuration (e.g., timezone, language), Further configuration, Languages, Shortcut links, Global templates, Code macro administration), Security (Security configuration, Global permissions, Default space permissions), Look and Feel (Themes, Colour scheme, Site logo and favicon, Header and footer, Default space logo), Administration (Audit log, Application links, 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. 



Additional Help

On this pageCopy all spaces or projectsCopy specific spaces or projects
CommunityQuestions, discussions, and articles