Jira Cloud migration to Jira Data Center: Importing a Custom Field and a System Field with the same name
Platform Notice: Cloud, Server, and Data Center - This article applies equally to all platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
It might happen that Jira contains a Custom field and a System Field with the same name.
For instance, "Environment" is a System Field that does exist on Next-Gen projects, and it might exist a custom field "Environment" created for a Classic Project Area.
What will happen with the import when there are a Custom Field and a System Field with the same name?
Both fields will be created or will just remain one? We did test this migration following the steps below, and both fields were correctly imported.
Steps used to replicate the use case
Jira Cloud:
* Custom Field "Environment" created as "Multiple Selection" and with the values "Cloud 1" and "Cloud 2";
* New Project Area of type Next-Gen created;
* We can observe that it does contain its own Environment field, but it is using a free format - We typed "something at the Environment"
Migrating to Jira Server
- Prior to creating the backup, it is required to migrate next-gen Projects to Classic;
- As part of the migration, the wizard asks for some specific actions for some fields. The "Environment" was not listed:
- The content of the Environment variable from the next-gen project was preserved during the migration to Classic
Backup your Jira Cloud application data and Import it into Jira Server
Import was successful and both fields were preserved
Caveats when using a Custom Field and a System Field with the same name
If you pull issues from Jira into Confluence, you may face the issue described on this bug: