-
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
-
- Closed
-
- Closed
-
- Closed
- relates to
-
- Closed
-
- Closed
-
- Closed
-
- Closed
- Testing discovered
-
JSDSERVER-323 notification not working in version 1.2.0
-
- Closed
-
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSDSERVER-72] Disable Notifications per Project; Use JIRA's default notification rules and templates
| Workflow | Original: JAC Suggestion Workflow [ 3011700 ] | New: JAC Suggestion Workflow 3 [ 3649181 ] |
| Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
| Workflow | Original: Confluence Workflow - Public Facing v4 [ 2665023 ] | New: JAC Suggestion Workflow [ 3011700 ] |
| Workflow | Original: JSD Suggestion Workflow - TEMP [ 2322231 ] | New: Confluence Workflow - Public Facing v4 [ 2665023 ] |
| Status | Original: Closed [ 6 ] | New: Resolved [ 5 ] |
| Workflow | Original: JSD Suggestion Workflow [ 2052647 ] | New: JSD Suggestion Workflow - TEMP [ 2322231 ] |
| Workflow | Original: JSD Suggestion Workflow - TEMP [ 2048530 ] | New: JSD Suggestion Workflow [ 2052647 ] |
| Workflow | Original: JSD Suggestion Workflow [ 1280419 ] | New: JSD Suggestion Workflow - TEMP [ 2048530 ] |
Arg! The summary of this "Fixed" issue is completely misleading! There's no "per-project" ability to disable Service Desk notifications, it's either Globally On or Off.
Service Desk notification is idiot. We can't enter specific email to notify. We can notify by group. What are you guys doing? By not listen your client ?
| Description |
Original:
h3. 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. h3. 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|https://confluence.atlassian.com/jira/jira-admin-helper-376834956.html#JIRAAdminHelper-NotificationHelper]) for usability. h3. Workaround No Workaround at this time has been determined. |
New:
{panel:bgColor=#e7f4fa} *NOTE:* This suggestion is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JSDCLOUD-72]. {panel} h3. 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. h3. 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|https://confluence.atlassian.com/jira/jira-admin-helper-376834956.html#JIRAAdminHelper-NotificationHelper]) for usability. h3. Workaround No Workaround at this time has been determined. |
If using JSD 3.3.0 or newer, under your Project Settings, there is a tab Customer Notifications. From here it is possible to mark each of these notification rules as disabled.
If want your own notifications, they can be added manually as Automation rules, using the Send Email Then action.
If you would like to ensure that the JIRA notification scheme is used instead / as well, then the Global Setting is now used to determine whether to also send JIRA email or not. It is no longer one or the other, it is now only Service Desk Customer Emails or both Service Desk and JIRA emails (in regards to the global setting). As previously mentioned Service Desk emails can be disabled on a per project basis, by marking each unwanted default rule as disabled.