Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
Celebration

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

Join now to unlock these features and more

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.

Get started Tell me more
Atlassian Community about banner
4,551,698
Community Members
 
Community Events
184
Community Groups

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

fer
fer Feb 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!

Answer
Watch
Like Be the first to like this
313 views

1 answer

0 votes
David Garcia Vives
David Garcia Vives Feb 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.

View More Comments
fer
fer Feb 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.....

Like
Larry
Larry Sep 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.

Like
Reply

Suggest an answer

Log in or Sign up to answer
Atlassian logo
Team-managed projects
TAGS
AUG Leaders

Atlassian Community Events

See all events