Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-82762

C2C migration of a single project creates duplicated custom fields with (migrated) in their name

XMLWordPrintable

    • 2,432
    • 198

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

       

      Atlassian Update -Dec 2024

      Hi everyone,

      Thank you for taking the time to share your feature request with us. Your input is greatly appreciated, and we understand the effort and dedication it takes to provide us with your thoughts and ideas.

      we plan to launch an EAP in mid Dec 2024 to address handling of duplicated Jira config entities, refer community post for more details and to sign up to early access.

      Regards
      Rahil Hameed  
      Senior PM - Cloud Transitions

       

      Issue Summary

      When migrating a single project to a site the first time using C2C method, a new custom field will be created with (migrated) appended in their name.

      This is reproducible on Data Center: N/A

      Steps to Reproduce

      1. Choose a destination site where C2C migration has not been performed yet.
      2. In the source site, select a project and perform a C2C migration to the destination site. 
      3. Go to Settings > Issues > Custom fields 

      Expected Results

      If the custom field in the source and the destination sites have the same name, and underlying properties, they should be merged in one custom field to avoid unnecessary duplicates. 

      Actual Results

      If the custom field in the source and the destination sites have the same name, and underlying properties, a new custom field is still created in the destination site with (migrated) appended on the name. 

      Workaround

      As a workaround, it is possible to merge duplicated fields after the migrations. You can find detailed steps to achieve that in the documentation below:

      This is also mentioned on the article, but please note that the steps mentioned above have the potential to irrevocably change issue data within Jira. As such, we recommend that you create a backup of your data before attempting any changes. 

      Other than that, considering the potential limitations of CSV imports (mainly on team-managed projects) it might be best to test the solution in just a few issues before applying it to all issues.

        1. Screenshot 2024-01-11 at 11.54.12.png
          Screenshot 2024-01-11 at 11.54.12.png
          85 kB
        2. Screenshot 2024-01-11 at 11.45.56.png
          Screenshot 2024-01-11 at 11.45.56.png
          31 kB

              77106d063435 Soumyadeep Chatterjee
              6b2430609069 Alexis
              Votes:
              79 Vote for this issue
              Watchers:
              108 Start watching this issue

                Created:
                Updated: