Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-72

Disable Notifications per Project; Use JIRA's default notification rules and templates

XMLWordPrintable

    • We collect Jira Service Desk feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      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.

            [JSDSERVER-72] Disable Notifications per Project; Use JIRA's default notification rules and templates

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3011700 ] New: JAC Suggestion Workflow 3 [ 3649181 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2665023 ] New: JAC Suggestion Workflow [ 3011700 ]
            Owen made changes -
            Workflow Original: JSD Suggestion Workflow - TEMP [ 2322231 ] New: Confluence Workflow - Public Facing v4 [ 2665023 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Suggestion Workflow [ 2052647 ] New: JSD Suggestion Workflow - TEMP [ 2322231 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Suggestion Workflow - TEMP [ 2048530 ] New: JSD Suggestion Workflow [ 2052647 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Suggestion Workflow [ 1280419 ] New: JSD Suggestion Workflow - TEMP [ 2048530 ]
            jonah (Inactive) made changes -
            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.
            jonah (Inactive) made changes -
            Link New: This issue relates to JSDCLOUD-72 [ JSDCLOUD-72 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels Original: affects-cloud sdt srl New: affects-cloud affects-server sdt srl
            Confluence Escalation Bot (Inactive) made changes -
            Labels Original: sdt srl New: affects-cloud sdt srl

              Unassigned Unassigned
              a38518e05741 David Yu
              Votes:
              52 Vote for this issue
              Watchers:
              53 Start watching this issue

                Created:
                Updated:
                Resolved: