Forums
Home Product Q&A Discussion groups Articles Ask a question Search
Learning
Events
Champions

Forums

Articles
Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Product Q&A
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Events
Community resources

Why am I getting errors when importing issues via Admin CSV?

Todd Palermo
Todd Palermo
Contributor
March 20, 2020

I need some help tracking down my problem. I get errors when importing issues via CSV and it seems to only happen on new Created issues. Updating issues never seem to create an error. Additionally, when I import issues, I assign a KEY instead of letting Jira pick one for me. It is like Jira is telling me I can't update an issue because that issue doesn't exist. When I check Jira, all issues imported correctly and as expected, but the after import error and log disagrees. If I run the same import back to back, the second time I always get zero errors. I need to have zero errors the first time so that these errors will not confuse other members when importing and so real errors don't get overlooked.  Any ideas with the log?

Here is one problem:

2020-03-20 06:42:25,036 ERROR - Error importing issue [externalId='autoid-4131920644414190394', summary='CLA(PE) plate length reduced to avoid poping noise']
com.atlassian.jira.plugins.importer.external.ExternalException: Unable to create issue: com.atlassian.jira.plugins.importer.compatibility.FixedKeyMutableIssue70@1e35f33f
at com.atlassian.jira.plugins.importer.imports.importer.impl.ExternalUtils.createIssue(ExternalUtils.java:210)
at com.atlassian.jira.plugins.importer.imports.importer.impl.DefaultJiraDataImporter.createIssue(DefaultJiraDataImporter.java:914)
at com.atlassian.jira.plugins.importer.imports.importer.impl.DefaultJiraDataImporter.importIssues(DefaultJiraDataImporter.java:798)
at com.atlassian.jira.plugins.importer.imports.importer.impl.DefaultJiraDataImporter.doImport(DefaultJiraDataImporter.java:414)
at com.atlassian.jira.plugins.importer.imports.importer.impl.ImporterCallable.call(ImporterCallable.java:26)
at com.atlassian.jira.plugins.importer.imports.importer.impl.ImporterCallable.call(ImporterCallable.java:15)
at com.atlassian.jira.task.TaskManagerImpl$TaskCallableDecorator.call(TaskManagerImpl.java:537)
at com.atlassian.jira.task.TaskManagerImpl$TaskCallableDecorator.call(TaskManagerImpl.java:495)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at com.atlassian.jira.task.ForkedThreadExecutor$ForkedRunnableDecorator.run(ForkedThreadExecutor.java:216)
at java.lang.Thread.run(Thread.java:748)
Caused by: com.atlassian.jira.exception.CreateException: com.atlassian.jira.workflow.WorkflowException: Error occurred while creating issue. This could be due to a plugin being incompatible with this version of JIRA. For more details please consult the logs, and see: http://confluence.atlassian.com/x/3McB
at com.atlassian.jira.issue.managers.DefaultIssueManager.createIssue(DefaultIssueManager.java:522)
at com.atlassian.jira.issue.managers.RequestCachingIssueManager.createIssue(RequestCachingIssueManager.java:207)
at sun.reflect.GeneratedMethodAccessor2080.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.atlassian.plugin.util.ContextClassLoaderSettingInvocationHandler.invoke(ContextClassLoaderSettingInvocationHandler.java:26)
at com.sun.proxy.$Proxy591.createIssue(Unknown Source)
at sun.reflect.GeneratedMethodAccessor2080.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:343)
at org.eclipse.gemini.blueprint.service.importer.support.internal.aop.ServiceInvoker.doInvoke(ServiceInvoker.java:56)
at org.eclipse.gemini.blueprint.service.importer.support.internal.aop.ServiceInvoker.invoke(ServiceInvoker.java:60)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:185)
at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:136)
at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:124)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:185)
at org.eclipse.gemini.blueprint.service.util.internal.aop.ServiceTCCLInterceptor.invokeUnprivileged(ServiceTCCLInterceptor.java:70)
at org.eclipse.gemini.blueprint.service.util.internal.aop.ServiceTCCLInterceptor.invoke(ServiceTCCLInterceptor.java:53)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:185)
at org.eclipse.gemini.blueprint.service.importer.support.LocalBundleContextAdvice.invoke(LocalBundleContextAdvice.java:57)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:185)
at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:136)
at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:124)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:185)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:212)
at com.sun.proxy.$Proxy1339.createIssue(Unknown Source)
at com.atlassian.jira.plugins.importer.compatibility.CompatibilityUtil71.createIssue(CompatibilityUtil71.java:231)
at com.atlassian.jira.plugins.importer.compatibility.CompatibilityBridgeUtils.createIssue(CompatibilityBridgeUtils.java:113)
at com.atlassian.jira.plugins.importer.imports.importer.impl.ExternalUtils.createIssue(ExternalUtils.java:202)
... 12 more
Caused by: com.atlassian.jira.workflow.WorkflowException: Error occurred while creating issue. This could be due to a plugin being incompatible with this version of JIRA. For more details please consult the logs, and see: http://confluence.atlassian.com/x/3McB
at com.atlassian.jira.workflow.OSWorkflowManager.createIssue(OSWorkflowManager.java:778)
at com.atlassian.jira.issue.managers.DefaultIssueManager.createIssue(DefaultIssueManager.java:513)
... 41 more
Caused by: java.lang.ClassCastException: com.atlassian.jira.plugins.importer.compatibility.FixedKeyMutableIssue70 cannot be cast to com.atlassian.jira.issue.IssueImpl
at com.akelesconsulting.jira.plugins.jira.workflow.LookupPostFunction.getFieldValue(LookupPostFunction.java:135)
at com.akelesconsulting.jira.plugins.jira.workflow.LookupPostFunction.execute(LookupPostFunction.java:373)
at com.opensymphony.workflow.AbstractWorkflow.executeFunction(AbstractWorkflow.java:1014)
at com.opensymphony.workflow.AbstractWorkflow.transitionWorkflow(AbstractWorkflow.java:1407)
at com.opensymphony.workflow.AbstractWorkflow.initialize(AbstractWorkflow.java:606)
at com.atlassian.jira.workflow.OSWorkflowManager.createIssue(OSWorkflowManager.java:754)
... 42 more

Answer
Watch
Like Be the first to like this
2219 views

2 answers

1 accepted

0 votes
Answer accepted
Todd Palermo
Todd Palermo
Contributor
July 26, 2020

This problem was caused by Lookup Manager plugin that was failing during import. I contacted Lookup manager and they were great and had a major revision of their plugin to correct this issue. Thanks Akeles Consulting!

Reply
0 votes
Andrew Laden
Andrew Laden
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 Leaders.
Get recognized
March 23, 2020

I don't think you can tell the importer to create an issue at a particular key. You can't do that from the gui etc, so I don't think you can do it otherwise.  (Other then database hacks) there isnt really a way to tell jira to "skip" a number when creating a new issue.

If you specify a key in the csv file it tries to update that issue.

I would guess what is happening is that it fails to create a new issue at the key you specified, then creates a new issue at the next possible key, which is probably the one you listed, and then the rest works ok because the issues now exist.

Just a guess on my part,

View More Comments
Todd Palermo
Todd Palermo
Contributor
March 23, 2020

Hi Andrew,

Thanks for looking at this. I am creating new issues by specifying a KEY without any hackary. In fact, this import is working as expected; the KEY that I specify is being created and the issue is being "updated"/created, but Jira gives me an error on import, even though there really isn't an error on my data. Is it possible that the Jira importer is not expecting this and throws an error, but only because it isn't programmed to expect a Key creation? Is there a way to get Atlassian to inspect this problem and correct their importer? This is a daily function for us and it would be better to not have a false positive error every day to inspect.

Like
Andrew Laden
Andrew Laden
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 Leaders.
Get recognized
March 23, 2020

Why do you need to specify the key? Why not just let jira use the next available key?

You can open a ticket with Atlassian support. But Given their backlog of support items, I would not expect fast action on it.

Like
Todd Palermo
Todd Palermo
Contributor
March 23, 2020

We are importing problems from another database where we use Jira to track and resolve the problem. We need a way to update the Jira problem with the updated problem from another database. We need to match KEYs between the two.

OK, I will open a ticket. We can wait to get this fixed because it currently works, but we are just getting false positive errors on all created imported records.

Thanks for your support!

Like
Todd Palermo
Todd Palermo
Contributor
April 12, 2020

As a follow up, I have requested that Akeles, the author of Lookup Manager plugin, look into this error. They have confirmed that this is a bug and ranked it a Major problem. Please see the following for details: https://akeles.jira.com/browse/LOOKUP-42

Like
Reply

Suggest an answer

Log in or Sign up to answer
Jira
Jira
DEPLOYMENT TYPE
SERVER
VERSION
8.5.3
TAGS
AUG Leaders

Atlassian Community Events

    See all events
    Community
    Forums
    FAQs Forums guidelines
    Learning
    About learning Resources
    Events
    Champions
    Copyright © 2025 Atlassian
    Privacy Policy Terms Security
    Welcome illustration

    Welcome to the new Atlassian Community

    Online forums and learning are now in one easy-to-use experience.

    By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.