CSV import with Epic as parent

[j_begemann]

I am unable to import epics as a parent via csv. I created a simple example by exporting a minimal set of issues to csv and trying to re-import them.

Issue Type;Issue key;Issue id;Summary;Parent
Epic;TESTTENS-90;16361;Epic 1;
Task;TESTTENS-91;16362;Task 1;16361
Sub-task;TESTTENS-92;16363;Sub-task 1;16362
Sub-task;TESTTENS-93;16364;Sub-task 2;16362

 The import config:

the error message i get:

2026-02-23 13:20:54,128 INFO - ------------------------------
2026-02-23 13:20:54,128 INFO - Importing: Work Items
2026-02-23 13:20:54,128 INFO - ------------------------------
2026-02-23 13:20:54,128 INFO - Only new items will be imported
2026-02-23 13:20:54,285 INFO - Importing work item: [externalId='16361', summary='Epic 1']
2026-02-23 13:20:55,360 WARN - Cannot add value [ [TESTTENS-106] ] to CustomField Epic Link in Work item with summary 'Task 1'. Probably value was in incorrect format
2026-02-23 13:20:55,365 INFO - Importing work item: [externalId='16362', summary='Task 1']
2026-02-23 13:20:56,084 INFO - Importing work item: [externalId='16363', summary='Sub-task 1']
2026-02-23 13:20:56,825 INFO - Importing work item: [externalId='16364', summary='Sub-task 2']
2026-02-23 13:20:57,623 INFO - 4 work items successfully created
2026-02-23 13:20:57,623 INFO - 0 out of 4 work items successfully updated
2026-02-23 13:20:57,628 INFO - ------------------------------
2026-02-23 13:20:57,628 INFO - Finished Importing : Work Items
2026-02-23 13:20:57,628 INFO - ------------------------------
2026-02-23 13:20:57,697 INFO - ------------------------------
2026-02-23 13:20:57,697 INFO - Importing: Work item 
2026-02-23 13:20:57,697 INFO - ------------------------------
2026-02-23 13:20:57,697 INFO - Only new items will be imported
2026-02-23 13:20:57,706 INFO - Linking 'TESTTENS-108' and 'TESTTENS-107' as sub-task-link
2026-02-23 13:20:58,226 INFO - Created parent-child (sub-task) relationship between TESTTENS-108 and TESTTENS-107
2026-02-23 13:20:58,234 INFO - Linking 'TESTTENS-109' and 'TESTTENS-107' as sub-task-link
2026-02-23 13:20:58,696 INFO - Created parent-child (sub-task) relationship between TESTTENS-109 and TESTTENS-107
2026-02-23 13:20:58,702 INFO - ------------------------------
2026-02-23 13:20:58,702 INFO - Finished Importing : Work item 
2026-02-23 13:20:58,702 INFO - ------------------------------

importing multiple issues with parent links (Epic-Task-Subtask) was no problem and an quick task using jira server a few years back.. now i can not do it at all.... 

[Trudy Claspill]

Hello @j_begemann 

While it did previously work to create Epics and their child issues within the same CSV file and also actually link the child issues to the Epic through the Parent field, that functionality broke at some point. There were some publicly visible issues recorded about this that I have listed in my response on this post:

https://community.atlassian.com/forums/Jira-questions/CSV-Import-is-not-linking-items-to-epics/qaq-p/3155548?

There is a suggested workaround in this issue:

https://jira.atlassian.com/browse/JRACLOUD-93760

[John Funk]

Hi J,

I am confused by what you are trying to do. Are you just trying to update the Parent field with the Epic for a list of current work items? 

[j_begemann]

not sure whats confusing about the problem. The content of the csv is given in the thread. I am trying to import this exact CSV into an empty company manged project.

The parent link for Sub-task --> Task is created succesfully, the link for Task --> Epic is not.

[John Funk]

You don't need to have an attitude when trying to get help. We are users here just like you. And your last sentence is not easily derived from the data you provided. 

Having said that, is your use case that you are wanting in a single CSV import to create an Epic and children under the Epic and sub-tasks under the Epic children? 

Are you are wanting something else? 

[j_begemann]

sorry, the response was not intended to be rude. I thought the initial posting has all relevant information.

Yes, the assumed use-case is correct. 

• single CSV import
• create an Epic and children under the Epic
• create sub-tasks under the Epic children

using this workflow on jira-server worked as intened (with the now deprecated fields "Epic link") in a single import.

[John Funk]

Fair enough and thank you for that. Just so you are aware, I was confused why you were exporting and then reimporting when trying to create all 3 at one time. 

Regardless, here is what you can try:

Issue ID	Issue Type	Parent	Summary
1	Epic		Epic 1
	Task	1	Task 2
	Story	1	Story 1
2	Task		Task 1
	Sub-task	2	Sub-task 1
	Sub-task	2	Sub-task 2

This is setup to do those creations independently of each other and works. I have not tried to create all three at one time, but I think it should work. Just ignore the two rows under the Epic and move everything up. 

Now, having said all of that, there is no control how Jira processes rows when it does the import - meaning it might process row 5 before row 3. Try it with a small subset like you are doing and see how it goes. 

[j_begemann]

since i assumed the error was on my custom data, i created a simple example in the testproject and export the tickets to be sure about the fields and links.

Using your exact example yields the same error

Issue ID;Issue Type;Parent;Summary
1;Epic;;Epic 1
;Task;1;Task 2
;Story;1;Story 1
2;Task;;Task 1
;Sub-task;2;Sub-task 1
;Sub-task;2;Sub-task 2

Import field configuration:

Error message:

"funny" thing about the error message is, that Atlassian is referring to the CustomField as  "Epic Link" even though it is set to  "Parent" in the config.

All issues are created succesfully. But as you can see, the Story 1 and Task 2 are not the children from Epic 1.

The only workaround i can see, is creating the Epics in the first import and adding the children in a second import using the known Issue-Keys for the epics .. but that is tedious and not very practical and contradicts the automation aspect.

[John Funk]

Yes, that is very weird that it is trying to use Epic Link and calling it a custom field. The CSV import has been flaky for awhile now. Sometimes you can do it through Settings > System > External system Import and it work but not though the import through the Project. Then a week or two later, it works through the other process but not the one it worked through before. So, you might want to try the import again through the other path that you didn't do this time and see what happens. 

Other than that, yes you can create the Epics first. Then I would just update the CSV directly with the actual values instead of tryin to export and reimport. But do know that it should work by what you are doing, and it recognized by Atlassian as a bug that it doesn't. 

[j_begemann]

i only use the external system import. Through the project directly i cannot map all needed fields ("original estimtate" for example).. i cannot remember to have that many problems with the on premise version of jira for such simple tasks ...

probably could have solved this by writing an import script faster than trying to use this buggy mess of an import ... 

thanks for your response, looks like that this is a problem on the atlassian side rather than an user error.

[Ugnius Aušra]

Hello @j_begemann 

Last time similar issue occurred in - https://community.atlassian.com/forums/Jira-questions/Csv-importer-not-working-for-parent/qaq-p/2766507

"Epic link" was renamed to "Parent" and when uploading CSV for some users it worked for a while (I don't know if it's still working), but i suggest you to try. 

[j_begemann]

no, "Epic link" does not work anymore (as of september 2025). The answers in the linked thread are all refereing to a date before september 25.

[Ugnius Aušra]

Yes, you are right.

I would recommend, to check these documentations:

https://support.atlassian.com/jira/kb/keep-issue-parent-child-mapping-during-csv-import-to-jira-cloud/

https://support.atlassian.com/jira/kb/fix-epic-link-csv-import-format-errors-jira/

[j_begemann]

yes, even using the exact same sample and steps from the links you provided does not work. Try it yourself, would be interesting if anybody can get this to work - if so, it must be an error on my side.