Uploaded image for project: 'Migration Platform'
  1. Migration Platform
  2. MIG-478

Support migration for Canned Responses from Server/DC to Cloud

XMLWordPrintable

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

      Problem Definition

      The new Atlassian App Migration Platform (currently under development) will enable all Atlassian Marketplace Partners apps to build automated migration paths for their apps.

      Suggested Solution

      When a customer migrates projects from Jira Server / Data Center to Jira Cloud using the Jira Cloud Migration Assistant, the app migration platform will coordinate with Canned Responses to automatically move CR templates to be used in your Cloud instance.

      Current Status

      Currently, the Cloud Migration Assistant can be used to automatically migrate CR templates. Please refer to our public documentation to learn about the differences between Server/Cloud versions: https://confluence.spartez-software.com/display/CT/Canned+Responses+-+Server+to+Cloud+migration 

       

            [MIG-478] Support migration for Canned Responses from Server/DC to Cloud

            Divyanshi made changes -
            Remote Link Original: This issue links to "APP-364 (Ecosystem Jira)" [ 560356 ] New: This issue links to "APP-364 (Ecosystem JIRA)" [ 560356 ]
            Divyanshi made changes -
            Remote Link Original: This issue links to "APP-400 (Ecosystem Jira)" [ 576280 ] New: This issue links to "APP-400 (Ecosystem JIRA)" [ 576280 ]
            Judit (Inactive) made changes -
            Link New: This issue is related to MIG-1469 [ MIG-1469 ]

            Alex added a comment -

            Hi 8b935a134d60 -

            We are planning to release the App migrations features for JCMA to beta this week. Please follow this ticket for more details. Note: if you have documentation referring to the JCMA App Migrations EAP, please update as soon as possible.

            Thanks,

            Alex Kassab
            Product Manager - Cloud Migrations

            Alex added a comment - Hi 8b935a134d60 - We are planning to release the App migrations features for JCMA to beta this week. Please follow this ticket for more details. Note: if you have documentation referring to the JCMA App Migrations EAP, please update as soon as possible. Thanks, Alex Kassab Product Manager - Cloud Migrations
            Alex made changes -
            Link New: This issue depends on MIG-261 [ MIG-261 ]
            Kate Caldecott (Inactive) made changes -
            Remote Link New: This issue links to "APP-400 (Ecosystem Jira)" [ 576280 ]
            Alex made changes -
            Remote Link New: This issue links to "APP-364 (Ecosystem Jira)" [ 560356 ]
            Piotr Buczek {Appfire} made changes -
            Resolution New: Done [ 17 ]
            Status Original: Waiting for Release [ 12075 ] New: Closed [ 6 ]

            Kate Caldecott (Inactive) added a comment -

            Hi there and to note:

            App migrations EAP for the Jira Cloud Migration Assistant has arrived! (see the release schedule).

            Before we can include your app in the EAP, we need a final confirmation from you that your automated migration path has been tested with the Jira Cloud Migration Assistant and is ready for release to EAP customers. As part of this process, can you please ensure that your public migration documentation is up to date and customer contact points are in place.

            The way we will track your readiness is by looking at your public MIG ticket on https://jira.atlassian.com/issues/?filter=103236 and seeing that its status has been set to Closed with Resolution = Done, and you’ve updated the Marketplace API’s to show that your app migration path is now compatible with the Cloud Migration Assistants.

            If you are not quite ready, it would be best advised if you could provide an update via a comment on your ticket for customers to understand your plans. We’ve prepared a checklist for you with steps to take as you prepare for release.

            Once you push your ticket to Closed with Resolution = Done and update the Marketplace API as per the link above, we’ll then automatically know to start offering your app migration path to customers who have signed up during EAP.

            Kate Caldecott (Inactive) added a comment - Hi there and to note: App migrations EAP for the Jira Cloud Migration Assistant has arrived! (see the release schedule ). Before we can include your app in the EAP, we need a final confirmation from you that your automated migration path has been tested with the Jira Cloud Migration Assistant and is ready for release to EAP customers. As part of this process, can you please ensure that your public migration documentation is up to date and customer contact points are in place. The way we will track your readiness is by looking at your public MIG ticket on https://jira.atlassian.com/issues/?filter=103236 and seeing that its status has been set to Closed with Resolution = Done, and you’ve updated the Marketplace API’s to show that your app migration path is now compatible with the Cloud Migration Assistants. If you are not quite ready, it would be best advised if you could provide an update via a comment on your ticket for customers to understand your plans. We’ve prepared a checklist for you with steps to take as you prepare for release. Once you push your ticket to Closed with Resolution = Done and update the Marketplace API as per the link above, we’ll then automatically know to start offering your app migration path to customers who have signed up during EAP.
            JoJo (Inactive) made changes -
            Component/s New: Jira - Migration Assistant [ 60091 ]

              8b935a134d60 Piotr Buczek {Appfire}
              8b935a134d60 Piotr Buczek {Appfire}
              Votes:
              1 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: