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

Cannot activate customized notification scheme for JIRA Service Desk

    • Icon: Bug Bug
    • Resolution: Handled by Support
    • Icon: Low Low
    • None
    • None
    • Email - Outgoing

      NOTE: This bug report is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding bug report.

      I need to significantly dicrease a number of JSD notification. But when I disable notification setting for JIRA Service desk, my custom JIRA notification scheme does NOT take effect. I followed this article: https://confluence.atlassian.com/display/Cloud/Configuring+JIRA+Service+Desk+notifications
      According to it, my notification scheme must be used after I turn off JSD's one.
      I have found the similar issue descrideb here: https://answers.atlassian.com/questions/12261159/fewer-service-desk-notifications
      PLease help!

            [JSDSERVER-1644] Cannot activate customized notification scheme for JIRA Service Desk

            Owen made changes -
            Workflow Original: JSD Bug Workflow v5 - TEMP [ 2305365 ] New: JAC Bug Workflow v3 [ 3125808 ]
            Status Original: Done [ 10044 ] New: Closed [ 6 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v5 [ 2059319 ] New: JSD Bug Workflow v5 - TEMP [ 2305365 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v5 - TEMP [ 2056739 ] New: JSD Bug Workflow v5 [ 2059319 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v5 [ 1956515 ] New: JSD Bug Workflow v5 - TEMP [ 2056739 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v4 [ 1616180 ] New: JSD Bug Workflow v5 [ 1956515 ]
            jonah (Inactive) made changes -
            Description Original: I need to significantly dicrease a number of JSD notification. But when I disable notification setting for JIRA Service desk, my custom JIRA notification scheme does NOT take effect. I followed this article: https://confluence.atlassian.com/display/Cloud/Configuring+JIRA+Service+Desk+notifications
            According to it, my notification scheme must be used after I turn off JSD's one.
            I have found the similar issue descrideb here: https://answers.atlassian.com/questions/12261159/fewer-service-desk-notifications
            PLease help!
            New: {panel:bgColor=#e7f4fa}
              *NOTE:* This bug report is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/JSDCLOUD-1644].
              {panel}

            I need to significantly dicrease a number of JSD notification. But when I disable notification setting for JIRA Service desk, my custom JIRA notification scheme does NOT take effect. I followed this article: https://confluence.atlassian.com/display/Cloud/Configuring+JIRA+Service+Desk+notifications
            According to it, my notification scheme must be used after I turn off JSD's one.
            I have found the similar issue descrideb here: https://answers.atlassian.com/questions/12261159/fewer-service-desk-notifications
            PLease help!
            jonah (Inactive) made changes -
            Link New: This issue relates to JSDCLOUD-1644 [ JSDCLOUD-1644 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v2 [ 1603386 ] New: JSD Bug Workflow v4 [ 1616180 ]
            Owen made changes -
            Workflow Original: JSD Bug Workflow [ 1399360 ] New: JSD Bug Workflow v2 [ 1603386 ]
            Owen Sanico [Administrative Account] made changes -
            Workflow Original: TTT: Simple Issue Tracking Workflow [ 841169 ] New: JSD Bug Workflow [ 1399360 ]

              Unassigned Unassigned
              279b0120329f Vladimir Sagan
              Affected customers:
              2 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: