incoming mail handler, Unable to create issue with message

sahere December 24, 2019

hi all,

I am trying to create issue in jira with incoming emails. the incoming email part of jira has been configured to create issue in a issue type. but, when i sent email, following forward email will be sent back to me:

An error was encountered whilst handling messages from the mail server "issues" using the handler "class com.atlassian.jira.plugins.mail.handlers.CreateIssueHandler".




The error was:

------------------------

"Unable to create issue with message."

Also, following message has been found in the atlassian-jira-incoming-mail.log:

 

2019-12-24 16:10:53,932 WARN [issues] Caesium-2-4 anonymous POPTEst POPTEst[10002]: Unable to create issue with message.
com.atlassian.jira.exception.CreateException: com.atlassian.jira.workflow.WorkflowException
at com.atlassian.jira.issue.managers.DefaultIssueManager.createIssue(DefaultIssueManager.java:519) [classes/:?]
at com.atlassian.jira.issue.managers.DefaultIssueManager.createIssueObject(DefaultIssueManager.java:608) [classes/:?]
at com.atlassian.jira.issue.managers.RequestCachingIssueManager.createIssueObject(RequestCachingIssueManager.java:209) [classes/:?]
at com.atlassian.jira.service.util.handler.DefaultMessageHandlerContext.createIssueWithIssueManager(DefaultMessageHandlerContext.java:248) [jira-api-7.12.3.jar:?]
at com.atlassian.jira.service.util.handler.DefaultMessageHandlerContext.createIssue(DefaultMessageHandlerContext.java:166) [jira-api-7.12.3.jar:?]
at com.atlassian.jira.service.services.mail.DelegatingMessageHandlerContext.createIssue(DelegatingMessageHandlerContext.java:43) [jira-api-7.12.3.jar:?]
at com.atlassian.jira.plugins.mail.handlers.CreateIssueHandler.handleMessage(CreateIssueHandler.java:266) [?:?]
at com.atlassian.jira.service.services.mail.MailFetcherService.processMessage(MailFetcherService.java:415) [jira-api-7.12.3.jar:?]
at com.atlassian.jira.service.services.mail.MailFetcherService$MessageProviderImpl.getAndProcessMail(MailFetcherService.java:272) [jira-api-7.12.3.jar:?]
at com.atlassian.jira.service.services.mail.MailFetcherService.processMessages(MailFetcherService.java:404) [jira-api-7.12.3.jar:?]
at com.atlassian.jira.service.services.mail.MailFetcherService.runImpl(MailFetcherService.java:396) [jira-api-7.12.3.jar:?]
at com.atlassian.jira.service.services.file.AbstractMessageHandlingService.run(AbstractMessageHandlingService.java:229) [jira-api-7.12.3.jar:?]
at com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:68) [classes/:?]
at com.atlassian.jira.service.ServiceRunner.runService(ServiceRunner.java:62) [classes/:?]
at com.atlassian.jira.service.ServiceRunner.runServiceId(ServiceRunner.java:44) [classes/:?]
at com.atlassian.jira.service.ServiceRunner.runJob(ServiceRunner.java:32) [classes/:?]
at com.atlassian.scheduler.core.JobLauncher.runJob(JobLauncher.java:153) [atlassian-scheduler-core-1.7.0.jar:?]
at com.atlassian.scheduler.core.JobLauncher.launchAndBuildResponse(JobLauncher.java:118) [atlassian-scheduler-core-1.7.0.jar:?]
at com.atlassian.scheduler.core.JobLauncher.launch(JobLauncher.java:97) [atlassian-scheduler-core-1.7.0.jar:?]
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.launchJob(CaesiumSchedulerService.java:443) [atlassian-scheduler-caesium-1.3.3.jar:?]
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeClusteredJob(CaesiumSchedulerService.java:438) [atlassian-scheduler-caesium-1.3.3.jar:?]
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeClusteredJobWithRecoveryGuard(CaesiumSchedulerService.java:462) [atlassian-scheduler-caesium-1.3.3.jar:?]
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeQueuedJob(CaesiumSchedulerService.java:390) [atlassian-scheduler-caesium-1.3.3.jar:?]
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService$1.consume(CaesiumSchedulerService.java:285) [atlassian-scheduler-caesium-1.3.3.jar:?]
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService$1.consume(CaesiumSchedulerService.java:282) [atlassian-scheduler-caesium-1.3.3.jar:?]
at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeJob(SchedulerQueueWorker.java:65) [atlassian-scheduler-caesium-1.3.3.jar:?]
at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeNextJob(SchedulerQueueWorker.java:59) [atlassian-scheduler-caesium-1.3.3.jar:?]
at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.run(SchedulerQueueWorker.java:34) [atlassian-scheduler-caesium-1.3.3.jar:?]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_111]
Caused by: com.atlassian.jira.workflow.WorkflowException
at com.atlassian.jira.workflow.OSWorkflowManager.createIssue(OSWorkflowManager.java:768) [classes/:?]
at com.atlassian.jira.issue.managers.DefaultIssueManager.createIssue(DefaultIssueManager.java:510) [classes/:?]
... 28 more
Caused by: java.lang.NullPointerException
at com.idalko.tgng.jira.server.models.duckets.grid.customfield.GridFieldType.$anonfun$upsertValue$2(GridFieldType.scala:100) [?:?]
at play.api.libs.json.JsSuccess.map(JsResult.scala:17) [?:?]
at com.idalko.tgng.jira.server.models.duckets.grid.customfield.GridFieldType.$anonfun$upsertValue$1(GridFieldType.scala:93) [?:?]
at scala.util.Either.map(Either.scala:350) [?:?]
at com.idalko.tgng.jira.server.models.duckets.grid.customfield.GridFieldType.upsertValue(GridFieldType.scala:90) [?:?]
at com.idalko.tgng.jira.server.models.duckets.grid.customfield.GridFieldType.createValue(GridFieldType.scala:72) [?:?]
at com.idalko.tgng.jira.server.models.duckets.grid.customfield.GridFieldType.createValue(GridFieldType.scala:42) [?:?]
at com.atlassian.jira.issue.fields.ImmutableCustomField.createValue(ImmutableCustomField.java:693) [classes/:?]
at com.atlassian.jira.workflow.function.issue.IssueCreateFunction.execute(IssueCreateFunction.java:81) [classes/:?]
at com.opensymphony.workflow.AbstractWorkflow.executeFunction(AbstractWorkflow.java:1014) [osworkflow-2.9.0-atlassian-1.jar:2.9.0-atlassian-1]
at com.opensymphony.workflow.AbstractWorkflow.transitionWorkflow(AbstractWorkflow.java:1407) [osworkflow-2.9.0-atlassian-1.jar:2.9.0-atlassian-1]
at com.opensymphony.workflow.AbstractWorkflow.initialize(AbstractWorkflow.java:606) [osworkflow-2.9.0-atlassian-1.jar:2.9.0-atlassian-1]
at com.atlassian.jira.workflow.OSWorkflowManager.createIssue(OSWorkflowManager.java:742) [classes/:?]
... 29 more

Could you please advise me about this? 

1 answer

0 votes
Cristiano Mariano
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.
January 1, 2020

Hi! How are you doing?

Looking at this part of the log, there are a few classes beginning with com.idalko.tgng. It looks like you are having an issue with the plugin Table Grid Next Generation (https://marketplace.atlassian.com/apps/1217571/table-grid-next-generation?hosting=cloud&tab=overview). Maybe it is related to some required field no being set.

Caused by: java.lang.NullPointerException
at com.idalko.tgng.jira.server.models.duckets.grid.customfield.GridFieldType.$anonfun$upsertValue$2(GridFieldType.scala:100) [?:?]
at play.api.libs.json.JsSuccess.map(JsResult.scala:17) [?:?]
at com.idalko.tgng.jira.server.models.duckets.grid.customfield.GridFieldType.$anonfun$upsertValue$1(GridFieldType.scala:93) [?:?]
at scala.util.Either.map(Either.scala:350) [?:?]
at com.idalko.tgng.jira.server.models.duckets.grid.customfield.GridFieldType.upsertValue(GridFieldType.scala:90) [?:?]

Hope this helps!

sahere January 4, 2020

Dear Cristiano,

Many thanks for your reply, there is no "Table Grid Next Generation" based custom field in the create screen and just there are common fields as summary, component, link issue , and so on. 

Regards

Like Cristiano Mariano likes this
Cristiano Mariano
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.
January 4, 2020

Hi @sahere 

I would check the Field Configuration, to make sure there is no field related to this app marked as required and also the Create transition in workflow, to make sure they are not being used in Validators or Post Functions.

Would you please check that and reply with your findings?

Thank you very much!

Suggest an answer

Log in or Sign up to answer