1/11/2024 0 Comments Github actions marketplace![]() ![]() 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. The following video demonstrates a migration from TMP to CMP, manipulating the CSV files and importing the custom fields: (Optional) Archive or delete the TMP project. Import the CSV to bulk create issues in the CMP project via External CSV Import. Import the CSV to bulk update the fields for the issues in the CMP project via External CSV Import.Īlternatively, TMP can be left untouched and bulk-create the issues in the CMP project instead: Modify the earlier exported CSV file, changing the issue keys to match the issue keys in the CMP project. 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.ĭata can be populated in the fields via Jira's External CSV Import.Įxport all issues from the TMP project into CSV.īulk-move the issues from the TMP project to the CMP 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. 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.īecause 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. 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. 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. Once the issue is moved, the FixVersion will remain intactĭevelopment data stays intact by default when issues are moved from one project to another. Update the issue with the above version and map the same with the one in the CM project So the following steps can be taken to avoid fix-version loss:Ĭreate a fix version with the same name in both the TM and the CM projects: The FixVersions value would be migrated if the same version (with the same name) exists in the CM project. Migrate between team-managed and company-managed projects.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. While migrating/moving issues from team managed to company-managed or vice versa, some information is lost, while other fields stays intact. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |