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

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • 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 specify link direction when importing issues via external system CSV import

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

NameOutward DescriptionInward Description
Implementationimplementsis implemented by

and this csv file:

Summary
Issue Id
Link:Implementation
new one
1TEST-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

 

 

2 answers

1 accepted

1 vote
Answer accepted

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.

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.

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.

Suggest an answer

Log in or Sign up to answer
TAGS

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