Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Getting an Error

Yannam_ Pavan _P__
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 5, 2026

When importing a CSV file containing bug tickets linked to stories (via parent/epic link), the validation completes successfully, but no items are actually imported.

I have done this before many times but this time it's throwing error

2026-02-05 18:33:49,472 INFO - Importer started!
2026-02-05 18:33:49,472 INFO - Engine is running in Import mode
2026-02-05 18:33:49,643 INFO - All issues will be imported to project: ADAS DAT 2.0 Issues (ADASDAT20)
2026-02-05 18:33:49,665 INFO - Creating issue: [externalId='autoid-572702486314479823', summary='Highway - ME Inaccurate Lane Line Detection Issues in Curves']
2026-02-05 18:33:49,945 ERROR - Fatal error during import: Cannot invoke "com.atlassian.jira.issue.Issue.getIssueType()" because "issue" is null

 

2 answers

0 votes
Marc -Devoteam-
Community Champion
February 5, 2026

Hi @Yannam_ Pavan _P__ 

It seems there is no column for issue type in your CSV, or there is but this isn ot mapped when importing the CSV

Yannam_ Pavan _P__
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 6, 2026

pic1.pngpic2.pngpic3.png

Yannam_ Pavan _P__
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 6, 2026

I've mapped all the columns correctly, but when I try to create issues manually in Jira Cloud, it shows 'Work Type' instead of 'Issue Type'. Importing my CSV file, there's no 'Work Type' field to map—only 'Issue Type'—so I have to map it to 'Issue Type', which causes issues during import. I have tried it with Issue type and Work type to map the field.

Yannam_ Pavan _P__
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 6, 2026
0 votes
Chris Rogers
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
February 5, 2026

Hi @Yannam_ Pavan _P__ 

 

Are you able to include a screenshot of how you have the columns mapped as part of the import and a screenshot of how the data is structured in the csv you're trying to import?

Jira can sometimes be finicky, depending on how the data is structured or if you have a hidden row/column somewhere.

Yannam_ Pavan _P__
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 6, 2026

pic1.pngpic2.pngpic3.png

Yannam_ Pavan _P__
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 6, 2026
Chris Rogers
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
February 6, 2026

@Yannam_ Pavan _P__ 

Try and see if you have an option for "Work type" that you're mapping Issue Type to:

2026-02-06_16-51-17.png

Atlassian has changed the terminology for issue type to work type, but in many cases, users create their own issue type field, which can make it a bit more confusing than it needs to be.

One other thing to check is that all rows in your import sheet have a valid issue/work type, so it doesn't try to create a work item under a type that doesn't exist.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
ENTERPRISE
TAGS
AUG Leaders

Atlassian Community Events