Issue Summary

When importing issues via CSV to a different Jira Cloud project, issue links (e.g., "is cloned by", "blocks", "relates to") are not carried over to the destination project. The CSV importer maps standard fields but does not fully support importing all issue link types, particularly inward links.

Expected Results

Provide full support for importing both inward and outward issue links via CSV import, including link types such as "is cloned by", "blocks", and "relates to". The mapping step should allow users to select and map link columns to their corresponding link types bidirectionally.

Actual Results

 

When importing issues via CSV to a destination project, issue links are not carried over. The CSV importer only supports standard fields such as Summary, Description, Status, and Assignee. There is no column or mapping option available to recreate issue relationships, resulting in all issue links being lost after the import. Users are required to manually recreate every link in the destination project, which is time-consuming and error-prone - especially for large-scale imports.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available