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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,456,478
Community Members
 
Community Events
176
Community Groups

I need a solution for on boarding new employees that uses automation. spawn ticket to multiple team

What is the best way to have a ticket sent to multiple teams for fulfilment of a new employee being on boarded? 

The ticket should go out in parallel to all teams that are required to complete their respective activities separate from each other e.g. access to building, access to IT systems, printer card created, mobile phone etc. 

Ideas:

Use automation to create/spawn additional subtasks for each group

Create a new request type, workflow and screens for on boarding 

Share ticket with onboarding Teams/groups using active directory 

 

If you have a solution please post screens, automation, workflow diagram etc.

 

cheers

 

 

 

 

1 answer

2 votes
Ismael Jimoh Community Leader Dec 03, 2022

Hi @craig orde 

Firstly there isn’t a one solution fits all as we do not know the full context of what should be created for you and your employees.

Anyway you could use the on create issue in automation’s page, add a condition to check issue type I’ll recommend a specific issue type for these tickets to avoid all issues that are created firing this automation and lastly use the create sun-task operation to create your sub-task. Close that you’ll like to set fields and then add the specific fields like assignee you want to set on the sun-task.

See the image attached as a sample:

F139B08B-00A5-4A14-8372-59EFC6B50FF1.png

Ismael Jimoh Community Leader Dec 03, 2022

F00D3951-62D1-4559-B537-61889A5542DC.png

 

shows that assignee is set

Thanks Ismael.

Didn't mention I need this for Jira Service Management project.

 

E.g. There are 3 teams A, B & C

The idea is to Create a single Ticket that goes out to multiple teams e.g. HR raise the Service Request (SR) to On Board a new employee. 

The Ticket should go out to Teams A, B & C into a Queue named On Boarding in JSM as well it could be filtered to for each of the Teams (A, B and C) Queues.

 

How would you write this in an Automation rule. Is Sub-task creation the only way? 

or Can a single Ticket (with no sub-tasks) be automated go out to multiple Teams. 

The SR would need to be sent to Groups to ensure it was not missed and land into the respective queue for each Team A B and C.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events