How to copy issues from one project to another while having parent links and epic links mapped?

Rinaldi James Michael
Contributor
May 29, 2024

Jira Data center currently provides two options to copy issues. One being "Cloning using Automation", the other being Export the JQL csv and use "External Import".

The problem with these methods is the parent links and epic links. I would like to have the sub tasks and child tasks point to the new 'parent issue copies' instead of the original issue (where applicable).

Is there a better way to copy issues while solving the above mentioned?

1 answer

1 vote
Rilwan Ahmed
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 29, 2024

Hi @Rinaldi James Michael ,

This can be achieved by adding required columns to your csv file before importing. 

More details in https://confluence.atlassian.com/jirakb/how-to-import-issue-links-from-a-csv-file-in-jira-740262715.html

Please note: Always try in test Jira OR if you don't have test Jira, try for a single test ticket

Rinaldi James Michael
Contributor
May 30, 2024

But in this method:

1. Attachments aren't copied. They're just linked to the original.

2. The same with parent tasks, sub tasks and Epic links. Links are generally mixed up.

Suggest an answer

Log in or Sign up to answer