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

Internal comments on agents view trigger workbox notification in Confluence

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a bug
    • Icon: Low Low
    • None
    • 4.5.4
    • Email - Outgoing
    • None

      Issue Summary

      Internal comments on agents view trigger workbox notification in Confluence and are causing security problems in customer environments

      Steps to Reproduce

      1. Have an application link setup configurated using OAuth with Confluence, in this case, v6.13.7
      2. Create two users with application access and browse project permission only in a Jira Service Desk project
      3. Create a new ticket
      4. Add them as watchers in a ticket from the agent view
      5. Add an internal comment from Jira service desk agent view
      6. Check workbox notification in confluence by logging in as those users
      7. Workbox notifications trigger in confluence from Jira only on 'Comments on issues that you are watching' our official documentation Which notifications are included? 

      Detailed replication steps are in this screen recording: Replication_Steps_JiraServiceDesk.mp4

      The same behavior is not replicable in Jira Software when adding restricted comments: Not_replicable_JiraSoftware.mp4

      Expected Results

      Internal comments should not be triggered as workbox notification in Confluence, should be handled in the same way as done in Jira Software

      Actual Results

      Internal comments are being triggered to customers as workbox notifications in Confluence, which are causing security problems in customer environments

      Workaround

      Refer to the heading 'Stopping Jira applications from sending notifications to Confluence' in this KB article Configuring Workbox Notifications 

              Unassigned Unassigned
              skattamuru@atlassian.com Sriteja Kattamuru (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: