Fixing Parent Links after Jira migration
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center 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
After a Jira migration, the Advanced Roadmaps field "Parent Link" is set to a wrong issue.
Cause
The Parent Link custom field uses a different way of storing the references than regular custom fields, potentially causing the references to get mixed.
Solution
- In the original instance, export the parent issues (typically Epic) to CSV with the columns:
- Project
- Issue Key
- Parent Link
- Summary
- Import the CSV in the new instance to fix the parent links
Last modified on Mar 1, 2023
Powered by Confluence and Scroll Viewport.