Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How to notify the component lead when the issue is updated with a new component?

Hi All,

Any inputs on my issue will be very helpful, thanks in advance.

Here is my scenario, all the customer request are by default tagged by a particular component (ex: SD) and I have set the notification for the SD component lead to getting notified when the issue is created. Now there are few use cases that the SD team needs to redirect the ticket to some other team (i.e., tagging some other component ex: FD), in this case whenever the issue got updated with new components I wanted to notify that particular new component lead. How can I do it?


3 answers

Hi @devsuresh2005  -- Welcome to the Atlassian Community!

No; it is not possible yet to use the Component Lead attribute as a smart value from an automation rule.  Here are the two backlog items which would make that possible:

Best regards,


Hi @devsuresh2005 ,

If you're looking for a short-term solution, I'd like to recommend having a look at Jira Workflow Toolbox and its built-in automation rules feature.

When dealing with single components, a simple rule like


could alert your component leads via '@ mentions' as a comment, e.g.


If you prefer an email without adding a comment, there is a dedicated send email action as well. Besides, those rules can obviously be restricted to projects/issue types/etc. using conditions.

If you have further questions, e.g. how to configure a rule that works for multiple components, let me know.


Disclaimer: I'm part of the team behind the aforementioned app.

You can easily do this in JIRA automation available in the project settings.



The trigger can be the update of the issue, you can place a condition for a specific component and then include the action of notifying.

Hera an example:


Instead of sending an email you can add a watcher.

Suggest an answer

Log in or Sign up to answer

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you