nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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!

Accepted answers

All comments

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/

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.

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:

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.

Yossi barezer

Hi All,

I have the same issue and not able to resolve for a while trying all sort of different ideas. Is there an actual working example to look at?

Thank you,

Yossi

Maxfield Burdge

Same issue here, have yet to find a resolution.

Yossi barezer

Hello Everyone,

I hope the following can help to those that have this issue. I did my research and create the below template. It seems to be stable. Please, check and hopefully can resolve your issue.

Those are the links to the parents in the different level - the are not the same and what cause the issue. You can use 4 files. That will ensure no mistake, no warning, no error and simple to create.

However, if you create an automation to generate the Project Key in advance, as long you keep this specific order it should work. Important note: in consolidate file, the JIRA Validation step will show errors and even the Import Phase will show Warning / Errors due to the internal memory flow the validation steps of the JIRA is working. But actually, it will import well.

Let me know what do you think? if it worked for you or not.

Regard,

Yossi

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-cloud