Add components to automation rule email

[Anthony Pugliese]

HI, I am looking to send an email via automation rule to internal TM's once an issue type is created.

I have everything working except for components appearing in the email.

I have tried numerous ways to find the correct syntax but is not appearing.

as shown in email copy below i am using both {{issue.components.name}} & {{issue.getComponents()}} and neither work.

Reporter: {{reporter.displayName}}
Issue ID: <a href="{{issue.toUrl}}">{{issue.key}}</a>
Title: {{issue.summary}}
Component: {{issue.components.name}} {{issue.getComponents()}}
Description: {{issue.description}}

is this possible? what am i doing wrong?

any help would be appreciated.

[Kalyan Sattaluri · Accepted solution]

Hello @Anthony Pugliese 

{{issue.components.name}} is the correct syntax.

Maybe try doing a "refetch" action before sending email. I have heard of race condition where not all fields are available when trigger like issue created is used. Just a hunch.

[Anthony Pugliese]

@Kalyan Sattaluri 
thanks for reply

i didnt provide it before, i had already had this step in the workflow.
would there be an issue with the step in the process to 're-fetch"? do i need to add this re-fetch before the sending of email?

[Kalyan Sattaluri]

If you have already included a fetch before, maybe we dont need again. But it does not hurt.

Also, Can you, after your current fetch after issue is created, log {{issue.components.name}} to see if you are able to see that info.

[Anthony Pugliese]

@Kalyan Sattaluri 

thanks. looks like adding a secondary re-fetch has made it work