-
Suggestion
-
Resolution: Low Engagement
-
None
-
None
-
1
-
Problem Definition
As a Service Desk Admin I would like to restrict the ability to remove Requests Participants from a Service Desk Request, because currently any user who has access to a Service Desk request (reporter, participant, or organization member) can remove any participant.
Suggested Solution
Implement a way to restrict Customer's abilities to remove Request Participants, maybe by adding an extra setting in the page Project Settings > Customer Permissions called Can customers remove participants from requests?
Workaround
None
[JSDSERVER-6042] As a Service Desk Admin I would like to restrict the ability to remove Requests Participants from a Service Desk Request
| 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 [ 3012072 ] | New: JAC Suggestion Workflow 3 [ 3647122 ] |
Hi,
This feature (and many many more) is available in our app Extension for Jira Service Desk. Under Project settings, in the General tab, you can find "Restrict to remove participants". When you switch the toggle on, "Remove" label is hide. Moreover, you can define on which request types it should work. We also wrote about it in our latest article about Jira Service Desk customisation.
Best regards,
Kate
| Workflow | Original: Confluence Workflow - Public Facing v4 [ 2857898 ] | New: JAC Suggestion Workflow [ 3012072 ] |
| Support reference count | New: 1 |
| Description |
Original:
h3. Problem Definition As a Service Desk Admin I would like to restrict the ability to remove Requests Participants from a Service Desk Request, as for now anyone who has access to a Service Desk request (reporter, participant, or organization member) can remove any participant. h3. Suggested Solution Implement a way to restrict Customer's abilities to remove Request Participants, maybe by adding an extra setting in the page Project Settings > Customer Permissions called Can customers remove participants from requests? h3. Workaround None |
New:
h3. Problem Definition
As a Service Desk Admin I would like to restrict the ability to remove Requests Participants from a Service Desk Request, because currently any user who has access to a Service Desk request (reporter, participant, or organization member) can remove any participant. h3. Suggested Solution Implement a way to restrict Customer's abilities to remove Request Participants, maybe by adding an extra setting in the page Project Settings > Customer Permissions called Can customers remove participants from requests? h3. Workaround None |
| Description |
Original:
h3. Problem Definition
As a Service Desk Admin I would like to be able to removing Requests Participants from the Customer portal h3. Suggested Solution Implement a way to restrict Customer's abilities to remove Request Participants, maybe by adding an extra setting in the page _Project Settings > Customer Permissions_ called _Can customers remove participants from requests_ ? h3. Workaround None |
New:
h3. Problem Definition As a Service Desk Admin I would like to restrict the ability to remove Requests Participants from a Service Desk Request, as for now anyone who has access to a Service Desk request (reporter, participant, or organization member) can remove any participant. h3. Suggested Solution Implement a way to restrict Customer's abilities to remove Request Participants, maybe by adding an extra setting in the page Project Settings > Customer Permissions called Can customers remove participants from requests? h3. Workaround None |
| Summary | Original: As a Service Desk Admin I would like to be able to removing Requests Participants from the Customer portal | New: As a Service Desk Admin I would like to restrict the ability to remove Requests Participants from a Service Desk Request |
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