We believe a recent change to Jira Cloud https://ecosystem.atlassian.net/browse/ACJIRA-1152 has impacted JEMHC's ability to update some issues and generate related notifications.
Historically, JEMHC gained required access to projects through the atlassian-addons-project-access role, but as of 20th Dec appear no longer to be the case. The result of this is that JEMHC 'event' data is very limited, effectively stopping JEMHC having enough data to generate notifications from.
Workaround
If this impacts your instance, a workaround we have tested is to directly add the JEMHCloud user into each Issue Security Level.
Further Updates
For further updates on this issue, please monitor our live status page: http://status.thepluginpeople.com/
What we are doing about this
We have identified the root cause and are working on a solution, which will be rolled out as soon as possible.
We've been advised that our database will be upgraded soon:
We are contacting you to inform you that one or more of your Amazon RDS DB instances is scheduled to receive system upgrades during one of your maintenance windows between December 13 2017 4:00 PM PST and January 3 2018 4:00 PM PST.
Multi-AZ DB instances will be unavailable for the amount of time it takes a fail-over to complete, usually about 60 seconds, also in your maintenance window.
Our db maintenance window is: mon:05:00-mon:05:30 UTC (GMT)
Impact
As and when the maintenance kicks in JEMHC will be unable to store event data for about a minute, whilst the Database is transitioned from primary to backup, and later back. Its possible there could be some duplicate issue creation in this 60S period, given the time and historic data volumes we expect impact to be low.