Hi,

I am encountering the following error when syncing Jira issues to Zendesk. The error I am receiving is below:

Impact:

Sync for remote ticket ITH-540 is blocked

Remote ticket:

ITH-540

Connection:

LRGJira_to_LRGITZendesk

Error Type:

Issue Tracker Error

Error Creation Time:

2020-04-23 23:17:15

Error Detail Message:

Bad response when creating issue - 422 {"error":"RecordInvalid","description":"Record validation errors","details":{"base":[{"description":"Description: cannot be blank","error":"BlankValue","ticket_field_id":26777977,"ticket_field_type":"FieldDescription"}]}}

Error Stack Trace

com.exalate.api.exception.IssueTrackerException: Bad response when creating issue - 422 {"error":"RecordInvalid","description":"Record validation errors","details":{"base":[{"description":"Description: cannot be blank","error":"BlankValue","ticket_field_id":26777977,"ticket_field_type":"FieldDescription"}]}} at services.node.client.ZendeskClient.services$node$client$ZendeskClient$$filterResponse(ZendeskClient.scala:599) at services.node.client.ZendeskClient$$anonfun$createIssue$1$$anonfun$apply$71$$anonfun$apply$72.apply(ZendeskClient.scala:415) at services.node.client.ZendeskClient$$anonfun$createIssue$1$$anonfun$apply$71$$anonfun$apply$72.apply(ZendeskClient.scala:415) at scala.concurrent.Future$$anonfun$flatMap$1.apply(Future.scala:253) at scala.concurrent.Future$$anonfun$flatMap$1.apply(Future.scala:251) at scala.concurrent.impl.CallbackRunnable.run(Promise.scala:32) at scala.concurrent.impl.ExecutionContextImpl$AdaptedForkJoinTask.exec(ExecutionContextImpl.scala:121) at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260) at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339) at scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979) at scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)

Any recommendations how I might be able to circumvent this error? I have tried by setting a description on the Jira issue and retrying the sync but the error persists.