Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How to import issue link - (relates to) via CSV


Is JIM upgraded to import issue links via CSV ? I am interested in importing 2 items with 'relates to' issue linking between them. (I looked at the available faq in the forum, but did not find any option other than jelly)

Please help.

3 answers

1 accepted

8 votes
Answer accepted


It's possible - we have just release to marketplace JIM 6.2.20 which allows to import/create Issue links via CSV. It's available for both CSV admin and non-admin importer. You can install this version of JIM to JIRA 6.2+ and it will be by default bundled with JIRA 6.4+

I'm afraid we do not have available docs for this process yet, but it's really similar to import of SubTasks: You need to map one column as Issue ID, and the other as desired link (e.g. "Link 'relates to'"). The 'Link' column need to have a value corresponding to other issue 'Issue Id' value or it needs to be an issue key of already existing issue. For example:

Summary,Issue Id,Link One,Link One,Link Two
House  ,       1,       2,       3,       2
Patio  ,       2,        ,        ,
Garden ,       3,  TEST-1,        ,

The file above would create three issues with correctly created issue links:

  • Issue 'House' will have three links:
    • Two links of type "Link One" to issue 'Patio' and 'Garden'
    • One link of type "Link Two" to issue 'Patio'
  • Issue 'Garden' will be linked to issue with key 'TEST-1'

I didn't expect it so soon: +1

Currently not possible, but soon, see


I have two existing issues [ RJM-169 (Foo-1) and RJM-170 (Foo-2) ]. My import csv has

SummaryIssue IdBlocks


After the import, my expectation is to see both RJM-169 and RJM-170 are showing issues links 'blocks' to each other. But instead, a new item RJM-171 is created, which has RJM-169 as External ID and RJM-170 as the 'Blocked' link.  Please help to understand this better.          

My requirement is to create links between EXISTING ITEMS ONLY. I don't want to create new items.

image2015-2-19 16:12:33.png



Unfortunately the non-admin CSV Importer is securely designed and it only allows to create new issues. If you'd like to update existing issues, you will need to use the admin CSV Importer available in External System Import menu in system settings.

Hi, I am using the admin External Importer. Is there anything else that I may be missing ?.

Like msi72805 likes this

In that case, CSV Importer identifies the issue that you'd like to update by Issue Key mapping. If your CSV file looks like the table that you have posted in this answer then please map it this way: - Summary -> Summary - Issue Id -> Issue Key - Blocks -> Link 'blocks' This way imorter will update the issue that is pointed by 'Issue Key' mapping.

This worked great!! Thanks a lot. Could you please look and advice on this ticket JST-128657. I have received an answer but not accepted it yet.

Hello, regarding above:


Unfortunately the non-admin CSV Importer is securely designed and it only allows to create new issues. If you'd like to update existing issues, you will need to use the admin CSV Importer available in External System Import menu in system settings.


Is this still the case? 

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.

Hi Nikhil,

I had the same challenge some times ago regarding "Inward" and "Outward". And I found a simple solution (in case I have understood your question correctly ;-):

Assume you have the two Jira projects "A" and "B" and in A issue "A-1" and in B  issue "B-1".

1. Use Case

If you want to import a link between A-1 and B-1 in the sense "A-1 contains B-1" the csv-file should look like this:

IssueKey ;LinkKey ;Summary
A-1; B-1;

In the "External System Import" you would select the file and - important - the Jira project "A". That is because Jira generates the link as parent-relationship of the linktype "Story" into the issues of A (in this case A-1). As mentioned in the other contributions the import of the links is only possible in one direction: parent -> child. The result of this import would look like this:

  • A-1 contains B-1 (in the detailed view of A-1)
  • B-1 is part of A-1 (in the detailed view of B-1)

2. Use Case

Let us now assume you would like to come the other way around. You are working or thinking about B. You have imported the issue B-2 and B-3 somehow (without link). And you would like to import the link between B-2, B-3 and A-1 in the sense of: "B-2 is part of A-1" and "B-3 is part of A-1". That seems to be not possible because it looks like a child relation from B-2, B-3 point of view. And as mentioned before in Jira currently only "parent"-relations are importable. Maybe you think about an import file like this:

IssueKey ;LinkKey ;Summary
B-1; A-1;
B-2; A-1

And during the "External System Import" you would choose the file and the Jira project B because you would like to update the B-issues. During the assignment of the fields from the file to the Jira project you use "IssueKey -> Issue Key", "Summary -> Summary", and "LinkKey -> Link Story". Jira would generate the following links after such an import: "B-2 contains A-1" and "B-3 contains A-1" or the other way around (when you look in the detailed view of A-1): "A-1 is part of B-2" and "A-1 is part of B-3".

That is not what you aim at in this use case.

The trick is to use the same perspective as explained in use case one: you should define a csv-file like this:

IssueKey ;LinkKey ;Summary
A-1; B-2;
A-1; B-3;

During the "External System Import" you now select the appropriate file and the project "A" (and NOT "B") to import the links. With "IssueKey -> Issue Key", "Summary -> Summary", and "LinkKey -> Link Story" Jira now would generate the following links:

  • A-1 contains B-2
  • A-1 contains B-3

or according to the other direction (looking in the views of B-2, B-3):

  • B-2 is part of A-1
  • B-3 is part of A-1

That is what we wanted ;-)

Of course this way only works in case one has the needed edit-permissions in project A.

When I have the task to import several linktypes I always import them separately because this is the easiest way. But to be honest I haven't got the challenge to import more than one or two linktypes to a specific set of issues.

I assume that the mentioned way is documented somewhere in the Jira community...but with this reply you do not have the necessity to search for it :-)

Hope that I could help you with my "story",

kind regards.


Suggest an answer

Log in or Sign up to answer

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you