nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Importing CSV causes error

John Di Ciurcio

When user attempts to import a CSV file the following error is displayed:

An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug. Details: ------- org.apache.velocity.exception.MethodInvocationException: Invocation of method 'getIssueTypes' in class com.atlassian.jira.plugins.importer.imports.csv.web.CsvValueMappingsPage threw exception java.lang.NullPointerException at com.atlassian.jira.plugins.jim-plugin:actions//templates/admin/views/csv/csvValueMappingsPage.vm[line 101, column 51] at org.apache.velocity.runtime.parser.node.ASTIdentifier.execute(ASTIdentifier.java:223) at

Any ideas? Thanks.

Accepted answers

All comments

Mark Sanders_exjel4

I'm facing the very same issue right now. Did you find a solution?

Matheus Fernandes

Hi, @Mark Sanders / @John Di Ciurcio

It looks like you are hitting into a bug in Jira when mapping the Issue Type field during the CSV import: JRACLOUD-68491. As a workaround please try removing the issue type from the mapping option. Alternatively, you can try importing the CSV using the Import to Jira Project option rather than mapping the project in the CSV (this should also work, we'll test this option and update the bug report accordingly if it does).

Cheers!

Katie_c5sui3

This bug ha not been fixed. Facing the same issue now.

Ben Hunnicutt

Facing the same issue now. Bug not fixed.

Ben Hunnicutt

I selected the "JIRA Field" (Issue Type to Issue Type) but did not check the "Map Field Value" I was updating start and due dates. This worked for me.

Kevin Delord

I am having this issue as well. The CSV importer gives a warning if no issue type is given.

Omar Sood

Any news on this one? The issue type mapping renderer is still broken

Omar Sood

Is there any way to exclude entries from the import then, when importing to a specific project? To split multi project import is quite laborious.

Murugan Mittapalli_djben3

I am having the same issue, getting an error when I map the issue type field.

Thank you.

Jose_Ramirez

Affected by this as well.

Austin Powell

I too have encountered this bug. Still no solution after 2 years?

Yash Doshi_376rox

Still waiting for a resolution

Tabbish Noorani

Hi guys. Try to change the name of the issue type and revert it back. This resolves the issue.

Tabbish Noorani

Hi @Yash Doshi. Try to change the name of the issue type and revert it back.

Hector Eduardo Calzada Tenorio

The problem is with the language in the Issues. I had a task Issue Type in two languages and when importing that was the error because it updated from task to tarea (in spanish)

Work on homologating your Issues from your workflows so that they do not have this error or do not select the Issue Type of incident in "Map Field Value"

Jim Edgeton_on1yyh

Hi @Tabbish Noorani can you provide more specifics to this workaround?

Johan Hultberg

More than 5 years has passed and I still have this problem

Yatish Madhav

Thanks all ... Unchecking "Map Field Value" worked for me

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira