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

No Notifications when Assignee = Reporter

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Answered
    • None
    • None
    • None
    • 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.

      Hi together,

      I would like to know if it is possible to get mail notifications when Reporter and Assignee are the same user? Atm I am just getting external comments as mail notification. Is there a way to get internals too?

      I already tried to configure "Own Changes" as "Notify me" but that does not solve the problem.

      Best,

      Adrien

          Form Name

            [JSDSERVER-5238] No Notifications when Assignee = Reporter

            Bartosz Ornatowski added a comment -

            Hi there,

            Thanks so much for your patience.

            We're sorry to hear you've been experiencing problems and have updated the Jira Service Desk documentation.

            You'll find the information you need here https://confluence.atlassian.com/jirakb/enabling-notifications-for-agents-acting-as-customers-987144325.html

            Thank you,

            The Jira Service Desk Team

            Bartosz Ornatowski added a comment - Hi there, Thanks so much for your patience. We're sorry to hear you've been experiencing problems and have updated the Jira Service Desk documentation. You'll find the information you need here https://confluence.atlassian.com/jirakb/enabling-notifications-for-agents-acting-as-customers-987144325.html Thank you, The Jira Service Desk Team

              bornatowski Bartosz Ornatowski
              4fc0125c8d95 Adrien Landecker
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: