You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I am not able to import new issues with an existing epic name/id. I have tried linking the parent id, but I get the following error.
I have searched and searched on how to enable the Epic Link, Parent, and any field that would help me do this but only the Parent ID is visible on the import.
Hello @Jeremy Whittington
Thank you for reaching out.
Indeed, there are some bugs in Jira Next-gen that causes the CSV import/export functionality to don't work as expected, including the ability to link Epics to imported issues as you can see in the report below:
Ability to import issues with parent-child(epic-task) relationship to next-gen project
These bugs are caused due to the Next-gen architecture which uses unique identities for each project, so they are not properly mapped in the External system import.
You can check the link below for more details:
Unable to perform direct migration of the project from cloud to cloud due to CSV import bugs with Next-Gen projects
Feel free to vote and watch these bugs to increase its priority and also receive notifications about its fix implementation.
For now, if you need to use the CSV import functionality, we recommend you to migrate your issues to a Classic project by following the steps of the documentation below:
Migrate between next-gen and classic projects
Let us know if you have any questions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.