• Icon: Sub-task Sub-task
    • Resolution: Unresolved
    • Icon: Low Low
    • None
    • None
    • None

      Summary

      By default, when creating a sandbox, it is possible to import the data from production.

      As sandboxes are generally used to test data prior to pushing it to production, it would be helpful if an option to keep the sandbox in sync with the production existed so any changes applied to the sandbox could be delivered to production (and vice-versa) with a single button once they are evaluated.

      Suggestion

      This is a suggestion to have a sync option to allow users to keep the sandbox environment in sync with production without necessarily starting a new copy from the scratch

            [CLOUD-11209] Ability to keep sandbox synced with production data

            My main use-case is for testing custom integrations and the biggest pain point right now is that the custom fields numbering is not preserved when you create a sandbox.  Having the customfield numbers match is essential for us to test out existing integrations without having to re-write them.  The whole point is to test that the integration will work on production, and if we need to make changes between the two deployments, it isn't really a valid test.

            tim.mcdougall added a comment - My main use-case is for testing custom integrations and the biggest pain point right now is that the custom fields numbering is not preserved when you create a sandbox.  Having the customfield numbers match is essential for us to test out existing integrations without having to re-write them.  The whole point is to test that the integration will work on production, and if we need to make changes between the two deployments, it isn't really a valid test.

            Hurry up Atlassian - this is stealing otherwise productive time from teams globally (and their support partners). 

            Russell Charman added a comment - Hurry up Atlassian - this is stealing otherwise productive time from teams globally (and their support partners). 

            This would be really nice to have. Does not need to copy over all production data but maybe have the ability to update certain projects on a weekly basis rather than having to keep going back and copying all production data over.

            Matt Baillargeon added a comment - This would be really nice to have. Does not need to copy over all production data but maybe have the ability to update certain projects on a weekly basis rather than having to keep going back and copying all production data over.

            Conversely,
            I would rather protect certain projects in sandbox from being overwritten if a lot of development work has taken place in them but not yet rolled out to production.

            Our ICT team regularly re-sync sandbox but this, obviously, overwrites automations, workflows, transition conditions and all sorts.

            Perhaps, when a sync is performed a backup could be kept in another area so that developers can copy or export configurations back into sandbox.

            Rus Yates-Aylott added a comment - Conversely, I would rather protect certain projects in sandbox from being overwritten if a lot of development work has taken place in them but not yet rolled out to production. Our ICT team regularly re-sync sandbox but this, obviously, overwrites automations, workflows, transition conditions and all sorts. Perhaps, when a sync is performed a backup could be kept in another area so that developers can copy or export configurations back into sandbox.

            I know there is now add-ons that do this like Revyz CMJ for Cloud or Revyz back up and restore but this is something that should be native. Admins don't want to build in production as we been doing for years now. We need a place to build and deploy. We need SDLC around Atlassian products.

            Aaron Geister added a comment - I know there is now add-ons that do this like Revyz CMJ for Cloud or Revyz back up and restore but this is something that should be native. Admins don't want to build in production as we been doing for years now. We need a place to build and deploy. We need SDLC around Atlassian products.

            Marie added a comment -

            I would want the option to schedule a restore on a weekly basis as well.

            Marie added a comment - I would want the option to schedule a restore on a weekly basis as well.

            For us, we'd like to be able to pull/refresh configuration data (projects, workflows, roles, permission sets, etc.) back and forth, but /not/ raw data (tickets, users, etc). This is because we do not want most users to have sandbox access, and we do not want to have to manage tickets in sandbox, but we do want to be able to test configurations there, and then promote the config.

            Rabbit Stoddard added a comment - For us, we'd like to be able to pull/refresh configuration data (projects, workflows, roles, permission sets, etc.) back and forth, but /not/ raw data (tickets, users, etc). This is because we do not want most users to have sandbox access, and we do not want to have to manage tickets in sandbox, but we do want to be able to test configurations there, and then promote the config.

            Given this is low priority, I'm thinking birthday cake around 2036

            Ed McCulloch added a comment - Given this is low priority, I'm thinking birthday cake around 2036

            Anyone assigned this? Asking for a friend...

            Tommy Augustine added a comment - Anyone assigned this? Asking for a friend...

            Please make it so we can schedule a 'sandbox refresh' that will automatically pull production Jira data to our sandbox. We used to run datacenter Jira on prem and Sunday night we cleaned out the sandbox and restored it from the production data through an automated process. Having this automatic process will greatly improve our satisfaction with Cloud Jira and sandboxes.

            Matt Mangione added a comment - Please make it so we can schedule a 'sandbox refresh' that will automatically pull production Jira data to our sandbox. We used to run datacenter Jira on prem and Sunday night we cleaned out the sandbox and restored it from the production data through an automated process. Having this automatic process will greatly improve our satisfaction with Cloud Jira and sandboxes.

              Unassigned Unassigned
              gdecampos Giuliano C.
              Votes:
              161 Vote for this issue
              Watchers:
              99 Start watching this issue

                Created:
                Updated: