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

Subtask shows unsupported messages for sprint field in post migration report when migrating to cloud

    • 47
    • Severity 3 - Minor

      Issue Summary

      Subtask show unsupported messages for sprint field in post migration report after migrating to cloud. It makes customer confusing.

      Unsupported ABC5OPE Issue ABC5OPE-38 Custom field value The "Sprint" custom field is not supported via migration
      

      Steps to Reproduce

      • Migrate tickets linking with a Sprint, and the ticket has some subtask.

      Expected Results

      No error report since sprint it supported by cloud migration, and sprint field is actually set for those ticket after migration.

      Actual Results

      Below message is written into Requires attention_Post-migration report for each subtask.

      Unsupported	ABC5OPE	Issue	ABC5OPE-38	Custom field value	The "Sprint" custom field is not supported via migration. The value for this issue will not be migrated.	If you require this field value, use a csv import to update the issues post migration. See the 'Adding additional entities with CSV' section in this document: https://confluence.atlassian.com/cloud/what-gets-migrated-with-the-jira-cloud-migration-assistant-993925216.html
      

      Workaround

      Ignore the message in post report if the sprint of ticket is set in cloud side.

            [MIG-541] Subtask shows unsupported messages for sprint field in post migration report when migrating to cloud

            T H added a comment -

            It is a pity that this issue is only in "Long Term Backlog", because it has caused several hours of work in our case:

            The error message is linked with the knowledge base article https://confluence.atlassian.com/cloud/what-gets-migrated-with-the-jira-cloud-migration-assistant-993925216.html

            • It states, that Sprint is migrated
            • but it also contains instructions how to import missing fields with csv import

            While showing the sprint field on premise, in cloud only "None (+2)" is shown (not sure, whether the (+2) is new). So I tried to import the sprint field with csv. This is not really useful, because the id's are different in cloud and you have to make a mapping.

            So it would be nice to get this issue fixed quite fast for other customers. At least you should document the wrong error messages in the knowledbase article linked above.

            T H added a comment - It is a pity that this issue is only in "Long Term Backlog", because it has caused several hours of work in our case: The error message is linked with the knowledge base article https://confluence.atlassian.com/cloud/what-gets-migrated-with-the-jira-cloud-migration-assistant-993925216.html It states, that Sprint is migrated but it also contains instructions how to import missing fields with csv import While showing the sprint field on premise, in cloud only "None (+2)" is shown (not sure, whether the (+2) is new). So I tried to import the sprint field with csv. This is not really useful, because the id's are different in cloud and you have to make a mapping. So it would be nice to get this issue fixed quite fast for other customers. At least you should document the wrong error messages in the knowledbase article linked above.

            I am facing the same problem. I am getting this error message in my 'Pre migration' report.

            Is there any resolution on this? 

            Prasad Kawadkar added a comment - I am facing the same problem. I am getting this error message in my 'Pre migration' report. Is there any resolution on this? 

              14ede9477001 Radhika Patodiya (Inactive)
              rli@atlassian.com Rick Li
              Affected customers:
              16 This affects my team
              Watchers:
              27 Start watching this issue

                Created:
                Updated:
                Resolved: