Home > Jira Error > Jira Error Importing Issue Externalissue

Jira Error Importing Issue Externalissue

Not imported2012-12-06 13:25:27,582 INFO - ------------------------------2012-12-06 13:25:27,582 INFO - Importing: Versions2012-12-06 13:25:27,582 INFO - ------------------------------2012-12-06 13:25:27,582 INFO - Only new items will be imported2012-12-06 13:25:27,582 INFO - ------------------------------2012-12-06 13:25:27,582 INFO - I'm sure there is something not kosher with the import file but the error message is not providing me with information to help me narrow down my issue. For enumerated field types? Yes No Thanks for your feedback! have a peek here

at com.atlassian.jira.plugins.importer.imports.importer.impl.ExternalUtils.createIssue(ExternalUtils.java:172) at com.atlassian.jira.plugins.importer.imports.importer.impl.DefaultJiraDataImporter.createIssue(DefaultJiraDataImporter.java:848) at com.atlassian.jira.plugins.importer.imports.importer.impl.DefaultJiraDataImporter.importIssues(DefaultJiraDataImporter.java:762) at com.atlassian.jira.plugins.importer.imports.importer.impl.DefaultJiraDataImporter.doImport(DefaultJiraDataImporter.java:354) at com.atlassian.jira.plugins.importer.imports.importer.impl.ImporterCallable.call(ImporterCallable.java:27) at com.atlassian.jira.plugins.importer.imports.importer.impl.ImporterCallable.call(ImporterCallable.java:16) at com.atlassian.jira.task.TaskManagerImpl$TaskCallableDecorator.call(TaskManagerImpl.java:366) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at com.atlassian.multitenant.impl.DefaultMultiTenantManager.runForTenant(DefaultMultiTenantManager.java:61) at com.atlassian.multitenant.juc.MultiTenantExecutors$WrappedRunnable.run(MultiTenantExecutors.java:160) at com.atlassian.jira.task.ForkedThreadExecutor$ForkedRunnableDecorator.run(ForkedThreadExecutor.java:249) at at com.googlecode.jsu.util.ValidatorErrorsBuilder.process(ValidatorErrorsBuilder.java:50) at com.googlecode.jsu.workflow.validator.GenericValidator.validate(GenericValidator.java:75) at com.opensymphony.workflow.AbstractWorkflow.verifyInputs(AbstractWorkflow.java:1512) at com.opensymphony.workflow.AbstractWorkflow.transitionWorkflow(AbstractWorkflow.java:1203) at com.opensymphony.workflow.AbstractWorkflow.initialize(AbstractWorkflow.java:615) at com.atlassian.jira.workflow.OSWorkflowManager.createIssue(OSWorkflowManager.java:803) at com.atlassian.jira.issue.managers.DefaultIssueManager.createIssue(DefaultIssueManager.java:440) ... 33 more2012-12-06 13:25:27,613 INFO - 1 issues successfully created2012-12-06 13:25:27,613 INFO - ------------------------------2012-12-06 13:25:27,613 INFO - and map the issue types? Error importing issue ExternalIssue{externalId=autoid-2120182549912055863, summary=Test, issueType=null} Exception occurred parsing comment.

Select any issue type rather than 'None' from the Default Issue Type dropdown menu. but the data is present in the CSV file still the error is coming.. Voice Grid Picking dialogue changes.", issueType=7} com.atlassian.jira.plugins.importer.external.ExternalException: Unable to create issue: WAIBRA-143 at com.atlassian.jira.plugins.importer.external.ExternalUtils.createIssue(ExternalUtils.java:245) at com.atlassian.jira.plugins.importer.imports.importer.impl.DefaultJiraDataImporter.createIssue(DefaultJiraDataImporter.java:778) at com.atlassian.jira.plugins.importer.imports.importer.impl.DefaultJiraDataImporter.importIssues(DefaultJiraDataImporter.java:704) at com.atlassian.jira.plugins.importer.imports.importer.impl.DefaultJiraDataImporter.doImport(DefaultJiraDataImporter.java:302) at com.atlassian.jira.plugins.importer.imports.importer.impl.ImporterCallable.call(ImporterCallable.java:25) at com.atlassian.jira.plugins.importer.imports.importer.impl.ImporterCallable.call(ImporterCallable.java:14) at com.atlassian.jira.task.TaskManagerImpl$TaskCallableDecorator.call(TaskManagerImpl.java:359) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at Also have you applied the proper Issue Type Scheme to the project STTL.

My input file is as I have in the issue.CommentCommentAdd your comment...10-1Betsy WalkerJul 26, 2011The Summary field is a required field and it can't be empty even if the project to set in system profile). ? You might want to try reading the log file - that should tell you what it can't map and why. Only in Production showing the same below error.

Not imported 2014-05-07 11:16:32,886 INFO - ------------------------------ 2014-05-07 11:16:32,886 INFO - Importing: Versions 2014-05-07 11:16:32,886 INFO - ------------------------------ 2014-05-07 11:16:32,886 INFO - Only new items will be imported 2014-05-07 11:16:32,886 INFO After migration for few issue i am getting below error. Make sure that you tell it to expect 2-digit years, and it will properly fill in the century (according to the rules listed in http://docs.oracle.com/javase/6/docs/api/java/text/SimpleDateFormat.html .) Alternatively, make sure your CSV FYI: You may need to enclose the string in quotes if the string value could contain commas.CommentCommentAdd your comment...Sign up or log in to answerWatchRelated questions Powered by Atlassian Confluence 5.7.3,

CommentAdd your comment...10-1Renjith PillaiJan 19, 2013Also check this - https://confluence.atlassian.com/display/JIRAKB/Issue+Types+Missing+from+the+Default+Issue+Type+Scheme May be related. But, if your import is failing (you can see some red messages), then there is something else wrong with your import and it's not connected to the comment warning. Here's the logs. not text, numbers or dates)CommentCommentAdd your comment...10-1Wojciech SeligaJul 27, 2011Hi, Actually you probably faced this bug in JIRA Importers plugin.

Error : 03:56:17] ************************************************************** [03:56:17] IMPORTING STARTED[03:56:17] **************************************************************[03:56:17] Importing with ImportBeanType: com.atlassian.jira.plugins.importer.imports.csv.CsvDataBean[03:56:17] Skipped importing of Users[03:56:17] Retrieving projects... https://answers.atlassian.com/questions/116818/error-while-importing-from-csv That’s over 2,000 years ago. Report a bug Atlassian News Atlassian Skip to content Skip to breadcrumbs Skip to header menu Skip to action menu Skip to quick search Linked ApplicationsLoading… Quick Search Help About Confluence Para 1.1.3.,Requirements,MajorjiraimportcsvCommentNavneet SohalJul 09, 2015Import completed with 3 errors:Error importing issue ExternalIssue{externalId=autoid-1095801192875015355, summary=Trip View - Add Location, issueType=10100}Error importing issue ExternalIssue{externalId=autoid-7804890968372533742, summary=List Locations, issueType=4}Error importing issue ExternalIssue{externalId=autoid-3783287243605814551, summary=Text Updates for Modal

at com.atlassian.jira.workflow.OSWorkflowManager.createIssue(OSWorkflowManager.java:846) at com.atlassian.jira.issue.managers.DefaultIssueManager.createIssue(DefaultIssueManager.java:402) ... 32 more Caused by: com.atlassian.jira.exception.DataAccessException: Error occurred while storing issue. http://ascadys.net/jira-error/jira-error-creating-issue-source-generic-value-cannot-be-null.html Para 1.1.2.,Requirements,MajorThe system shall provide the capability to review existing pictures,1.1.3,2. Report a bug Atlassian News Atlassian Skip to content Skip to breadcrumbs Skip to header menu Skip to action menu Skip to quick search Linked ApplicationsLoading… Quick Search Help About Confluence Para 1.1.1.,Requirements,MajorThe system shall provide the capability to take and store multiple pictures,1.1.2,2.

Skip to content Skip to breadcrumbs Skip to header menu Skip to action menu Skip to quick search Linked ApplicationsLoading… Quick Search Help About Confluence Log in Sign up QuestionsTopicsLeaderboardRewardsUnable As per Ivan Tse [Atlassian], this should be resolved by https://jira.atlassian.com/browse/JRA-25967CommentCommentAdd your comment...Sign up or log in to answerWatchRelated questions Powered by Atlassian Confluence 5.7.3, Team Collaboration Software Printed by Atlassian I did as you said, quote my summary field, and it's still giving me the same error. http://ascadys.net/jira-error/jira-error-creating-issue-null.html All functionality to be wrapped in a new function access This change is being engineered ahead of the rest of the customisations to allow the user to trial voice picking to

last four digits)Pick 2 2 ? naama levDec 18, 2014Thanks Naamanaama levDec 18, 2014Hi Nic, Can you please let me know - Users cannot import issues from csv and map it to issue types? When should the box be checked?

That’s why the importer is complaining that “Only dates between January 1, 1753 and December 31, 9999 are accepted.” It looks like your CSV file is exporting 2-digit years, while the

Not imported 2014-05-07 11:16:32,885 INFO - ------------------------------ 2014-05-07 11:16:32,885 INFO - Importing: Versions 2014-05-07 11:16:32,885 INFO - ------------------------------ 2014-05-07 11:16:32,885 INFO - Only new items will be imported 2014-05-07 11:16:32,885 INFO Report a bug Atlassian News Atlassian Skip to content Skip to breadcrumbs Skip to header menu Skip to action menu Skip to quick search Linked ApplicationsLoading… Quick Search Help About Confluence You say that the map box should be checked only when trying to populate select field types. I am having the same problem here.

jira-administrationjiraimportCommentCommentAdd your comment...2 answers210Przemyslaw BorkowskiMay 06, 2014Hi Nayan, We had a similar bug reported ( https://ecosystem.atlassian.net/browse/JIM-919) - JIM coudn't create an issue if validator was configured to check mandatory Custom Fields. I'm not importing many issues with too many columns ( 3 issues and 5 fields/columns). It seems that importer is trying to interpret your comment as the second type. this contact form I've mapped the fields to the JIRA fields and when I begin the import, JIRA produces the following msg: 2011-07-26 09:19:34,447 WARN - Issue ExternalIssue{summary=null, issueType=12} has a blank summary.

Can you check that you have more than one issue type in the project, and that the column you are trying to map is complete - no blank lines in it I'm attempting to import a CSV file into an existing project. CommentAdd your comment...10-1Nic Brough [Adaptavist]May 06, 2014You have put a validator on the "create issue" transition in your workflow, which says "field must be filled in" (this is actually unneccessary, you If you are not using this format - please just ignore this warning as your comment is then treated as Plain-text and created correctly.