Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Manage access of system

Hi everyone,

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!

Thank you!

1 answer

1 accepted

2 votes
Answer accepted

Hi @Nguyen Ngo Hoang Long 

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.

This is really helpful.
Thank you @Luis Machado 

Like Luis Machado likes this

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events