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.
Reaching out with what I hope is an easy question. I'm trying to do a simple CSV import for tickets in upcoming sprints. When trying to map the Epics so I don't have to select "Add Epic" afterward, I'm finding difficulty. I've tried using Issue Key, Issue ID and Parent ID. My csv file headers are:
They're all exact match, I just can't figure out what to include in the epic name header. I saw a similar post from 2020 about a bug, but I've got to imagine things have been fixed since then? Any suggestions here?
Hello @Ekow Essel
Welcome to the Atlassian community.
Are you importing the issue into a Company Managed project or a Team Managed project?
Currently it is not possible to set the parent Epic for a child issue if you are importing to a Team Managed project. That is noted in this issue:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.