-
Bug
-
Resolution: Won't Fix
-
High
-
None
-
None
-
35
-
Severity 3 - Minor
-
265
Summary
- CSV Importer produces errors when checking the Map Field Value for the Issue Type field
Environment
- JIRA Cloud
Steps to Reproduce
- Create a CSV file defining values for the Issue Type field
- Access “External System Importer”
- Click on CSV
- Choose the Defined in CSV option
- Associate CSV values with Jira fields and check the Map Field Value option for the Issue Type field
- Click Next
Expected Results
- CSV import goes through without a hitch
Actual Results
The following error is triggered:
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 org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:262) at org.apache.velocity.runtime.parser.node.ASTReference.value(ASTReference.java:507) at org.apache.velocity.runtime.parser.node.ASTExpression.value(ASTExpression.java:71) at org.apache.velocity.runtime.parser.node.ASTSetDirective.render(ASTSetDirective.java:142) at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:72) at org.apache.velocity.runtime.parser.node.ASTElseIfStatement.render(ASTElseIfStatement.java:92) at org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:106) at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:72) at org.apache.velocity.runtime.directive.Foreach.performIteration(Foreach.java:393) at org.apache.velocity.runtime.directive.Foreach.render(Foreach.java:316) at org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:175) at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:72) at org.apache.velocity.runtime.directive.Foreach.performIteration(Foreach.java:393) at org.apache.velocity.runtime.directive.Foreach.render(Foreach.java:316) at org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:175) at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:72) at org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:87) at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:336) at org.apache.velocity.Template.merge(Template.java:328) at org.apache.velocity.Template.merge(Template.java:235) at org.apache.velocity.app.VelocityEngine.mergeTemplate(VelocityEngine.java:381) at com.atlassian.velocity.DefaultVelocityManager.writeEncodedBodyImpl(DefaultVelocityManager.java:117) at com.atlassian.velocity.DefaultVelocityManager.writeEncodedBody(DefaultVelocityManager.java:97) at com.atlassian.jira.template.velocity.DefaultVelocityTemplatingEngine$DefaultRenderRequest.toWriterImpl(DefaultVelocityTemplatingEngine.java:122) at com.atlassian.jira.template.velocity.DefaultVelocityTemplatingEngine$DefaultRenderRequest.asHtml(DefaultVelocityTemplatingEngine.java:113) at com.atlassian.jira.web.dispatcher.JiraVelocityViewDispatcher.dispatch(JiraVelocityViewDispatcher.java:50) at com.atlassian.jira.web.dispatcher.JiraWebworkViewDispatcher.dispatchViaVelocityView(JiraWebworkViewDispatcher.java:89) at com.atlassian.jira.web.dispatcher.JiraWebworkViewDispatcher.dispatchView(JiraWebworkViewDispatcher.java:56) at com.atlassian.jira.web.dispatcher.JiraWebworkActionDispatcher.service(JiraWebworkActionDispatcher.java:184) at javax.servlet.http.HttpServlet.service(HttpServlet.java:729) at com.atlassian.jira.servlet.WebExceptionCheckingServlet.delegate(WebExceptionCheckingServlet.java:86) at com.atlassian.jira.servlet.WebExceptionCheckingServlet.service(WebExceptionCheckingServlet.java:32) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:292) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207) at com.atlassian.jira.web.filters.JiraAbstractHttpFilter.lambda$doFilter$0(JiraAbstractHttpFilter.java:33) at com.atlassian.jira.web.filters.steps.ChainedFilterStepRunner.doFilter(ChainedFilterStepRunner.java:75) at com.atlassian.jira.web.filters.JiraAbstractHttpFilter.doFilter(JiraAbstractHttpFilter.java:38) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:240) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207) at
- Using issuetype.csv
as a test file, considering that the Service Desk Test project did not have a default issue type, the following outcomes were observed:
Option Map Field Value Option Has Default Issue Type Outcome Import to Project Unchecked No 
Works as expected 
Import to Project Checked No Works as expected Defined in CSV Unchecked No Works as expected Defined in CSV Checked No Error is returned Defined in CSV Checked Yes Works as expected *Work as expected if the issue type defined in the CSV file is mapped at the project, if it is not mapped, then it will fail
Workaround
- Use one of the options where the problem was not observed, as defined in the table above
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[MIG-392] CSV Importer produces errors when mapping the Issue Type field
Please reconsider fixing this bug. It is over 5 years old, and is one of our blockers migrating from server to cloud.
| Resolution | New: Won't Fix [ 2 ] | |
| Status | Original: Gathering Impact [ 12072 ] | New: Closed [ 6 ] |
Hi all,
Although we appreciate that this bug is not great in terms of User Experience, unfortunately it is unlikely that we will address it in the near future.
We are working on a new Importer for Jira (JWM, JSW, JSM, JPD) to solve many of the existing JIM bugs and provide a better experience while importing data.
We have already shipped it in JWM with more features to come soon: [!https://wac-cdn.atlassian.com/assets/img/favicons/atlassian/favicon.png!Import data from other tools into Jira Work Management | Jira Work Management Cloud | Atlassian Support|https://support.atlassian.com/jira-work-management/docs/import-data-from-other-tools-into-jira-work-management/] .
As a result, we decided to close this bug as Won't fix.
Follow the updates on our public roadmap [!https://www.atlassian.com/favicon-16x16.png!Cloud Roadmap | Atlassian|https://www.atlassian.com/wac/roadmap/cloud?selectedProduct=jiraWork;jsw;jiraService;jpd&] __
Thank you again for providing valuable feedback to our team!
Jira Cloud team
| UIS | Original: 264 | New: 265 |
| UIS | Original: 317 | New: 264 |
| UIS | Original: 369 | New: 317 |
| UIS | Original: 370 | New: 369 |
| UIS | Original: 316 | New: 370 |
Hello!
We’re looking to improve the import experience in Jira and are keen to understand how our community is using the Jira Import Module (JIM). If you’ve used JIM to migrate/move data into Jira recently, we’d love to hear about your experience. Please take a few minutes to fill out this survey. Your feedback will help us learn how we can improve your experience in importing data.
Survey link - https://forms.gle/NYNkmS92r96z42QV9
Thanks!
Prashanth M
Product Manager, Jira Platform