...
Hidden links types such as epic links or asset relation links Advanced Links cannot be imported with a single CSV import.
Workaround 1: 2 Imports and V-Lookup
(as recommended by Atlassian Community)
Import issues without relation linksAdvanced Links.
Export imported issues with their issue keys and summary.
Use excel V-Lookup to merge issue keys into original csv file for every row and for the links to be imported (see docu).
Import csv again to update issue links for existing issues (map issue key as well to avoid creation of issue duplicates).
Workaround 2: Scripted post-function
(as recommended by STAGIL using Script Runner or Power Scripts)
Import issues with epic links and relation links Advanced Links as default links (i.e. relates to).
Allow users to change link types in bulk change via workflow - transition with a scripted post-function. Show this option only to issues that have issue links of defined link type.
The following scripts allows to define allow defining link type per issue type. I.e. you can configure a different target parent link for issues of type “Story” then than for issues of type “Epic”.
...
SAJ field ID (11000) to be replaced with actual ID.
Above The above script refers to outward links only. If you want to replace inward links instead, sourceId (line 11) and destinationId destinationID (line 16) need to be swapped.
...
Issue link type ID (12345) to be replaced with actual ID.
Above The above script refers to outward links only. If you want to look for inward links instead, sourceId (line 5) to be replaced with destinationId.
...