Issue linking via CSV using a single Dependency column

YARON LEVY_bbu1e2

HI, 

I'm doing a data migration, and the method I've chosen is:

1. import all issues (after a large scale data manipulation)
2. import all links.

 

About the links- I have 2 options: 

1. get a comma delimited linked issues - This option meens I have to link to do an Excel work - separating the field into column, and giving every column a "Dependency" name.
   for ex.: 
   issue key, Dependency,          Dependency          , Dependency
   issue A , Dependency Link A, Dependency Link B, Dependency Link C
2. getting multiple rows, with same issue, every row linked to another issue.
   for ex.: 
   issue key, Dependency
   issue A , Dependency Link A
   issue A , Dependency Link B
   issue A , Dependency Link C
   
   

I like option number 2. I prefer not doing Excel manipulations, when i have the option not to.

I saw it is actually working and only adding more links. (Unlike Labels which replaces the labels with other ones).

 

I just want an approval from JIRA official it is acceptable, since I didn't find any documented working method like this.

 

Thanks,

 

Yaron

 

Dave Theodore [Coyote Creek Consulting]

You aren't going to break anything. You may end up with data that doesn't represent what you actually want, but there is no other harm in what you propose.

You will need to include one additional column in your CSV, though. You need the issue Summary. Like the label behavior you describe, the CSV importer will replace the current value with what is in the CSV, so you should build your file with the correctly associated Summary for each IssueKey.