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
Next: Root
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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
For JIRA cloud, when creating issues, and using automatic assignment issues are assigned to a component lead if a component with a component lead is included. What about issues that are created with multiple components that each have a different component lead, and notification is set to component lead for each?
Welcome to Atlassian Community!
If you create an issue with multiple components that have leads the issue will be assigned to the lead who's component is furtherest to the left. Example, let's say you create an issue and add 3 components (comp1, comp2, comp3) and comp1 and comp3 both have leads, the issue would be assigned to comp1.
Now, if you want to notify and maybe add all component leads that have a component added to and issue you could do that with automation. All you would need to do is use the web request action to get each lead via the REST API and then send them a notification/add them as watchers to the issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.