Import issue "Cannot add value [ [PROJ-15986] ] to CustomField Epic Link in Work item

[frank_schilperoort]

I am trying to import the following example CSV:

Internal ID,Issue ID,Project,Issue type,Parent,Epic name,Summary
1,Project A - 1,Project A,Initiative,,,[Project A] Initiative summary
2,Project A - 2,Project A,Epic,Project A - 1,[Project A] Epic name,[Project A] Epic summary
3,Project A - 3,Project A,Story,Project A - 2,,Story summary

Using the following configuration: 

However, I get the following error:

2026-01-20 09:17:15,963 INFO - Importing work item: [externalId='Project A - 1', summary='[Project A ] Initiative summary']
2026-01-20 09:17:17,943 INFO - Importing work item: [externalId='Project A - 2', summary='[Project A ] Epic summary']
2026-01-20 09:17:19,870 WARN - Cannot add value [ [PROJ-15986] ] to CustomField Epic Link in Work item with summary 'Story summary'. Probably value was in incorrect format
2026-01-20 09:17:19,878 INFO - Importing work item: [externalId='Project A - 3', summary='Story summary']
2026-01-20 09:17:20,830 INFO - 3 work items successfully created

 This worked before. However, now I consistently get this error. I have tried all kinds of ways to prevent the error but to no avail. Thanks in advance!

[Marc -Devoteam-]

Hi @frank_schilperoort 

You should use the Parent field, the Epic Link field has been deprecated in 2024.

This field can only contain work item keys, no other information

[frank_schilperoort]

Thanks for your input. As you can see above I am using the parent field. I am not using the Epic Link, even though the error does suggest this. 

[Marc -Devoteam-]

Hi @frank_schilperoort 

Based on your reply to @Madhumitha N  This can only be done, by using issue IDs using the Parent field in the CSV file, and map them, see the lik provided by @Madhumitha N 

Then you don't need to map the field issue key, as keys don't exist yet.

[frank_schilperoort]

Yes exactly, that's what I am doing. This leads to the error, however. 

[Marc -Devoteam-]

Hi @frank_schilperoort 

What information do you have set in parent child relation options?

You example in the initial question, doesn't represent it.

You CSV needs to columns (I always use) issue id and parent.

So if row 1 is the Epic to be created:

Type,Summary,Description,issue id, parent id
Epic,Epic 1,epic1,1,
Story,Story1,story1,2,1
Sub-task,Sub-task1,sub-taks1,,2

Also see the part "Map issue IDs using the Parent field in the CSV file" in the link of @Madhumitha N , work item key column can be skipped.

[frank_schilperoort]

Hi, 

Thanks for your comment. You can see all the information in my question above. I added the CSV I used as text. 

[Marc -Devoteam-]

Hi @frank_schilperoort 

This is incorrect

Internal ID,Issue ID,Project,Issue type,Parent,Epic name,Summary
1,Project A - 1,Project A,Initiative,,,[Project A] Initiative summary
2,Project A - 2,Project A,Epic,Project A - 1,[Project A] Epic name,[Project A] Epic summary
3,Project A - 3,Project A,Story,Project A - 2,,Story summary

Matching on issue id and parent column is on the numbers, so if internal id is 1 for initiative, for epic it is 2, the parent column on the epic should be set to 1, as this is the iid of the Initiative.

Correct is:

Internal ID,Parent, Issue type,Epic name,Summary
1,,Initiative,,[Project A] Initiative summary
2,1,Epic,[Project A] Epic name,[Project A] Epic summary
3,2,Story,,Story summary

[frank_schilperoort]

Hi Marc, I tried what you suggest but I get this error: 

[Marc -Devoteam-]

@frank_schilperoort 

CSV column internal ID needs to map to Issue ID and CSV column Parent to parent

[frank_schilperoort]

Hi Marc, thanks for your suggestion. I now tried to import the following: 

Issue ID,Project,Issue type,Parent,Epic name,Summary
1,Project A, Initiative,,,Initiative summary
2,Project A,Epic,1,[Epic summary,Epic summary
3,Project A,Story,2,,Story summary


I still get the following error: 

Cannot add value [ [COPS-16068] ] to CustomField Epic Link in Work item with summary 'Story summary'. Probably value was in incorrect format

[Marc -Devoteam-]

Hi @frank_schilperoort 

Try otherwise Work Item ID, or is your import based on issues of multiple spaces (projects)?

If this is the case you need to specify additional column in the CSV an map them in the import.

Additional columns to specify: "Space name" and "Space key"

See all CSV import information; https://support.atlassian.com/jira-cloud-administration/docs/import-data-from-a-csv-file/ 

[frank_schilperoort]

Yes, "Issue ID" in the CSV maps to "Work item ID" in the CSV import in Jira. The import is to create issues on just one space.

[Marc -Devoteam-]

@frank_schilperoort 

Please show a screenshot of your mapping.

[Madhumitha N]

Hello @frank_schilperoort ,

The Epic Link field expects the issue key of the Epic (e.g., PROJ-15986), not the Issue ID or summary.

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

[frank_schilperoort]

Thanks for your input. I am not using the Epic Link field as you can see in my configuration screenshot. 

[Madhumitha N]

For me, your mapping looks correct for Parent, but the values in your CSV for Parent must match the expected format (the Epic’s issue key, not an ID). This should resolve the Epic Link error.

[frank_schilperoort]

Hi, that would be strange. How would I be able to know the issue key before the tickets are created? The method I am following used to work fine before. 

What should I fill in for the issue key? 

Also, if I try this I get the following disclaimer in JIRA: 

[Madhumitha N]

As an alternative, you can import work items project-wise by importing parent items first and then their sub-tasks.
From the Filter page, open the three-dot menu (top right) and select Import work items from CSV, or go to Project → All work items → Import work items from CSV.

In your CSV, include a Parent column containing the work item key of the corresponding parent item. During the import, ensure that this column is correctly mapped to the Parent field so the hierarchy is created properly.