How to retain field data such as Fix Versions, Repository data(Bitbucket/Github) & Custom Fields when migrating from Team-Managed project to Company Managed or vice versa
Platform Notice: Cloud - This article applies to Atlassian products on the cloud platform.
要約
While migrating/moving issues from team managed to company-managed or vice versa, some information is lost, while other fields stays intact. In this article, we have discussed how to manage Fix Versions, Repository data(Bitbucket/Github) & Custom Fields data so that most information can be saved during the process. This is an extension to :
環境
Jira Cloud
ソリューション
For FixVersions field migration:
The FixVersions value would be migrated if the same version (with the same name) exists in the CM project. So the following steps can be taken to avoid fix-version loss:
Create a fix version with the same name in both the TM and the CM projects:
Update the issue with the above version and map the same with the one in the CM project
Once the issue is moved, the FixVersion will remain intact
For Development data migration:
Development data stays intact by default when issues are moved from one project to another.
However, the old issue key would be displayed when trying to view the data, the reason being, the dev tool would still have a record of the old issue key and not the new one.
免責事項
While the development information will be brought over for each issue that gets moved to the new Company-Managed Project, please keep in mind that the references in the panel will still point to the original issue. For example, if moving from TMP-1 to CMP-1, the development information will still point to TMP-1 (due to the smart commits and other information in Github), but any links from Github over to Jira will successfully redirect from TMP-1 to CMP-1.
Because of this use of the original project key and issue number to redirect, we will be unable to reclaim the original project key from the Team-Managed Project. So it is recommended to keep the original Team-Managed Project around (possibly archive the project if it's no longer being used) to keep the reference link intact.
If the original Team-Managed Project is Deleted to free up the project key for reuse in another project, it will break the reference link and lose the relevant Development panel data on the existing issues.
For Custom fields
Data can be populated in the fields via Jira's External CSV Import.
The high-level steps would be:
Export all issues from the TMP project into CSV.
Bulk-move the issues from the TMP project to the CMP project.
Modify the earlier exported CSV file, changing the issue keys to match the issue keys in the CMP project.
Import the CSV to bulk update the fields for the issues in the CMP project via External CSV Import.
Alternatively, TMP can be left untouched and bulk-create the issues in the CMP project instead:
Export all issues from the TMP project into CSV.
Import the CSV to bulk create issues in the CMP project via External CSV Import.
(Optional) Archive or delete the TMP project.
Practical Example:
The following video demonstrates a migration from TMP to CMP, manipulating the CSV files and importing the custom fields:
Keep in mind that if your project has more than 1000 issues, you need to follow the Knowledge Base Export Over 1000 Results to Excel from JIRA Cloud to export all issues.