Currently, it is possible to provide users with permissions to work with the connector from Jira (all the functionalities). However, it would be great having the ability to provide/restrict access to work with the create and/or associate buttons.
Guest
| Hosting platform | Cloud, Server, Data Center |
Really useful feature. We need this feature.
Attachments Open full size
We need this in our org. Our product team are the only ones who should have ability to associate/create Jira bugs but we want other users to be able to view when their is an associated bug.
Attachments Open full size
Hi
Facing the same issue on our end, and this is extremely misleading to the user. A user that only has the "Browse Projects" right in Jira will have no edit rights whatsoever on issues, but the SalesForce section of the issue still remains completely active and available, so the user can click on the buttons to create new Salesforce objects or associate with existing ones.
Clicking on either of those buttons does eventually result in a cryptic error about the mapping not being correct, so the user can't actually affect the data in any way, but the buttons should be disabled and at the very least the error messages made way clearer.
This issue has been discussed with your support department under SRSUP-16992.
Attachments Open full size
Hi ServiceRocket Team, this is a crucial feature for operations and compliance. Please add the ability to only enable Jira creation to certain salesforce users, but all other users can view Jira information. Use Case: Engineering does not want all call center users to be able to open bug tickets i, but rather Tier 1 should be able to view tickets, and Tier 2 or 3 can only escalate Jira tickets when deemed necessary
Attachments Open full size