-
Bug
-
Resolution: Not a bug
-
Low
-
None
-
2.5.1-OD-03
NOTE: This bug report is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding bug report.
Summary
Replies from a Service Desk Customer participants are always created as internal comments when the reply made via email. Raising this as a bug because it doesn't make sense to have customer adding internal comments to the request they've raised.
Steps to Replicate
- Add a customer into a ticket as a participant.
- Disable Service Desk email channel for the project you are working on.
- Ensure that the participant has permission from JIRA Permission to add comments to the ticket. If you don't do this; SD Customer can't add comments on the ticket.
- Comment on the ticket so that a notification is sent to the participant.
- Reply to the notification as the participant.
Expected Result
Comment will be added as a public comment.
Current Result
Comment will be added as an internal comment.
- is related to
-
JSDSERVER-1505 Comments added to issues by addons are listed as internal by default
-
- Closed
-
-
JSDSERVER-2347 Comments added through the CommentManager API cant be made 'public'
-
- Closed
-
- relates to
-
JSDCLOUD-1961 Email replies by Participants are registered as internal comments
-
- Closed
-
-
JSDSERVER-3501 Allow Participants to See Emailed Comments when "Email Requests" is Disabled
- Gathering Interest
- mentioned in
-
Page Failed to load
[JSDSERVER-1961] Email replies by Participants are registered as internal comments
Remote Link | New: This issue links to "Page (Confluence)" [ 490091 ] |
Workflow | Original: JSD Bug Workflow v5 - TEMP [ 2304732 ] | New: JAC Bug Workflow v3 [ 3125095 ] |
Status | Original: Done [ 10044 ] | New: Closed [ 6 ] |
Workflow | Original: JSD Bug Workflow v5 [ 2058671 ] | New: JSD Bug Workflow v5 - TEMP [ 2304732 ] |
Workflow | Original: JSD Bug Workflow v5 - TEMP [ 2056578 ] | New: JSD Bug Workflow v5 [ 2058671 ] |
Workflow | Original: JSD Bug Workflow v5 [ 1956214 ] | New: JSD Bug Workflow v5 - TEMP [ 2056578 ] |
Workflow | Original: JSD Bug Workflow v4 [ 1615446 ] | New: JSD Bug Workflow v5 [ 1956214 ] |
Description |
Original:
h2.Summary
Replies from a Service Desk Customer participants are always created as internal comments when the reply made via email. Raising this as a bug because it doesn't make sense to have customer adding internal comments to the request they've raised. h2.Steps to Replicate # Add a customer into a ticket as a participant. # Disable Service Desk email channel for the project you are working on. # Ensure that the participant has permission from JIRA Permission to add comments to the ticket. If you don't do this; SD Customer can't add comments on the ticket. # Comment on the ticket so that a notification is sent to the participant. # Reply to the notification as the participant. h2.Expected Result Comment will be added as a public comment. h2.Current Result Comment will be added as an internal comment. |
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-1961]. {panel} h2.Summary Replies from a Service Desk Customer participants are always created as internal comments when the reply made via email. Raising this as a bug because it doesn't make sense to have customer adding internal comments to the request they've raised. h2.Steps to Replicate # Add a customer into a ticket as a participant. # Disable Service Desk email channel for the project you are working on. # Ensure that the participant has permission from JIRA Permission to add comments to the ticket. If you don't do this; SD Customer can't add comments on the ticket. # Comment on the ticket so that a notification is sent to the participant. # Reply to the notification as the participant. h2.Expected Result Comment will be added as a public comment. h2.Current Result Comment will be added as an internal comment. |
Link |
New:
This issue relates to |
Labels | Original: SEE affects-cloud | New: SEE affects-cloud affects-server |