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

fer
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 17, 2020

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

0 votes
David Garcia Vives February 17, 2020

Hello, 

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.

fer
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 17, 2020

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.....

Larry September 11, 2020

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