Details
-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
8.13.1
-
None
-
8.13
-
4
-
Severity 3 - Minor
-
0
-
Description
Issue Summary
When JRASERVER-64595 is encountered, the error message "Unexpected failure occurred. Importer will stop immediately. Data may be in an unstable state" is alarming:
Steps to Reproduce
- Test an External System Import using a CSV file
- Map a CSV field to a Jira field that has two contexts defined in the target project, for example Context A and Context B.
Expected Results
The error message indicates that the import failed because a custom field has more than one context, and lists the problematic custom field.
Actual Results
The below exception is thrown in the atlassian-jira.log file:
2021-05-28 17:23:50,425-0500 JiraTaskExecutionThread-9 ERROR admin 1043x1221x1 om8myi 0:0:0:0:0:0:0:1 /secure/admin/ImporterLogsPage%21import.jspa [c.a.j.p.i.i.importer.impl.AbstractDataImporter$1Thread[http-nio-48131-exec-14,5,main]] Unexpected failure occurred. Importer will stop immediately. Data may be in an unstable state java.lang.IllegalArgumentException: expected one element but was: <com.atlassian.jira.issue.fields.config.FieldConfigSchemeImpl@5fcbbee4, com.atlassian.jira.issue.fields.config.FieldConfigSchemeImpl@e859a2e4> at com.google.common.collect.Iterators.getOnlyElement(Iterators.java:316) at com.google.common.collect.Iterables.getOnlyElement(Iterables.java:254) at com.atlassian.jira.plugins.importer.imports.importer.impl.customfields.CustomFieldsUtil.associateCustomFieldWithIssueType(CustomFieldsUtil.java:272) at com.atlassian.jira.plugins.importer.imports.importer.impl.customfields.CustomFieldsUtil.makeSureCustomFieldIsApplicableForIssue(CustomFieldsUtil.java:153) at com.atlassian.jira.plugins.importer.imports.importer.impl.DefaultJiraDataImporter.importExternalCustomFields(DefaultJiraDataImporter.java:1264) at com.atlassian.jira.plugins.importer.imports.importer.impl.DefaultJiraDataImporter.createIssue(DefaultJiraDataImporter.java:911) 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:533) at com.atlassian.jira.task.TaskManagerImpl$TaskCallableDecorator.call(TaskManagerImpl.java:491) 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)
Workaround
There is no workaround to change the logging behavior.
