-
Suggestion
-
Resolution: Low Engagement
-
None
-
0
-
2
-
NOTE: This suggestion is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.
As a JIRA Service Desk customer, it would be nice if you could have an option on the "Add People/Participants" button where you can choose if the new participant will only have the permissions to just watch issues (read-only access) without the service desk customer standard permissions (e.g Those new participants can not create new issues on the customer portal).
- relates to
-
- Closed
- supersedes
-
JSDSERVER-4478 Customers without Create Issue permission can't be added as Request Participants
-
- Closed
-
- mentioned in
-
![[Extranet] Page](/images/icons/generic_link_16.png "[Extranet] Page")
Page
Failed to load
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSDSERVER-2067] As a JSD customer, I would like to add participants to just watch issues (Without the ability to create new issues)
| 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 ] |
| UIS | Original: 1 | New: 0 |
| Workflow | Original: JAC Suggestion Workflow [ 3012141 ] | New: JAC Suggestion Workflow 3 [ 3650472 ] |
We got the same requirements from our larger (corporate) customers, who want to let their subsidiary users in on requests they set out with us for them.
So typically a case of our corporate customer organizes 1st line support within their corporation, only when they can't solve an issue themselves, the HQ will raise a request on our portal.
they want the local users to be able to view the issue + add a comment, but prevent the local users from creating new request in the portal, or change the sharing on an existing request (add/remove users/organizations)
Currently, we workaround the creation limitation via a validator on the "create issue" transition in underlying workflow, but this approach would be better handled via portal, e.g. via:
Split-up the Role "Customer-users" into "Portal-access users" and "Portal Request creators/editors"
| Workflow | Original: Confluence Workflow - Public Facing v4 [ 2664779 ] | New: JAC Suggestion Workflow [ 3012141 ] |
| Support reference count | New: 2 |
| Workflow | Original: JSD Suggestion Workflow - TEMP [ 2323753 ] | New: Confluence Workflow - Public Facing v4 [ 2664779 ] |
| Status | Original: Open [ 1 ] | New: Gathering Interest [ 11772 ] |
| UIS | New: 1 |
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