Provide the custom field ID and name alongside the type of the custom field in the post migration report for cloud-to-cloud migrations

XMLWordPrintable

    • 9
    • Jira Software

      Problem Description

      1. Perform a cloud to cloud migration for Jira.
      2. Go to the 'Logs & Reports' section and download the post migration report. 
      3. In some cases, a message is logged containing only the type of the unsupported custom field in the post-migration logs. An example with the custom field type 'com.atlassian.jira.toolkit:message':
      ""UNSUPPORTED"",""Referenced by project””:””ABCD””,””Impacted type"":""Issue"",""Impacted name””:””ABCD-1234””,””Problem"":""Custom field value"",""Description"":""The Message Custom Field (for edit) custom field is not supported via migration. The value for this issue will not be migrated."",""Next steps"":""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/"",""ProjectId"":""12345””}”

      Suggested Solution
      Add the capability to the Jira C2C Migration Assistant Tool to provide the custom field ID and name alongside the type of the custom field in the post migration report.

            Assignee:
            Unassigned
            Reporter:
            Beatriz Pereira [Atlassian Support]
            Votes:
            2 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: