Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 19:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

JIRA don't send curtomer notification.

Kamil Pietrzak November 29, 2017 edited

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 ...

3 answers

0 votes
Nicat Nagiyev January 11, 2018

Thank you @Andy Heinzer! :)

0 votes
Andy Heinzer
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
January 11, 2018

@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.

0 votes
Nicat Nagiyev January 10, 2018

I discovered the same problems in our company...

Suggest an answer

Log in or Sign up to answer
TAGS
atlassian, atlassian community, journeys for jira service management, journeys for jsm, eap jsm atlassian, early access program atlassian, early access program journeys atlassian, early access program journeys jira service management, join atlassian eap

Join the Early Access Program (EAP) - Journeys for Jira Service Management 🚪

Journeys is a brand new feature in Jira Service Management that helps you streamline various processes in your organization that may cross multiple departments, such as employee onboarding or off-boarding that require action from different teams. ✨

Join the EAP →
AUG Leaders

Upcoming Jira Service Management Events