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

Is it possible to auto-assign an issue to a component lead when it's moved to a specific status?

For example, when an issue is moved to Ready for QA or In QA, it auto-assigns to the QA component lead that is set for the project. 


The only method I see is to create an automation to assign to a specific person name, but trying to avoid having to change that automation every time there is a team member change. Would also like to be able to copy project config to a new project, and using component lead would again prevent having to update the automation for each new project.

3 answers

1 accepted

1 vote
Answer accepted

Hi @Amber Arguijo  -- Welcome to the Atlassian Community!

As you note, with automation rules there is no way yet to access the component lead from the issue smart value, and so do the assignment.  Here are the suggestions to support that:

Until one of those are implemented a convoluted work-around would be to call the REST API from the automation rule (using a web request) to get all the components, pull out the lead using RegEx, and then make the assignment.

Best regards,


0 votes
Danyal Iqbal Community Leader Mar 03, 2021

You can write a scripted postfunction to do this and attach it to the transition.

Okay - so no way to do this natively? 

0 votes
Jack Community Leader Mar 03, 2021

yes. use Automation.

Trigger - issue transitioned from (any) to Ready for QA

Condition - if/else block and inspect for each component

action - in each if/else leg use Edit issue and set Assignee

Thanks! I was actually hoping to be able to just tell the automation to assign based on the leads for each component that were already set in the project settings, instead of having to choose the assignees for each component again in this step. 

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