When I import a CSV the Issue Type field does not import correctly

[Chris Ferguson]

I am trying to import a CSV including the Issue Type field - the import appears to run with no errors, but all issues are imported as Stories, even though I have specified one as an Epic. Am I doing something incorrectly?

This used to work fine on older versions of cloud - but now doesn't work. The project type is next-gen - could this be affecting things?

Config File Field Mappings: 

"config.field.mappings" : {
 "Summary" : {
 "jira.field" : "summary",
 "userChanged" : "true",
 "manualMapping" : "false"
 },
 "Issue Type" : {
 "jira.field" : "issuetype",
 "userChanged" : "true",
 "manualMapping" : "false"
 },
 "Description" : {
 "jira.field" : "description",
 "userChanged" : "true",
 "manualMapping" : "false"
 }
 },

Log File

2019-01-02 12:11:38,232 INFO - ------------------------------
2019-01-02 12:11:38,239 INFO - Retrieving custom fields...
2019-01-02 12:11:38,247 INFO - ------------------------------
2019-01-02 12:11:38,247 INFO - Importing: Issues
2019-01-02 12:11:38,247 INFO - ------------------------------
2019-01-02 12:11:38,247 INFO - Only new items will be imported
2019-01-02 12:11:38,294 INFO - Importing issue: [externalId='autoid--275678961633451824', summary='Test epic for testing upload functionality']
2019-01-02 12:11:38,390 INFO - Importing issue: [externalId='autoid-2566635605164252712', summary='Test Story 1']
2019-01-02 12:11:38,462 INFO - 2 issues successfully created
2019-01-02 12:11:38,465 INFO - ------------------------------
2019-01-02 12:11:38,465 INFO - Finished Importing : Issues
2019-01-02 12:11:38,465 INFO - ------------------------------
2019-01-02 12:11:38,469 INFO - ------------------------------
2019-01-02 12:11:38,469 INFO - Importing: Issue Links & Subtasks
2019-01-02 12:11:38,469 INFO - ------------------------------
2019-01-02 12:11:38,469 INFO - Only new items will be imported
2019-01-02 12:11:38,472 INFO - ------------------------------
2019-01-02 12:11:38,472 INFO - Finished Importing : Issue Links & Subtasks
2019-01-02 12:11:38,472 INFO - ------------------------------

[Joao Arruda]

It seems there's a problem with "External System Import" for Next-gen projects.

You can vote in this bug to be solved: https://jira.atlassian.com/browse/JSWCLOUD-20625

Additionally, Jira suggests that you create a Classic project for importing the tasks and then migrate them to your Next-gen project.

I tested and it worked to import different Issue types to Classic projects, I must see now if it will work to migrate them as I wanted to.

[Huan Ting Chen]

Having the same problem. Anyone found a solution?

[Dave Hewlett]

I had this same problem.

I think the problem is with the "next-gen" project type because I was able to do the exact same import in a "classic" project and the Issue Type field would import correctly.

[Maurice W.]

I agree.

I think it is indeed a bug with the next-gen project type.

[RNV]

Try to remove the space in issueType,

"IssueType" : {
      "jira.field" : "issuetype"

[Maurice W.]

the space in the field name is correct. that's how the JIRA-generated config file exports it.