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

Comments added to issues by addons are listed as internal by default

XMLWordPrintable

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

      Summary

      JSD should not consider comments without the sd.public.comment attribute as internal comments, but as public comments. Only comments with the entity property set to false should be considered private.

      Steps to Reproduce

      1. Create a Service Desk enabled project;
      2. Create a customer request;
      3. Add a comment as an external AC or a P2 addon

      Expected Results

      The comment should be added as public.

      Actual Results

      the issue becomes shown as an Internal comment which is not accurate

      Notes

      I suspect the reason this occurs is because the Comment did not have an entity property sd.public.comment which is what JSD seems to use to differentiate between internal and public comments.

          Form Name

            [JSDSERVER-1505] Comments added to issues by addons are listed as internal by default

            Owen made changes -
            Workflow Original: JSD Bug Workflow v5 - TEMP [ 2304448 ] New: JAC Bug Workflow v3 [ 3125904 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v5 [ 2058539 ] New: JSD Bug Workflow v5 - TEMP [ 2304448 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v5 - TEMP [ 2055924 ] New: JSD Bug Workflow v5 [ 2058539 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v5 [ 1956526 ] New: JSD Bug Workflow v5 - TEMP [ 2055924 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v4 [ 1616184 ] New: JSD Bug Workflow v5 [ 1956526 ]
            jonah (Inactive) made changes -
            Description Original: h3. Summary
            JSD should not consider comments without the {{sd.public.comment}} attribute as internal comments, but as public comments. Only comments with the entity property set to false should be considered private.

            h3. Steps to Reproduce
            # Create a Service Desk enabled project;
            # Create a customer request;
            # Add a comment as an external AC or a P2 addon

            h3. Expected Results
            The comment should be added as public.

            h3. Actual Results
            the issue becomes shown as an Internal comment which is not accurate
             
            h3. Notes
            I suspect the reason this occurs is because the Comment did not have an entity property {{sd.public.comment}} which is what JSD seems to use to differentiate between internal and public comments.             		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-1505].
              {panel}

            h3. Summary
            JSD should not consider comments without the {{sd.public.comment}} attribute as internal comments, but as public comments. Only comments with the entity property set to false should be considered private.

            h3. Steps to Reproduce
            # Create a Service Desk enabled project;
            # Create a customer request;
            # Add a comment as an external AC or a P2 addon

            h3. Expected Results
            The comment should be added as public.

            h3. Actual Results
            the issue becomes shown as an Internal comment which is not accurate
             
            h3. Notes
            I suspect the reason this occurs is because the Comment did not have an entity property {{sd.public.comment}} which is what JSD seems to use to differentiate between internal and public comments.
            jonah (Inactive) made changes -
            Link New: This issue relates to JSDCLOUD-1505 [ JSDCLOUD-1505 ]
            Justin Freeman made changes -
            Link New: This issue relates to JSD-3501 [ JSD-3501 ]
            Justin Freeman made changes -
            Link New: This issue relates to JSD-1961 [ JSD-1961 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels Original: cqt pm New: affects-cloud affects-server cqt pm

              Unassigned Unassigned
              cd3cc7134331 Andy Brook
              Affected customers:
              27 This affects my team
              Watchers:
              36 Start watching this issue

                Created:
                Updated:
                Resolved: