Need to update the messaging for unsupported fields for Jira C2C migrations

XMLWordPrintable

    • 4
    • Jira Software

      Issue Summary

      Currently, when we perform a Jira cloud-to-cloud migration (C2C) then after the migration there are certain fields like the Location field & Development field, which are unsupported for C2C migration. As a result, we get the below message in the migration report, post-migration: 

      "The Location custom field type is not supported via migration. The configuration for this field will not be migrated and any items that reference it, such as workflow schemes and filters may no longer work.","If you require this custom field, re-create it in your cloud site and use a csv import to update the issues post migration. Learn more : https://support.atlassian.com/jira-cloud-administration/docs/import-data-from-a-csv-file/",

      UNSUPPORTED,Global entity (applied to all projects),Custom field, Development,Custom field configuration,"The Development custom field type is not supported via migration. The configuration for this field will not be migrated and any items that reference it, such as workflow schemes and filters may no longer work.","If you require this custom field, re-create it in your cloud site and use a csv import to update the issues post migration. Learn more : https://support.atlassian.com/jira-cloud-administration/docs/import-data-from-a-csv-file/"

      We need to update the above messaging and remove the below text for the Location & Development field: 

      "If you require this custom field, re-create it in your cloud site and use a csv import to update the issues post migration. Learn more : https://support.atlassian.com/jira-cloud-administration/docs/import-data-from-a-csv-file/"

      This is because Development field data & Location Field data cannot be imported to another site using the CSV Import feature. 

      Similarly, we need to revisit the messaging for all unsupported Fields, as wrong messaging can confuse the Admin and can divert them on an incorrect path to retrieve the data. 

      Steps to Reproduce

      • Perform a cloud-to-cloud migration from one cloud instance to another cloud instance as per the steps mentioned in the documentation: Copy Jira data

      Expected Results

      For example: For Location & Development field data, we should only show messaging as :

      "For Development, Jira Development integration uses issue keys to map the field. You will need to setup the integration on the destination."

      Actual Results

      Currently we get the below message: 

      "The Development custom field type is not supported via migration. The configuration for this field will not be migrated and any items that reference it, such as workflow schemes and filters may no longer work.","If you require this custom field, re-create it in your cloud site and use a csv import to update the issues post migration. Learn more : https://support.atlassian.com/jira-cloud-administration/docs/import-data-from-a-csv-file/"

      The above message diverts us to use the csv import feature to retrieve the data. However, for the Development field data, csv Import feature will not work. 

      Workaround

      NA

            Assignee:
            Unassigned
            Reporter:
            Anindyo Sen
            Votes:
            3 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: