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

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)

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!

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?

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

Thanks!

Hello @Ait Benhida Fatimaezzahra 

If you want SDM-350 to be the parent of SET-4912, you need to select the SDM project  not SET at the project selection on Setup step.

Otherwise, the behaviour you'll get is a new SET issue being created, instead of SDM-350 being reused.

:)

Hi,

Thank you for your suggestion.

I followed the recommended format and mapping:

Issue Key -> Work item key

Linked Issue Key -> Link "Parent-Child"

Summary -> Summary

Initially, when I selected the SET project, Jira linked SET-350 to SET-4912 instead of reusing SDM-350.

I then retried the import by selecting the SDM project as suggested.

The link was created successfully, but the result is still not what I need:

SDM-350 is parent of SET-4912

whereas the expected relationship is:

SET-4912 is parent of SDM-350

When I reverse the values in the CSV:

CSV
Issue Key,Linked Issue Key

SET-4912,SDM-350
Afficher plus de lignes
Jira creates or uses SDM-4912 instead of SET-4912.

It seems that Jira is converting the issue key to the selected project during the import.

How can I create a Parent-Child link between existing issues from different projects (SET and SDM) while preserving the original issue keys?

Thanks for your help.

@Ait Benhida Fatimaezzahra 

C'est normal, c'est le même principe que lors de ton action précédente.

Si tu inverses l'import CSV sans changer de projet pendant la configuration, l'effet sera identique.

Sélectionne donc le projet SET cette fois-ci avec le csv 

Issue Key,Linked Issue Key

SET-4912,SDM-350

ca va inverser le lien 

merci beaucoup le fichier a été bien importé

Thanks a lot for your help