CSV Import Error: Issues have been skipped because they already exist in destination projects
Summary
This document provides guidance on how to resolve the "issues have been skipped" error that occurs when importing Jira issues using CSV import on the Jira Cloud.
Overview
When importing issues into Jira Cloud using a CSV file, users may encounter the following error:
xxxx of xxxx issues have been skipped because they already exist in destination projects.
This typically occurs when the "Issue ID" column is mapped during the import process.
Cause
This is expected behavior due to the external issue IDs being updated in the imported issues. As a result, the import process is not going through. We do have a feature request JRACLOUD-81999 raised for this one
Resolution
To address this problem effectively, follow the steps below:
Create a new filter using JQL that targets the project and its associated issues. Alternatively, you can use an existing filter that captures these specific issues.
After running the filter, go to the top right corner and click on the three dots. Then, choose the "Bulk change all..." option.
Locate the issues with External issue IDs from the list and proceed by clicking "Next."
Choose "Edit issues," move to the next stage, and remove the External issue IDs by selecting the checkbox next to 'Change External issue ID' and leaving the field empty to clear the value.
Once you have completed the above steps, try the import process again. This action should effectively resolve the problem, enabling a smooth continuation of the import process.