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
I have a question that I am hoping someone will be able to help me with. We are in the process of moving from a team-managed service desk to a company-managed service desk for better control of workflows.
We have some access requests that include Approvals, as an example:
1. Storage Accounts
However we have some access request(s) that do not include approvals, as an example:
Each access request that needs an approver are all different from one another, however our main requirement is that we would like to keep the access request(s) both that need approval and DO NOT need approval on the same queue/request type.
What would be the best way to go about setting up a trigger to generate on the back end for the approvals depending on the value selected? Is there a way to do this? Or will I have to seperate each one out based on different use case / process workflow?
Any help would be greatly appreciated!
Hi @Alex Palmer ,
First and foremost, congratulations with moving to a more structured service management! Especially in Service mgmt I think it really important to have a transparent, clear process for all parties involved.
Now for you current question, how would you like to differentiate between the different types of access requests?
I hear that you want to bundle them all in 1 queue / request type / process flow. Those are 3 completely different levels of bundling however.
Queues accept JQL so can contain whatever you want, issue types and flows are linked, but an issue type can have many request types.
If you want to use the same workflow you could:
2 very different possibilities, where the latter is more scalable of course.
Automation is needed in both.
There are a lot of ways to tackle something like this, let me know if you need more info and enjoy the journey!
Thank you so much for the response, this has been super helpful to evaluate options. With our current service desk we have multiple applications we provision (screenshot attached), I don't think listing all of those out as multiple request types, therefore I think Option 2 may do the trick...
Can you add an approver to each of the checkboxes (or picklist) or whatever route we decide to go? i.e. can you set an approval workflow for Storage account to go to one person only, however for 1password you could set up a workflow based on two people who both have to approve?
Thanks again for everything, definitely moving in the right direction!