-
Bug
-
Resolution: Answered
-
High
-
None
-
2.2-OD-04, 2.5.4
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
- Create a Service Desk enabled project;
- Create a customer request;
- 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.
- incorporates
-
JSDSERVER-1261 Comment return from REST API does not include Visibility for Service Desk Project
- Closed
- is duplicated by
-
JSDCLOUD-5132 JSD Internal comment webhooks don't have comment visibility set - results in unexpected leaking of internal comments
- Closed
- is related to
-
JSDSERVER-3907 Unable to create comments using JSD API as the Portal User reporter
- Closed
-
JSDSERVER-3897 JSD Component API - need to be able create comments without firing events
- Gathering Interest
- relates to
-
JSDCLOUD-1505 Comments added to issues by addons are listed as internal by default
- Closed
-
JSDSERVER-1961 Email replies by Participants are registered as internal comments
- Closed
-
JSDSERVER-107 Create a public REST API for JIRA Service Desk
- Closed
-
JSDSERVER-3501 Allow Participants to See Emailed Comments when "Email Requests" is Disabled
- Gathering Interest
-
ACJIRA-320 Loading...
- Testing discovered
-
JSDSERVER-2347 Comments added through the CommentManager API cant be made 'public'
- Closed
- was cloned as
-
TESLA-586 Loading...