How to refer to the component owner?

[Nguyễn Quang]

Hi support team,

 I want to send an email to the component owner (the one who has been assigned as Lead of a component) when an issue is transitioned to Approved status. The steps are:

- Trigger the automation if an issue transitioned to Approved.

- Send the email to the component owner of that issue. 

How could I do the #2 step by an automation?

thanks!

[Vishal Biyani]

@Nguyễn Quang 

Currently it is not feasible to get component lead based on Component added in the issue within an automation rule.

However, you can send a web request (REST API call) to get the component lead name based on the component id.

There is a feature request that you can vote for.

[AUTO-485] Automation support for working with components and component leads - new triggers, actions and smart values - Create and track feature requests for Atlassian products.

[Pasam Venkateshwarrao]

@Nguyễn Quang As Per previous records in community i found a different solution which was answered by David Fischer you can refer the page 

https://community.atlassian.com/forums/Jira-questions/Automation-for-Jira-E-Mail-on-Component-Lead/qaq-p/2016998

[David Bakkers]

That article you've linked to describes a custom solution by creating a custom field and using the third party Jira Misc Workflow Extension to populate the values.

Can you advise if YOUR company has that extension installed and has specifically configured it to create those extra workflow smart values?

[Pasam Venkateshwarrao]

@David Bakkers Exactly right we are using Add-ons for workflow extensions.

[David Bakkers]

It would have been productive if you had included that critically important piece of information from the outset, rather than a post and a screen grab that inferred you were using a standard Jira setup and therefore the default automation smart values, which of course won't work for anyone without JMWE installed.

[Pasam Venkateshwarrao]

@David Bakkers i really appreciate your words.

[Pasam Venkateshwarrao]

Hi @Nguyễn Quang 

Automation rule to send email to component lead

[Nguyễn Quang]

Hi @Pasam Venkateshwarrao I tried but it seems your suggested smart value {{issue.components.lead.emailAddress}} is return empty in this case.

[David Bakkers]

Hello @Pasam Venkateshwarrao

Can you please provide a link to the Atlassian documentation that describes those two smart values {{issue.components.lead.displayName}} and {{issue.components.lead.emailAddress}} that you used in your automation screen grab.

I know only of the existence of {{issue.components.name}} for Jira Cloud and {{issue.components.first.name}} for Jira DC (which the OP has).

[Pasam Venkateshwarrao]

@Nguyễn Quang can you check whether component field is filled and also check component lead is empty in components tab

[David Bakkers]

and also check component lead is empty in components tab

That doesn't make any sense. If the component lead is empty, then where on earth will the issue.components smart value get the value of .lead.displayName and .lead.emailAddress from??

Also, feature request AUTO-485 says that additional automation smart values for issue.components are still Under Consideration.... they don't exist yet.

Lastly, since the Components field is a multi-select type, it could contain multiple components, each of which has a separate lead... so how, exactly, would it be possible for a smart value issue.components.lead know which lead for which component it should refer to?

[David Bakkers]

Hello @Vishal Biyani 

Given that @Pasam Venkateshwarrao hasn't answered the questions I've asked, I think it's safe to assume their suggested automation can't possible work, because it uses made-up, non-existent smart values that, even if they existed, couldn't possibly know which lead for which component to refer to.

[Pasam Venkateshwarrao]

@David Bakkers  I have used the component lead field in the screen and tried the automation some how it worked for me.if you give any suggestions on this i will accept and will learn if it is wrong,Thanks for pointing out to me.

[David Bakkers]

.