Uploaded image for project: 'Atlassian Cloud'
  1. Atlassian Cloud
  2. CLOUD-10910

Sandbox environment for Cloud (see sub-tasks for specific features)

XMLWordPrintable

    • 120

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Atlassian Update – 21 May 2021

      Hi everyone,

      Thank you all for your patience. The sandbox feature is now available to all Premium and Enterprise customers. This means that you will now have the ability to:

      1. Create (an empty) sandbox
      2. Delete a sandbox
      3. Copy production data into your sandbox*

      *There are some known caveats with what we do/do not copy. Please refer to our official documentation.

      We expect that providing fully capable sandbox environments will be a multi-step journey. Please refer to the sub-tasks for the features we're working on and/or considering. We will continue to share updates on this ticket as soon as features are available. Don't hesitate to contact me directly if you have questions at mtse@atlassian.com.

      Thanks,
      Matt Tse
      Senior Product Manager, Atlassian

      What is a sandbox?

      A sandbox is an isolated environment where admins & developers safely test applications and extensions and preview new features without impacting the production environment.

      For more about sandboxes, please check out our official documentation.

        1. last updated feedback.png
          last updated feedback.png
          585 kB

          Form Name
          1.
          		 Ability to push data from sandbox to production Sub-task In Progress Adithya Ramesh
          2.
          		 Ability to copy data from production to sandbox Sub-task Closed Matt Tse
          3.
          		 Ability to create & delete a sandbox Sub-task Closed Unassigned
          4.
          		 Improved visibility of errors/logging when attempting to Copy Data to Sandbox. Sub-task Closed Unassigned
          5.
          		 Ability to see sandbox events in admin audit log Sub-task Closed Maggie Pedersen
          6.
          		 Ability to reset a sandbox Sub-task Open Shruti Narayan
          7.
          		 Ability to do a partial copy of Confluence data from production to sandbox Sub-task Closed Shayka Zarrin
          8.
          		 Ability to do a partial copy of Jira Sub-task Closed Shayka Zarrin
          9.
          		 Multiple Sandboxes Sub-task Closed Swarna Mehta
          10.
          		 Ability to keep sandbox synced with production data Sub-task Open Unassigned
          11.
          		 Allow scheduled basis copies of Data from Production into Sandbox Sub-task Open Shruti Narayan
          12.
          		 Ability to enable Global Mail Settings - Email puller on Sandbox Sub-task Open jaikibpitt
          13.
          		 Ability to copy Assets Data to Sandbox Sub-task Open Rishikesh .
          14.
          		 Data copied from production to sandbox does not include the Jira automation rule data Sub-task Open Kaleb Mccall (Inactive)
          15.
          		 Ability to copy marketplace apps' data from production to sandbox Sub-task Open Shruti Narayan
          16.
          		 Ability to copy the permissions only from the Sandbox creator in the import from production to sandbox Sub-task Open Unassigned
          17.
          		 Improve error handling when Copy to Sandbox fails if uncompressed XML file size is over 20GB Sub-task Closed Unassigned
          18.
          		 Logging details for Sandbox copy Sub-task Open Matt Roche
          19.
          		 Support users managed by an external directory in Jira during Sandbox Data Copy Sub-task Closed Unassigned
          20.
          		 Ability to disable/control Sandbox Notifications Sub-task Open Unassigned
          21.
          		 Ability to copy projects without its issues Sub-task Open Unassigned
          22.
          		 Convert Sandbox into Production and Vice-Versa Sub-task Open Unassigned
          23.
          		 Ability to copy filters when only copying selective project to Sandbox Sub-task Open Unassigned
          24.
          		 Data copied from production to sandbox does not include certain project settings Sub-task Open Rishikesh .

            [CLOUD-10910] Sandbox environment for Cloud (see sub-tasks for specific features)

            Edie Hovermale added a comment -

            Instead of making us import our Automations, just write over them like you do the rest of the project. Or better yet, give us an option to overwrite the automations, or not.

            Edie Hovermale added a comment - Instead of making us import our Automations, just write over them like you do the rest of the project. Or better yet, give us an option to overwrite the automations, or not.

            ATP JIRA Administration 2 - Brenda Thoe added a comment - - edited

            7/29/24 - adding a comment regarding the  new sandbox refresh process for Specific Projects.  The validation step where it detects the existing project in Sandbox and requires it to be deleted before the process can begin.  This additional step adds a significant amount of time to the refresh process whereas prior, copying production data to sandbox would begin immediately and just overwrite the project in sandbox.  Please consider an alternative to deleting the project and allowing the option to overwrite.

            Another issue we ran into with the new copy production data to sandbox is the automation rules that existed in sandbox are not removed so when we finished our copy of production project to sandbox and tried to import the automation rules, it wanted to add them as a copy of the existing rule.  The only work around would be to first delete the automation rules in sandbox that are associated to the project we will be copying and then re-import the rules so we have the most up to date prod version of the rule.  This is very time consuming as we are not able to delete automation rules in bulk, only one by one as well as the newly copied project does not have the same ID associated to it so as we select which automation rules to import, we also have to associate them to the project.  We have 111 automation rules so this is also time consuming.

            Due to the issues encountered with copying a specific project vs. all projects, we will continue to copy all projects to avoid.

            ATP JIRA Administration 2 - Brenda Thoe added a comment - - edited 7/29/24 - adding a comment regarding the  new sandbox refresh process for Specific Projects.  The validation step where it detects the existing project in Sandbox and requires it to be deleted before the process can begin.  This additional step adds a significant amount of time to the refresh process whereas prior, copying production data to sandbox would begin immediately and just overwrite the project in sandbox.  Please consider an alternative to deleting the project and allowing the option to overwrite. Another issue we ran into with the new copy production data to sandbox is the automation rules that existed in sandbox are not removed so when we finished our copy of production project to sandbox and tried to import the automation rules, it wanted to add them as a copy of the existing rule.  The only work around would be to first delete the automation rules in sandbox that are associated to the project we will be copying and then re-import the rules so we have the most up to date prod version of the rule.  This is very time consuming as we are not able to delete automation rules in bulk, only one by one as well as the newly copied project does not have the same ID associated to it so as we select which automation rules to import, we also have to associate them to the project.  We have 111 automation rules so this is also time consuming. Due to the issues encountered with copying a specific project vs. all projects, we will continue to copy all projects to avoid.

            Aaron Morris added a comment -

            I agree completely with a feature request to deploy configurations from the Sandbox to Production. I was surprised to see that it was missing when I first used my Jira sandbox.

            For anyone interested, I eventually solved that problem in Jira using a tool called Salto (https://www.salto.io/jira).  However, I would still love to see this natively supported, especially since Salto doesn't support Confluence.  (I'm not affiliated with Salto; I'm just a happy customer.)

            Aaron Morris added a comment - I agree completely with a feature request to deploy configurations from the Sandbox to Production. I was surprised to see that it was missing when I first used my Jira sandbox. For anyone interested, I eventually solved that problem in Jira using a tool called Salto ( https://www.salto.io/jira).   However, I would still love to see this natively supported, especially since Salto doesn't support Confluence.  (I'm not affiliated with Salto; I'm just a happy customer.)

            Edie Hovermale added a comment -

            I don't see a feature request to push configuration from the Sandbox to Production. This is more important to me than data.

            Edie Hovermale added a comment - I don't see a feature request to push configuration from the Sandbox to Production. This is more important to me than data.

            Lucas Gagliano added a comment -

            https://community.atlassian.com/t5/Jira-Software-questions/Mandatory-field-quot-Sprint-quot-in-Bulk-migration/qaq-p/2684387

            Lucas Gagliano added a comment - https://community.atlassian.com/t5/Jira-Software-questions/Mandatory-field-quot-Sprint-quot-in-Bulk-migration/qaq-p/2684387

            Susan Snell added a comment -

            Good morning.  Just wondering if the ability to select PROD data to move to a Jira Cloud sandbox environment has been implemented yet.  I understand that, per your Sandbox creation documentation, only members of an EAP were previously enabled to select specific PROD data however wondering if this has now become standard functionality for a Jira Cloud Sandbox.  

            Thanks!

            Susan Snell added a comment - Good morning.  Just wondering if the ability to select PROD data to move to a Jira Cloud sandbox environment has been implemented yet.  I understand that, per your Sandbox creation documentation, only members of an EAP were previously enabled to select specific PROD data however wondering if this has now become standard functionality for a Jira Cloud Sandbox.   Thanks!

            Oluwanifemi Fadahunsi added a comment -

            Hey Team, 

            Quick question, I was wondering if there is a reason why creating a Team in Sandbox appears in Prod. I am trying to test out the functionality for Teams before getting my org to implement it and it is inconvenient to have the Teams show up in Prod without proper transition. 

            Oluwanifemi Fadahunsi added a comment - Hey Team,  Quick question, I was wondering if there is a reason why creating a Team in Sandbox appears in Prod. I am trying to test out the functionality for Teams before getting my org to implement it and it is inconvenient to have the Teams show up in Prod without proper transition. 

            Tapiwa Samkange added a comment -

            The sandbox is a great feature. Even in the short time that I have been using the Confluence and Jira sandboxes the usefulness of having an environment that is completely separate from production where testing can be carried out, is clear. They are good for trying out apps too. Thanks Atlassian team!

             

             

            Tapiwa Samkange added a comment - The sandbox is a great feature. Even in the short time that I have been using the Confluence and Jira sandboxes the usefulness of having an environment that is completely separate from production where testing can be carried out, is clear. They are good for trying out apps too. Thanks Atlassian team!    

            Aaron Morris added a comment -

            Hi Max,

            Thank you for the reply.  Unfortunately, I do not see that option.  I've already asked Atlassian Support, and they told me the functionality was not supported.  That's what prompted me to submit the feature request. 

            Regardless, I appreciate the advice, and I'll submit a new support ticket. Thank you!

            Aaron Morris added a comment - Hi Max, Thank you for the reply.  Unfortunately, I do not see that option.  I've already asked Atlassian Support, and they told me the functionality was not supported.  That's what prompted me to submit the feature request.  Regardless, I appreciate the advice, and I'll submit a new support ticket. Thank you!

            Max Zhang added a comment -

            Hey 0b00da0e7817,

            We allow the capability to create a Jira Service Management Free sandbox provided you have Jira Service Management free AND any other Jira premium product in your production environment.

            To create a sandbox please follow these instructions: https://support.atlassian.com/organization-administration/docs/manage-product-sandboxes/#Create-a-sandbox 

            You should see an option for Jira Service Management on your site. If not please raise a support request and we can have a look at it!

            Thanks,

            Max

            Max Zhang added a comment - Hey 0b00da0e7817 , We allow the capability to create a Jira Service Management Free sandbox provided you have Jira Service Management free AND any other Jira premium product in your production environment. To create a sandbox please follow these instructions: https://support.atlassian.com/organization-administration/docs/manage-product-sandboxes/#Create-a-sandbox   You should see an option for Jira Service Management on your site. If not please raise a support request and we can have a look at it! Thanks, Max

              face54eadb13 Shruti Narayan
              mchaudhry Megha
              Votes:
              190 Vote for this issue
              Watchers:
              202 Start watching this issue

                Created:
                Updated: