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
Next: Root
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
Hi,
I'm trying to import a CSV into a blank JIRA project. I have tried both with team-managed and company-managed projects.
This is my CSV:
This is the mapping when I import to JIRA (from System > External System Import > CSV):
This is the error on importing:
The issues are imported as a flat list, without any links. Ideally they should follow the Epic > Story/Task > Subtask. Here's the screenshot:
I've gone through numerous other support questions where people faced the same issue, but I was not able to get it working for me.
Any help would be appreciated. Thanks!
Yes, it sounds like you're trying to maintain nesting in a CSV import for a Team-Managed project, which doesn't work currently.
An alternative you can explore is copying and pasting the CSV to a spreadsheet that stays in sync with Jira and connect the data that way. Visor is one such spreadsheet: https://marketplace.atlassian.com/apps/1226209/visor-flexible-spreadsheet-for-jira-roadmapping-bulk-edits?hosting=cloud&tab=overview
However, if this isn't working for a Company Managed Project, then this built-in Jira CSV import functionality should be able to work.
Take care,
Becky
Hello @Rajat Saxena
Welcome to the Atlassian community.
Is the import log you showed from an attempt to import to a Company Managed project or a Team Managed project?
Currently it is not possible to create the relationship between an Epic and its child tasks via CSV import to a Team Managed project. See this change request:
https://jira.atlassian.com/browse/JSWCLOUD-17758
Also a value should be supplied for mapping to the Parent ID field only for subtask type issues that are being imported. Don't provide that value for Tasks/Story issues that you are trying to make children of an Epic.
When importing subtasks you need to make sure that the Issue Type name you specify in the CSV matches the actual name for the subtask issue type in the destination project. The default name for a subtask issue type in Company Managed projects is "Sub-task" (with a hyphen) and in Team Managed projects it is "Subtask" (without a hyphen).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.