Automation
Asked by Leanna Bremenkamp:

Using the automation features, I am creating an email triggered from a transition in JIRA Cloud, Business type project. I want to return a list of the Linked issues and present them in a list form (not separated by commas) and their summary. Not having luck with anything I have tried. Any suggestions?


Answers:
author: Trudy Claspill
body: Hello [@Leanna Bremenkamp](/t5/user/viewprofilepage/user-id/998068)

Please show us the Automation you have created.

You should be able to get what you want with

1. A [Lookup Issues action](https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Lookup-issues) to retrieve the list

2. In the email adding syntax like this:

{{#lookupIssues}}

{{key}}: {{Summary}}

{{/}

comments: author: Leanna Bremenkamp
body: I am creating an email to send out notice to a group and it returns values of multiple custom fields. The bold line is where I need to be able to call out the linked items key and summary in a list.

Automation:

Engineering has created {{issue.summary}} ({{issue.key}})\<br\>\<br\>  

JIRA items are making their way through. \<br\>\<br\>  
**Related JIRA items:\<br\>{{issue.Linked issues}}** \<br\>\<br\>  
\<hr\>  
File Directory: {{issue.File Directory Path}}\<br\>\<br\>  
\<hr\>  
PCB Quantity Required: \<br\>{{issue.PCB Quantity Required}}  
\<br\>\<br\>  
\<hr\>  
PCB Need in House by: \<br\>{{issue.PCB Need in House by:}}  
\<br\>\<br\>  
\<hr\>  
Prototype Build Date Requested: {{issue.Prototype Build Date Requested}}  
\<br\>\<br\>  
\<hr\>  
Please confirm the schedule to the group.  
\<br\>\<br\>  
Thank you

Result:

Engineering has created SUBXT75 R1 Lev XB (ECAD-32)  

JIRA items are making their way through.  

**Related JIRA items:**   
**ECAD-29, ECAD-30, ECAD-31**

File Directory: N:\\Controlled Documents\\Products\\Panels\\XT75\\PCB\\R1\\BOM

PCB Quantity Required:  
24.0

PCB Need in House by:  
7/25/2024

Prototype Build Date Requested: 2024-07-26

Please confirm the schedule to the group.  

Thank you


author: Trudy Claspill
body: Please show us the Automation you have created.

In order to include details about the linked issues in your email you are going to have to retrieve a list of the linked issues. You do that with a Lookup Issues action.

Before you generate the email use the [Lookup Issues action](https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Lookup-issues) to retrieve the list of linked issues

In the email change the syntax like this:

**Related JIRA items:\<br\>**

{{#lookupIssues}}

{{key}}: {{Summary}}

{{/}

\<br\>\<br\>  
\<hr\>


author: Leanna Bremenkamp
body: I did try that previously and didn't return any results in the email.


author: Trudy Claspill
body: I cannot provide any explanation about why it wouldn't work until you provide all the details of your rule. Images showing the entire rule and the details of each step are needed.


author: Leanna Bremenkamp
body: Sorry that was the entire thing. I just put that in the send email automation screen.


author: Bill Sheboy
body: Hi [@Leanna Bremenkamp](/t5/user/viewprofilepage/user-id/998068)

To help provide context for the symptom you are seeing, **please post images of the following**:

* your complete automation rule
* the Lookup Issues action where you gather the issues
* the Send Email action where you use the lookup results
* the audit log details showing the rule execution

Kind regards,  
Bill


author: Trudy Claspill
body: Hello [@Leanna Bremenkamp](/t5/user/viewprofilepage/user-id/998068)

We need to see all the steps in the rule in an image like this:

(This is an example of an entirely different rule.)

![Screenshot 2024-07-18 at 1.47.49?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/336515i8DC5009ABD64DB77/image-dimensions/312x349?v=v2 "Screenshot 2024-07-18 at 1.47.49?PM.png")

Then we need you to highlight each step in the rule and provide a screen image of the details of that step that appear on the right side.

And lastly we need you to go to the Audit Log:

![Screenshot 2024-07-18 at 1.50.21?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/336516i08CB1E945D597F95/image-size/large?v=v2&px=999 "Screenshot 2024-07-18 at 1.50.21?PM.png")

Then find the most recent execution log for the rule that doesn't say "Config Change" for the status, and click on the Show More link on the right side for that entry.

![Screenshot 2024-07-18 at 1.53.35?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/336517iDC257AAC554190F2/image-size/large?v=v2&px=999 "Screenshot 2024-07-18 at 1.53.35?PM.png")

Then provide a screen image of all the details in that entry. Here's an example.

![Screenshot 2024-07-18 at 1.55.01?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/336518i0CCAF8F41566E857/image-size/large?v=v2&px=999 "Screenshot 2024-07-18 at 1.55.01?PM.png")

Sometimes elements of a rule don't work as expected because of where that step is compared to the other steps of the rule. Sometimes there is a syntax error. We can't debug the rule without having the details of the entire rule, the details of each step, and the log for when the rule executed.


Tags: cloud

jira-cloud