I will explain our setup and the issue in detail to make the situation fully clear.
Jira Cloud
Team-managed project (not company-managed)
We are intentionally not using Epic Link
We are using the new hierarchy model based on:
Work type (Epic / Task / Sub-task)
Parent (internal work item ID)
This approach is based directly on Atlassian’s official documentation for CSV imports using Work item ID and Parent.
Despite the correct behavior above, the import always finishes with warnings such as:
"Cannot add value [ Work item ] to CustomField [JTE-XXX] in Epic Link.
Probably value was in incorrect format."
And the tasks are not properly linked to their corresponding epic.
It is also strange that the issue is inconsistent. In some cases, when I remove and re-add tasks, they link correctly, but when I repeat the same process, they are no longer linked again.
Thank you
Saba
Hello @Saba Kasrelou
Welcome to the Atlassian community.
This is a known limitation. Refer to
https://jira.atlassian.com/browse/JRACLOUD-83172
And there is a known bug on this functionality showing that specific error for Company Managed projects. I believe it is affecting Team managed projects also.
https://jira.atlassian.com/browse/JRACLOUD-96848
There is also this issue which could relate to your statements about trying the same process and the links no longer being present.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.