Description

When importing issues to a classic project using CSV files, Jira may add an invalid issue type to the issue type scheme if next-gen projects exist

Steps to reproduce

1. Create a classic project
2. Create a Next-Gen project
   • I.E. the Epic issue type exists in both the Classic and Next-Gen projects. One of them, however, is only applicable for the next-gen project
3. Create a simple CSV file that defines issues and their issue types, as exemplified below

   summary,issuetype
   Teste Epic Bug,Epic
   Teste Story,Story

4. Go to Jira Settings > System > External System Import
5. Select CSV
6. Upload the file, select a Classic project as the destination project and follow the prompts

Expected result:

Issues are imported using the correct issue types

Actual results:

A Next-Gen Epic issue type is added to the issue type scheme, causing the following message to be presented:

This may cause issues to be imported using the wrong issue type.

Workaround:

An existing workaround is to import the CSV file using the issue type's IDs instead of their "Names". This can be gathered by going to Jira Settings > Issues > Issue Types and click Edit next to the issue type. The ID will be displayed on the URL

• Example : https://<instance>.atlassian.net/secure/admin/EditIssueType!default.jspa?id=<ID>

Fixing the problem:

If a CSV file has already been imported and the problem represented by the image below exists, please contact Atlassian support