-
Suggestion
-
Resolution: Fixed
NOTE: This suggestion is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.
Problem Definition
The old Service Desk beta used to have the ability to disable notifications.
That configuration seems to be gone now. We'd need to disable it and not confuse users with two types of email notifications.
The notifications seem to be tied closely with the workflows statuses. It's very difficult to manage this. If you have 20 buttons, and suddenly you modify the Project's workflow, you'll now need to dive in to all 20, and re-key in the status mappings.
Suggested Solution
- An option to adhere to the global settings or have a per project configuration
- An option to set the configuration on a project level
- A Per Service Desk configuration option, to toggle specific Service Desk Notifications
- Tooling to help determine what specific notifications are configured (like the JIRa Notification Helper) for usability.
Workaround
No Workaround at this time has been determined.
- is duplicated by
-
JSDSERVER-971 Allow customization of the Service Desk notifications to customers
- Closed
-
JSDSERVER-1690 We would like to be able to administrate the number of notifications our users receive
- Closed
-
JSDSERVER-2284 Ability to toggle Service Desk notification scheme at the project level
- Closed
- relates to
-
JSDCLOUD-72 Disable Notifications per Project; Use JIRA's default notification rules and templates
- Closed
-
JSDSERVER-600 Request for instructions on how to set the notification settings in documentation
- Closed
-
JSDSERVER-894 Provide the ability for admin to control Service Desk notification for status change
- Closed
-
JSDSERVER-914 Service Desk Customer Not Treated as Reporter in JIRA Notification Scheme
- Closed
- Testing discovered
-
JSDSERVER-323 notification not working in version 1.2.0
- Closed