-
Suggestion
-
Resolution: Low Engagement
-
None
-
1
-
NOTE: This suggestion is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.
As a workaround to https://jira.atlassian.com/browse/JSD-270
Service Desk administrators usually set the Browse permission to the Service Desk project allowed to Anyone, doing so, customers will be able to see request reported by other customers.
However, the "Anyone" permission will make visible the internal comments, since these internal comments are JIRA standard comments, and users will access in the issue should be able to see.
As a Service Desk Administrator, I would like to hide my internal comments, even from users with browse permission.
- relates to
-
JSDCLOUD-2143 Internal Comment should not be visible by anonymous user
- Closed
[JSDSERVER-2143] Internal Comment should not be visible by anonymous user
Resolution | Original: Won't Do [ 10000 ] | New: Low Engagement [ 10300 ] |
Status | Original: Closed [ 6 ] | New: Closed [ 6 ] |
Resolution | New: Won't Do [ 10000 ] | |
Status | Original: Gathering Interest [ 11772 ] | New: Closed [ 6 ] |
Workflow | Original: JAC Suggestion Workflow [ 3010875 ] | New: JAC Suggestion Workflow 3 [ 3648262 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2665250 ] | New: JAC Suggestion Workflow [ 3010875 ] |
Support reference count | New: 1 |
Workflow | Original: JSD Suggestion Workflow - TEMP [ 2324556 ] | New: Confluence Workflow - Public Facing v4 [ 2665250 ] |
Status | Original: Open [ 1 ] | New: Gathering Interest [ 11772 ] |
Workflow | Original: JSD Suggestion Workflow [ 2053687 ] | New: JSD Suggestion Workflow - TEMP [ 2324556 ] |
Workflow | Original: JSD Suggestion Workflow - TEMP [ 2048859 ] | New: JSD Suggestion Workflow [ 2053687 ] |
Workflow | Original: JSD Suggestion Workflow [ 1279453 ] | New: JSD Suggestion Workflow - TEMP [ 2048859 ] |
Hi,
Thank you for raising and watching this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request.
This is an automated update triggered by low engagement with this suggestion (number of votes, number of watchers).
We hope you will appreciate our candid communication and our attempts to become more transparent about our priorities. You can read more about our approach to highly voted suggestions here, and how we prioritise what to implement here.
To learn more about our recent investments in Jira Service Management and Data Center, please check our public roadmap and our two dashboards containing recently resolved issues, and current work and future plans.
Regards,
Jira Service Management, Server & Data Center