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 looking for a way to work with Jira in a more object oriented way with different teams. For example, onboarding should not open a ticket in different projects, but an object (contract, new hire) should be processed by different teams in different stages. These teams should then only have access to the ticket when they need to process it.
So far I am working on two possible solutions:
1. create a project for e.g. onboardings and use the security levels to assign different teams to the stages of the work process, e.g. create the work contract by HR, prepare the hardware by IT.
2. create an Epic in the project where the process (onboarding in HR) starts and for each further stage of the workflow another ticket is opened (story or task) in another project (for example IT).
I would be very grateful for any further suggestions!
Translated with www.DeepL.com/Translator (free version)
Hi @Janine Resch - Option 2 is going to be most efficient and mainly because option 1 introduces a lot of overhead with security levels as well as splitting where team members have to pay attention to incoming work (assuming that onboarding isn't the only tasks they have to look out for).
You can help keep things organized and efficient with option 2 by leveraging automation. For example, when HR transitions to a status like "IT Onboarding", you could trigger a rule to create an IT issue (copying over pertinent information from the HR issue), link it back to the HR issue, etc. You can also have automation where as IT progresses through various statuses, it adds a comment back on the original HR request so users don't have to think about transactional communications.