Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

missing EPIC field when importing CSV files into Jira next gen project

I am trying to export EPIC and issue child issues to CSV, and import them into a new next gen project. 

All issues are created but no EPIC or parent issues.


Any one had the same issue?


Thanks in advance!

1 answer


Yes we did have the same problem. Some info is lost when you switch the project type or export-import between different kind of projects.

Thanks David. I think only the EPIC and the link between EPIC and issues seem to get lost. I researched online and it seems like this is a well known issue. Maybe the work around is to export the issues to a classic project then move them to next gen.....

That is a ludicrous thing to suggest as a workaround. This should be a working feature. It's something we rely on at the beginning of projects and as a mechanism for doing bulk changes through a spreadsheet. It makes certain things way easier to visualize.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events