JCMA doesn't migrate assets-like custom fields

XMLWordPrintable

      Issue Summary

      Assets-related custom fields are not migrated using JCMA

      Steps to Reproduce

      1. Create a migration plan
      2. Select a project that contains asset-related custom fields
      3. Run the migration
      4. Verify that the assets-related custom fields are not present in the target instance
      5. Review the migration reports for messages related to unsupported custom fields

      The test was performed using JCMA 1.12.49

      Expected Results

      Asset-related custom fields should be migrated along with the object schemas.

      Actual Results

      Asset-related custom fields are not migrated, and messages indicating unsupported custom fields are found in the migration reports.

      Unsupported,AST,Custom field,"""AssetRO"" [customfield_10424]",Custom field configuration,"The ""Assets readonly object"" 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. 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"
Unsupported,AST,Custom field,"""Assets_Multi"" [customfield_10425]",Custom field configuration,"The ""Assets referenced object (multiple)"" 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. 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"
Unsupported,AST,Custom field,"""LegacyAssets"" [customfield_10421]",Custom field configuration,"The ""Assets object (multiple) (legacy)"" 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. 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"
Unsupported,AST,Custom field,"""LegacyAssets_Single"" [customfield_10422]",Custom field configuration,"The ""Assets object (single) (legacy)"" 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. 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

      Migrate the Assets-related custom fields manually after the migration using CSV import as suggested in the migration report messages. Re-create the necessary custom fields in the target instance before importing the data.

      Adding additional entities using CSV import

      You can manually add missing fields using the CSV import feature after migration. Some of the fields that aren’t migrated include:

      • Any custom fields from apps

      To add missing fields using CSV import:

      1. Create the missing fields in Jira Cloud:
        1. Create any custom fields that weren’t migrated.
        2. Assign the custom fields to the relevant screens (using data from the Jira Server logs, look for the string unsupported custom field).
      2. Add data for missing fields with CSV export-import:
        1. Export data for all the fields and issues from Server. Create a search and export as CSV
        2. Edit the CSV (in Excel, for example).
          1. Leave only issue key, issue summary and all the missing fields that you want to top up.
          2. Include any other custom fields that are used on issue screens based on data from logs (optional).
        3. Run the CSV import in your Cloud site and select the project previously migrated with the Jira Cloud Migration Assistant.

      After completing these steps, all the issues should be updated with missing field data. Projects should now have up-to-date configuration, data and can be considered fully migrated.

            Assignee:
            Unassigned
            Reporter:
            Ulisses Azevedo
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: