-
Suggestion
-
Resolution: Low Engagement
-
None
-
None
Background and reason for this suggestion
Currently, JIRA Service Desk provides a history for incoming emails processed but it doesn't show the history of generated customer notifications.
Up until now, I have encountered two bugs which caused Service Desk customer notifications not going out. These were JRASERVER-64325 and JSDSERVER-5273.
To prevent them to happen I have created a non-JIRA dashboard which queries the database directly and shows me troublesome database entries. This is sufficient for issues I am aware of, but if any new type of problem occurs, I will not notice it until my customers report it to me.
The essence of this suggestion
I propose a _ new feature of _JIRA Service Desk customer notification audit, where admins could see the frequency of outgoing customer emails and maybe even, set alarm rules for situations when no customer notification is generated for the whole day.
If such alarms existed, any JIRA Service Desk manager would know about issues with customer emails after one day instead of three (or more).
- relates to
-
JRASERVER-64325 Jira fails to start due to duplicate job IDs in the clusteredjob table
- Closed
-
JSDSERVER-5273 Notifications that contain only an image will break SD notification job when using Oracle database
- Closed