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

Support the migration of Team user defined custom field data

XMLWordPrintable

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

      Problem Definition

      At the time of this request, the 'Team' type user defined custom field is not supported for migration, and is documented as not being migrated for project-by-project.

      Suggested Solution

      JCMA support the migration of this custom field, and it's data, when migrating project-by-project.

      Why this is important

      With the recent unification of Teams In Jira in Cloud, the expectation of customers is that this data would be supported for migration. 

      The below user defined custom field types are currently unsupported for migration -

      • Parent Link
      • Team
      • Target start
      • Target end

      Current Workarounds

      1. After completing project data migration, create the missing fields in the destination Jira Cloud
        • Make sure to assign the custom fields to the relevant screens
      2. Add data for missing fields with [CSV export-import|support.atlassian.com/jira-cloud-administration/docs/import-data-from-a-csv-file]

              Unassigned Unassigned
              zhill Zach
              Votes:
              1 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated: