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 am doing a service portal which can manage tasks about provisioning and deprovisioning.
For provisioning, it's quite easy.
- An user will have to create a ticket of which system they want to have the access.
- I already setup the automation of correct assignees to the requested system.
- Right now, i also can use filter view to see which systems an user have created requests for provisioning. (1)
However, for deprovisioning, it's a bit tough.
- But when an user leaves my company, is there any way to create deprovisioning tickets to all the requested system based on the list (1)?
NOTE: My work around is when the HR creates a termination ticket of an employee, the IT Helpdesk team has to take a look of the list (1) and create deprovisioning tickets but it really take a lot of effort.
I'm really appreciated if anyone could help me on this!
Welcome to the Community!
My first thought is you could create a custom field that houses a value for the user being provisioned. Then when a de-provisioning ticket is created, you have your automation run a lookup with a JQL that searches for any issues that match the one used in the de-provisioning ticket. You can then feed that lookup list into a branch that can spin up a new ticket for each provisioning ticket found.
Another way you could do this is by leveraging Assets. You could have a user object with an attribute that lists software assets as they are provisioned. You can automate adding assets to the user as part of your request process as well as automate removing them.