You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
How can I give some users limited Service Desk Access and other users full Jira access - while still keeping all of their approver roles and moving issues through the workflow?
There are sensitive payroll/bonus related tickets that only a select few should see. Those people would need to see tickets assigned to them, be able to approve/deny them and move them along in the workflow without being able to see any other tickets or issues within the project.
My understanding is that these people who need limited access require only Service Desk Access.
There are others (managers/directors/etc) who should have full back-end Jira access to see everything.
Can this be done? If so- how?
I've looked into creating an ISSUE SECURITY SCHEME but these aren't very clear and I've yet to see where I can assign a specific payroll/bonus ticket type to them scheme. It seems as though you can apply an ISSUE SECURITY SCHEME to a PROJECT, but not an ISSUE (which doesn't make sense to me.)
I've also tried putting users in either SERVICE DESK TEAM (which has full back-end Jira access) and SERVICE DESK CUSTOMER (limited access) for their roles, but then various approval buttons and other workflow missteps happened.
Is it a matter of going to the PROJECT PERMISSIONS area and adding indiviudal names in either the "Browse Projects", "Assign Issues", "Edit Issues", "Transition Issues", etc.?
It looks like there are a few requests here:
Jira vs Jira Service Management Access
In simple terms...
So for example, you could modify the Permission Scheme for the JSM Project to restrict Browse Projects access to...
Restricting Issue Access
Assuming this is from within the Agent view...
You are correct that Issue Security Schemes can do this. You'd need a method to...
You can then create your Issue Security Scheme:
Once the Security Scheme is live, you need to decide how to apply it. As these tickets could be sensitive from creation - I would ensure they're restricted immediately. To do this, I would...
Assuming Assignee is applied to the Security Level, you could then assignee the ticket to a user, and it'll be visible to them. But before that, it would be hidden.
You can also make the Security Level the default at creation from the main list of Security Levels, if all tickets should be limited in this way.
This isn't linked to the Issue Security Scheme directly - apart from the fact a user needs to be able to see the Issue if they're going to approve it, edit it, transition it, etc.
Approvers are managed via the Workflow - i.e.
Let us know if the above helps - or, if you have any further questions!