Uploaded image for project: 'Atlassian Cloud'
  1. Atlassian Cloud
  2. CLOUD-10910 Sandbox environment for Cloud (see sub-tasks for specific features)
  3. CLOUD-11161

Data copied from production to sandbox does not include the Jira automation rule data

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Unresolved
    • None
    • None
    • Admin - Sandbox - Create
    • None

      When copying data from Jira production site into sandbox, the Jira automation rules are not carried over.

      Automation rules are not included in Jira's site backup and the data will need to be migrated manually using the export and import feature of Jira automation.

      Suggestion : Consider the automation rules on the copy functionality for Sandbox.

            [CLOUD-11161] Data copied from production to sandbox does not include the Jira automation rule data

            Soumyadeep Chatterjee made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 1001040 ]
            Asvini R made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 1000394 ]

            Edie Hovermale added a comment -

            f42bc381263c,

            Recently I found export / import functionality for Automations that might help you. You will need to have Site Admin privileges for both Production and Sandbox.

            Export

            1. Open your Production Jira Instance
            2. Click on the Settings cog in the upper right corner
            3. Choose 'System'
            4. Select 'Global automation'
            5. To export one automation:
              1. Find the automation you would like to export. On the far right choose the ellipses "...", select 'Export'
            6. To export all automations:
              1. Choose the  ellipses "..." at the top of the Automation screen
              2. choose "Export rules'
              3. On the next page choose Next

            Import

            1. Open your Sandbox
            2. Click on the Settings cog in the upper right corner
            3. Choose 'System'
            4. Select 'Global automation'
            5. Choose the  ellipses "..." at the top of the Automation screen
            6. Choose "Import rules'
            7. On the next page select 'Upload JSON'
            8. Select the exported rules file, choose Open
            9. Choose the checkbox next to the automation(s) you want to import.
            10. Choose Next

            Hope this helps

            Edie Hovermale added a comment - f42bc381263c , Recently I found export / import functionality for Automations that might help you. You will need to have Site Admin privileges for both Production and Sandbox. Export Open your Production Jira Instance Click on the Settings cog in the upper right corner Choose 'System' Select 'Global automation' To export one automation: Find the automation you would like to export. On the far right choose the ellipses "...", select 'Export' To export all automations: Choose the  ellipses "..." at the top of the Automation screen choose "Export rules' On the next page choose Next Import Open your Sandbox Click on the Settings cog in the upper right corner Choose 'System' Select 'Global automation' Choose the  ellipses "..." at the top of the Automation screen Choose "Import rules' On the next page select 'Upload JSON' Select the exported rules file, choose Open Choose the checkbox next to the automation(s) you want to import. Choose Next Hope this helps

            Jacques Chatenet JCT added a comment - - edited

            @Jira Product owner: 
            Please rise priority as critical:

            Considering how a new automation not enough tested can create massive havoc against all existing automation, any professionnal admin and project admin MUST test any new automation in Sandbox environment.
            Same need for testing against current Automation in Sandbox when installing plugin that will introduce their own automations like:

            • Structure
            • Jira Excel Synchroniser
              etc.  

            Jacques Chatenet JCT added a comment - - edited @Jira Product owner:  Please rise priority as critical: Considering how a new automation not enough tested can create massive havoc against all existing automation, any professionnal admin and project admin MUST test any new automation in Sandbox environment. Same need for testing against current Automation in Sandbox when installing plugin that will introduce their own automations like: Structure Jira Excel Synchroniser etc.  

            Bandarupalli Sai added a comment -

            +1 This is a very useful feature to many Atlassian customers and also this reduces the lot of manual effort for admins

            Bandarupalli Sai added a comment - +1 This is a very useful feature to many Atlassian customers and also this reduces the lot of manual effort for admins

            itipping@leedsbuildingsociety.co.uk added a comment -

            We've got over 100 different rules across or prod environment, not having these in sandbox severely undermines the value of the sandbox environment

            itipping@leedsbuildingsociety.co.uk added a comment - We've got over 100 different rules across or prod environment, not having these in sandbox severely undermines the value of the sandbox environment
            Carlos Ughini made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 922346 ]
            Carlos Ughini made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 922505 ]

            James Rickards (Spark-Nel) added a comment -

            If you implement this, please have it as an optional, or give us a choice to bring them across but have them disabled.
            It would be a nightmare if used for integrating systems are suddenly sending test content to other production systems.

            I see a big blocker on this being that Atlassian need to introduce shared environent variables that can be used as smart values for things like the URL for a ServiceNow integration which are kept separate to the main data on the site, but are present in Site backups.

            James Rickards (Spark-Nel) added a comment - If you implement this, please have it as an optional, or give us a choice to bring them across but have them disabled. It would be a nightmare if used for integrating systems are suddenly sending test content to other production systems. I see a big blocker on this being that Atlassian need to introduce shared environent variables that can be used as smart values for things like the URL for a ServiceNow integration which are kept separate to the main data on the site, but are present in Site backups.
            Gabriele Franck made changes -
            Link New: This issue is duplicated by CLOUD-11592 [ CLOUD-11592 ]

              9ee60f91d5d1 Kaleb Mccall (Inactive)
              rmacalinao Ramon M
              Votes:
              197 Vote for this issue
              Watchers:
              101 Start watching this issue

                Created:
                Updated: