Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

CSV Import - Create "is parent of / is child of" issue links between existing issues

Ait Benhida Fatimaezzahra
August 31, 2026

Hi everyone,

I'm trying to create issue links between existing Jira issues using a CSV import in Jira Cloud.

Existing issues
Parent issue: Y-123
Child issue: X-456
The relationship I want is:

Y-123 is parent of X-456
(or equivalently)

X-456 is child of Y-123
Afficher plus de lignes
Context
I initially tried using the Parent field but discovered that both issues are of type Deliverable and Jira only allows Epics as parents in our hierarchy.

I then noticed that existing relationships in the project are displayed under Issue Links as:

is child of
is parent of
 
Afficher plus de lignes
rather than in the Jira Parent field.

CSV used
CSV
Issue Key,Linked Issues,Link type,Summary
X-456,Y-123,is child of,Test Summary
Afficher plus de lignes
Mapping used
Issue Key -> Issue Key
Linked Issues -> Linked Issues
Link type -> Link "Parent-Child"
Summary -> Summary
Unable to link issue ...
Unable to find imported issue key for external ID 'is child of'
 
Destination issue not found
No issues were created or updated.

Question
What is the correct CSV structure and field mapping to create an existing Parent-Child issue link ("is parent of / is child of") between already existing Jira issues?

Has anyone successfully imported this type of issue link in Jira Cloud?

1 answer

0 votes
Lalithesh
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
August 31, 2026

Hi @Ait Benhida Fatimaezzahra 

Welcome to the Atlassian community!

You can try this format

 Issue Key  Linked Issue Key Summary
 Y-123  X-456  

 

Mapping:

Issue Key -> work item key

Linked Issue key -> link"Parent-child"

Summary -> Summary. You can leave the checkbox empty

Cheers!

Ait Benhida Fatimaezzahra
August 31, 2026

Thank you.

For the field mapping step, could you please confirm the exact Jira field mapping?

Should it be:

Issue Key        -> Issue Key
Linked Issue Key -> Linked Issues
Link Type        -> Link "Parent-Child"

Or should the link type be mapped differently?

Lalithesh
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
August 31, 2026

Hi @Ait Benhida Fatimaezzahra 

try the below format

Issue Key        -> work item key
Linked Issue Key -> link"Parent-child" (your link type name)
Summary        -> Summary (Leave the checkbox empty)

 

Screenshot 2026-08-31 181723.png

 

I'd suggest you to create a simple test CSV with just one row and then do a bulk import based on the test run

Cheers!

Ait Benhida Fatimaezzahra
August 31, 2026

The link is now created successfully. However Jira resolves SDM-350 as SET-350.

Import log shows:

Linking 'SET-350' and 'SET-4912' as Parent-Child
while the CSV contains:

CSV

Issue Key,Linked Issue Key

SDM-350,SET-4912

Is there any limitation when importing Parent-Child links between issues from different projects?

Lalithesh
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
August 31, 2026

That's strange, I have just reproduced this and did not encounter any issues. Adding screen grabs for ref

Screenshot 2026-08-31 183638.png

 

Screenshot 2026-08-31 183729.png

 

Thanks!

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Product Admin Site Admin
TAGS
AUG Leaders

Atlassian Community Events