After update to 3.9.0 Jira stopped sending some notifications to reporters.
For example don't send notification after issue resolved. Only thing i found in logs is this:
2017-11-29 14:04:50,775 http-nio-8080-exec-7 INFO kamil 844x3664x1 vvojge 172.20.7.1,127.0.0.1 /secure/CommentAssignIssue.jspa [c.a.j.p.h.s.task.impl.SendNotificationTask] Found 1 messages to send to HipChat
2017-11-29 14:04:50,791 http-nio-8080-exec-7 WARN kamil 844x3664x1 vvojge 172.20.7.1,127.0.0.1 /secure/CommentAssignIssue.jspa [c.a.s.p.b.internal.events.ServiceDeskOnCompletionExpectationManagerImpl] Inconsistent Cache state, as object returned event 'com.atlassian.jira.event.issue.IssueEvent@6588c7f5[issue=CS-2473,comment=<null>,worklog=<null>,changelog=[GenericEntity:ChangeGroup][id,40529][issue,22001][author,admin][created,2017-11-29 14:04:50.746],eventTypeId=13,sendMail=true,params={eventsource=workflow, baseurl=https://jira.local},subtasksUpdated=false]' but expecting 'IssueChangedEventImpl{changeItems=[com.atlassian.jira.issue.history.ChangeItemBean@178b7ad6[fieldType=jira,field=status,from=5,fromString=Resolved,to=10300,toString=Waiting for support,created=2017-11-29 14:04:50.746], com.atlassian.jira.issue.history.ChangeItemBean@40189122[fieldType=jira,field=resolution,from=1,fromString=Fixed,to=<null>,toString=<null>,created=2017-11-29 14:04:50.746]], author=Optional[kamil(admin)], comment=Optional.empty, issue=CS-2473, eventTime=Wed Nov 29 14:04:50 UTC 2017, sendMail=true}'
2017-11-29 14:04:50,813 http-nio-8080-exec-7 WARN kamil 844x3664x1 vvojge 172.20.7.1,127.0.0.1 /secure/CommentAssignIssue.jspa [c.a.s.p.b.internal.events.ServiceDeskOnCompletionExpectationManagerImpl] Inconsistent Cache state, as object returned event 'com.atlassian.jira.event.issue.IssueEvent@6588c7f5[issue=CS-2473,comment=<null>,worklog=<null>,changelog=[GenericEntity:ChangeGroup][id,40529][issue,22001][author,admin][created,2017-11-29 14:04:50.746],eventTypeId=13,sendMail=true,params={eventsource=workflow, baseurl=https://jira.local},subtasksUpdated=false]' but expecting 'IssueChangedEventImpl{changeItems=[com.atlassian.jira.issue.history.ChangeItemBean@410d5ee3[fieldType=jira,field=status,from=5,fromString=Resolved,to=10300,toString=Waiting for support,created=2017-11-29 14:04:50.746], com.atlassian.jira.issue.history.ChangeItemBean@5fc94596[fieldType=jira,field=resolution,from=1,fromString=Fixed,to=<null>,toString=<null>,created=2017-11-29 14:04:50.746]], author=Optional[kamil(admin)], comment=Optional.empty, issue=CS-2473, eventTime=Wed Nov 29 14:04:50 UTC 2017, sendMail=true}'
2017-11-29 14:04:50,835 http-nio-8080-exec-7 WARN kamil 844x3664x1 vvojge 172.20.7.1,127.0.0.1 /secure/CommentAssignIssue.jspa [c.a.s.p.b.internal.events.ServiceDeskOnCompletionExpectationManagerImpl] Inconsistent Cache state, as object returned event 'com.atlassian.jira.event.issue.IssueEvent@6588c7f5[issue=CS-2473,comment=<null>,worklog=<null>,changelog=[GenericEntity:ChangeGroup][id,40529][issue,22001][author,admin][created,2017-11-29 14:04:50.746],eventTypeId=13,sendMail=true,params={eventsource=workflow, baseurl=https://jira.local},subtasksUpdated=false]' but expecting 'IssueChangedEventImpl{changeItems=[com.atlassian.jira.issue.history.ChangeItemBean@5fb0f249[fieldType=jira,field=status,from=5,fromString=Resolved,to=10300,toString=Waiting for support,created=2017-11-29 14:04:50.746], com.atlassian.jira.issue.history.ChangeItemBean@b546bad[fieldType=jira,field=resolution,from=1,fromString=Fixed,to=<null>,toString=<null>,created=2017-11-29 14:04:50.746]], author=Optional[kamil(admin)], comment=Optional.empty, issue=CS-2473, eventTime=Wed Nov 29 14:04:50 UTC 2017, sendMail=true}'
But i don't know what to do ...
@Nicat NagiyevThis was a known bug in that version. More details on this can be found in https://jira.atlassian.com/browse/JSDSERVER-5535
I would recommend upgrading Service Desk to 3.9.2 in order to fix this.
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.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.