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:
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
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.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs