We're currently implementing Jira Service Desk for an HR department. I'm looking for a way in which we can allow only certain Agents to view certain request types without having a separate project. I've been looking into issue security but it seems this only works on projects and not on requests.
Use case:
Employee A raises a harassment issue/request. Only the HR Chief Officer would be able to see the request due to the sensitivity of the issue.
Another functionality that we're trying to implement is setting up certain requests to be raised by certain users that fall under a specific group. I already asked the question here and was directed to an add-on but I was told by the developers that this functionality is not available for the Cloud version.
hello @Mikele Schembri - In short, the _Browse_ permission_ is used to manage access at the project level and _Issue Security_ is used within the project to manage access to issues.
So in the described use case, only the HR Chief Officer would be allowed by the Security Level assigned to the issue while other issues in the same JSD project would not be restricted.
For managing create permission by request type add a validator to the create step in the workflow restricting access to person, role, or group. This community post started in 2013 but has some interesting ideas and options that you might also find useful: https://community.atlassian.com/t5/Jira-questions/Restricting-issue-creation-of-certain-types-based-on-user/qaq-p/32785
Hope this answers your question - if so, please consider clicking the "Accept Answer" button so other Community users see the indicator in their search results. Thanks!
.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @LarryB , many thanks for your reply. With regards to the first answer, I did create an Issue Security Scheme with and Security Level that is assigned to a specific user, the HR CO. However neither from the Issue Type nor from the Issue Type Schemes can I find from where to assign the Issue Security Scheme created.
With regards to your second answer, I will be looking into it shortly.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
"Security Level" is the field to set. I like to set the security level via automation (post-function, pre-filled field in request form, etc.) whenever possible so it doesn't rely on humans, especially for sensitive information.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Mikele Schembri Hellllo
You can use this plugin "Extension For Jira Service Desk". In this plugin you have a lot of option that let you choose who can see your request types and it has a cloud version. its the best way. Also you can use the method that @LarryBrock says.
Best regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ashkan, I linked to that plugin in my question as I already tried it but was notified by the plugin's support that what I need was not an option on the Cloud version.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.