Hello. I want to display the child value only from a cascading custom field in the email content of an automation rule that sends out emails. I tried adding "{{issue.customfield_1234.child.value}}" to email content but when the rule is triggered and email is sent out, that piece is empty. I also looked in the below to see if there was a smart value I could use but saw no mention of custom cascading fields. Any help would be greatly appreciated
Automation smart values - issues | Cloud automation Cloud | Atlassian Support
Hi @Adrian Avalos
For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide context for the community to offer ideas. Thanks!
Until we see those...
If the field value and its child value are not empty, I would expect these two to work:
parent: {{issue.customfield_10105.value}}child : {{issue.customfield_10105.child.value}}
Have you confirmed both are set?
Have you confirmed the custom field id is correct?
Kind regards,Bill
Hello @Adrian Avalos
{{issue.customfield_1234.child.value}} is the correct syntax to reference child value.
Have you tried to confirm you have the correct customfield number?
Maybe reference the field directly..
{{issue.Your Field Name.value}}
{{issue.Your Field Name.child.value}}
Hi @Bill Sheboy
Adding a bit more details this Automation rule only has three parts. The trigger set every 7 days, a jql lookup, and the send email piece posted below. The Audit Log displays as success when I hit run rule button. Email is also successfully received with everything displaying in cells in table except the output from my custom field 30732 which appears empty. Tried setting both and can confirm issues have something listed in that cascading field
Hello,
See below for a list of requirements in 'Submitted', 'Section Review', or 'Branch Review' Status for over 2 weeks <a href=https://maestro.dhs.gov/jira/issues/?filter=131819> or click here to access filter to see Issues</a>
<table style="border-collapse: collapse" table-layout="fixed" width="80%">
<tr><th style="border: 1px solid #000000; background-color : #CDCACA" valign="middle" halign="center">Key</th>
<th style="border: 1px solid #000000; background-color: #CDCACA" valign="middle" halign="center">Summary</th>
<th style="border: 1px solid #000000; background-color: #CDCACA" valign="middle" halign="center">Status</th>
<th style="border: 1px solid #000000; background-color: #CDCACA" valign="middle" halign="center">Assignee</th>
<th style="border: 1px solid #000000; background-color: #CDCACA" valign="middle" halign="center">Section</th></tr>
{{#lookupIssues}}<tr><td style="border: 1px solid #000000" valign="middle" align="center"><a href="{{url}}">{{key}}</a></td><td style="border: 1px solid #000000" valign="middle" align="center">{{summary}}</td><td style="border: 1px solid #000000" valign="middle" align="center"> {{status.name}}</td><td style="border: 1px solid #000000" valign="middle" align="center"> {{assignee.displayName}}</td><td style="border: 1px solid #000000" valign="middle" align="center"> {{issue.customfield_30732.value}}</td><td style="border: 1px solid #000000" valign="middle" align="center"> {{issue.customfield_30732.child.value}}</td></tr>{{/}}
</table>
Hi @Kalyan Sattaluri I tried all the syntaxes you shared and no luck. Will not display in email being returned and can also confirm custom field number is correct
First thing: when inside of an iterator such as {{#lookupIssues}}...{{/}} do not add the {{issue. prefix to the fields. The scope is now the lookup and not the "current issue". Please try removing that and re-test:
<td style="border: 1px solid #000000" valign="middle" align="center"> {{customfield_30732.value}}</td><td style="border: 1px solid #000000" valign="middle" align="center"> {{customfield_30732.child.value}}</td>
If that does not help...
Are you using Jira Cloud or Jira Data Center? That is relevant because the Lookup Issues action for Jira Data Center does not yet support many fields, including custom fields.
Just attempted retested with {{issue. prefix removed like in your script and no luck. And I'm using Data Center
It looks like you're new here. Sign in or register to get started.
