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

customer comment remain internal if edited by an agent from the internal portal and then shared again to the customer

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: High High
    • None
    • 4.8.1
    • Customer Portal

      Issue Summary

      customer comment remain internal if edited by an agent from the internal portal and then shared again to the customer.

      The bug is reproducible in both JSD 4.6.1 and 4.8.1

      Steps to Reproduce

      1. While logged with an agent user, browse an issue from the internal portal edit a comment added by the customer on the customer portal
      2. Clic on Share with customer button
      3. Observe that the comment remain Internal and it is not visible on the Customer portal anymore:

      Expected Results

      the comment should be again shared with the customer

      Actual Results

      the comment is instead internal like when we clic on Add to issue only

      Workaround

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

          Form Name

            [JSDSERVER-6833] customer comment remain internal if edited by an agent from the internal portal and then shared again to the customer

            According to the release notes, this bug is fixed in Jira 4.9, but the fix version field for this bug is empty. Secondly, will this fix be included in the next JSD 4.5 Enterprise bugfix release?

            Rick van Twillert (TMC) added a comment - According to the release notes, this bug is fixed in Jira 4.9, but the fix version field for this bug is empty. Secondly, will this fix be included in the next JSD 4.5 Enterprise bugfix release?

              Unassigned Unassigned
              tmarchionni@atlassian.com Tiziana Marchionni
              Affected customers:
              0 This affects my team
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: