Hi,
I'm trying to use Codebarrels Automation for Jira with Jira Service Desk and seem to always get an error. It did work previously, but I don't know what changed to make it stop working.
I created a simple rule with "When: Issue Created" and a condition of if "request-channel-type = email" seems to not work anymore. The audit log shows:
ISSUE EVENT
Issue event trigger could not retrieve this issue for further processing:
UNKNOWN
The log shows: (I replaced some info with ***)
2018-03-14 19:50:08,716 automation-rule-executor:thread-1 WARN ***@*** [c.c.a.a.event.enrich.LazyLoadableEventEnricher] Unable to lazy load issue with key ***
2018-03-14 19:50:08,787 automation-rule-executor:thread-1 WARN admin [c.c.a.r.j.trigger.event.IssueEventTriggerExecutor] Unable to get the issue from event payload: {"timestamp":1521057008529,"webhookEvent":"jira:issue_created","comment":null,"issue":null,"user":{"self":null,"name":"***@***","key":"***@***","emailAddress":"***@j***","avatarUrls":{"48x48":"https://www.gravatar.com/avatar/6aedeaf52926502fb764837c74ffab97?d=mm&s=48","24x24":"https://www.gravatar.com/avatar/6aedeaf52926502fb764837c74ffab97?d=mm&s=24","16x16":"https://www.gravatar.com/avatar/6aedeaf52926502fb764837c74ffab97?d=mm&s=16","32x32":"https://www.gravatar.com/avatar/6aedeaf52926502fb764837c74ffab97?d=mm&s=32"},"displayName":"*** ***","active":true,"timeZone":"America/Los_Angeles","groups":{"size":0,"items":[]},"locale":"en_US"},"changelog":null,"issueIdentity":{"id":10300,"key":"***","updated":1521057007717},"issue_event_type_name":"issue_created"}
As you can see it says: "Unable to get the issue from event payload"
Anybody know where the problem may be?
Thanks
Hi Denis,
Sorry about that, we had a temporary issue and have released a fix already. If you upgrade to the latest version the issue should be resolved.
If your still having issues please contact us at support:
https://codebarrel.atlassian.net/servicedesk/customer/portal/1/create/3
Thanks,
Scott
Thanks Scott. I noticed the update release yesterday as well and after install, the issue was fixed.
Cheers
Denis
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.