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

Create an API to convert user references stored in JQL to AAID during the migration

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

      We are adding capabilities to the Cloud Migrations Assistants to migrate app data automatically. This functionality requires Marketplace Partners to build automated migration paths compatible with the Cloud Migration Assistants; they can do so using the App migration platform.

      Apps that store JQL may be storing JQL containing user references that will not work correctly in cloud. These user references will need to be converted from the format used in server (username / user key) to the format used in cloud (AAID) during the migration.

            [MIG-315] Create an API to convert user references stored in JQL to AAID during the migration

            https://jira.atlassian.com/browse/MIG-1021 would also cover the particular case described in this ticket. It makes more sense to implement MIG-1021. It would be a low investment on Atlassian's side with huge benefits for all vendors who add JCMA support. 

            Dan Mihalache [Qotilabs] added a comment - https://jira.atlassian.com/browse/MIG-1021 would also cover the particular case described in this ticket. It makes more sense to implement MIG-1021 . It would be a low investment on Atlassian's side with huge benefits for all vendors who add JCMA support. 

            Thank you for voting and linking your tickets as dependent on this feature.

            During our testing, we found an unexpected use case for which our implementation doesn't fulfil this capability. Its coverage requires extra effort.

            We have decided to put this feature back to "Gathering interest" to evaluate if its value matches the effort required.

            Please express your interest in this ticket.

            Regards,

            David Almeida

            Engineering Manager, Atlassian Cloud Migrations

             

             

            David Almeida added a comment - Thank you for voting and linking your tickets as dependent on this feature. During our testing, we found an unexpected use case for which our implementation doesn't fulfil this capability. Its coverage requires extra effort. We have decided to put this feature back to "Gathering interest" to evaluate if its value matches the effort required. Please express your interest in this ticket. Regards, David Almeida Engineering Manager, Atlassian Cloud Migrations    

            Jason Wong added a comment -

            Update on availability: May 2021

            Thank you for voting and linking your tickets as dependent on this feature. The development work is currently underway and we're working to get this out ASAP so that you can implement your automated migration path.

            So that you have better visibility on timeframes, today we're providing updated guidance that this feature is currently scheduled for release in May 2021.

            Regards,

            Jason Wong

            Product Manager, Atlassian Cloud Migrations

            Jason Wong added a comment - Update on availability: May 2021 Thank you for voting and linking your tickets as dependent on this feature. The development work is currently underway and we're working to get this out ASAP so that you can implement your automated migration path. So that you have better visibility on timeframes, today we're providing updated guidance that this feature is currently scheduled for release in May 2021. Regards, Jason Wong Product Manager, Atlassian Cloud Migrations

              rbattaglin Renan Battaglin
              akassab Alex
              Votes:
              6 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated: