How to specify link direction when importing issues via external system CSV import

[Jochen Neuhaus]

Following the directions in the manual and in https://confluence.atlassian.com/jirakb/how-to-import-issue-links-from-a-csv-file-740262715.html, I am able to import new issues into JIRA from a CSV file and to specify issue links between the new and existing issues.

Unfortunately, for this issue link

Name	Outward Description	Inward Description
Implementation	implements	is implemented by

and this csv file:

Summary	Issue Id	Link:Implementation
new one	1	TEST-1

it always imports a new issue "new one" and outward links it to the existing TEST-1. (new one implements TEST-1)

Is is possible to directly specify an inward link in the CSV file? I would like to specify "new one is implemented by TEST-1

[Petar Petrov (Appfire) · Accepted solution]

When importing through CSV and defining links, the row represents the source issue, while the issue id or key which is specified in the appropriate "Link" column is the destination issue. A link from source to destination is always an outward link - if you want to create an inward link, you need to swap the source and destination. This, however, will not work well for existing issues - if you create a row for TEST-1 in your example, if the issue exists you'll need to have columns for all its fields, otherwise they will be reset to default values. So I don't think this will work for you.

You could look at the JSON import instead, where you can specify which is the source and which is the destination issue. Another option is to write up a Script Runner groovy script to create the links, provided that you have the mapping for the issues. Or you could do the same via REST.

[Jochen Neuhaus]

This is an important hint that CSV import will reset all fields of existing issues that are not present in the csv!

Thank you for the clarification.

I will look into the REST option.

[Omprakash Thamsetty]

@Jochen Neuhaus I am also looking for the same. Did you get any workaround or solution to import the issue with Inward description?

Thanks,

Om

[Jochen Neuhaus]

Hi @Omprakash Thamsetty,

There is no workaround using CSV, as the other answers here detail.

I wouldn't wait for Atlassian to implement the linked suggestion ticket, It's been on hold for only four years yet...

I believe, that we used the REST API in the end to both import the issues and to correctly set the link direction.

[Nikhil]

Jira currently only allows the import of outward link descriptions. 

Here's a feature request created for the ability to import inward link descriptions implemented in Jira Server application:

- CSV Importer should allow users to choose to import Issue links as Outward or Inward Description

Please vote.