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

Mentioning users behaves differently between Jira and JSM

XMLWordPrintable

      Issue Summary

      Mentioning customers (Request Participants) behaves differently if we add the comment through Jira's view issue screen or JSM's request page.

      If we mention the user on Jira's screen, the "Mentioned" notification is not sent.
      If we mention the user on JSM's screen, the "Mentioned" notification is sent.

      Note: Mentioned notification refers to Jira's URLs so customer may be directed to a screen stating issue does not exist if the customer has Jira access but no access to that specific project.

      Steps to Reproduce

      1. Add customer as Request Participant
      2. Mention user (@username) on a comment through both screens

      Expected Results

      User should either receive the notification both times or not receive any of them.

      Actual Results

      User receives notification only if sent from JSM screen

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

            [JSDSERVER-8681] Mentioning users behaves differently between Jira and JSM

            Daniel Eads made changes -
            Labels New: cst
            Divyanshi made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Waiting for Release [ 12075 ] New: Closed [ 6 ]
            Alex Cooksey made changes -
            Assignee New: Anh Nguyen [ 26dfe8128d58 ]
            SET Analytics Bot made changes -
            UIS New: 23
            Bugfix Automation Bot made changes -
            Support reference count Original: 1 New: 2
            server-jirasync-bot made changes -
            Status Original: In Review [ 10051 ] New: Waiting for Release [ 12075 ]
            server-jirasync-bot made changes -
            Fix Version/s New: 4.20.0 [ 96191 ]
            server-jirasync-bot made changes -
            Status Original: In Progress [ 3 ] New: In Review [ 10051 ]
            server-jirasync-bot made changes -
            Status Original: Short Term Backlog [ 12074 ] New: In Progress [ 3 ]
            server-jirasync-bot made changes -
            Status Original: Needs Triage [ 10030 ] New: Short Term Backlog [ 12074 ]

              26dfe8128d58 Anh Nguyen
              malmeida Marcus Silveira
              Affected customers:
              1 This affects my team
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: