The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

[Email Automation] unable to use {{lookupIssue}} for smart value {{priority.name}}

James Warrington
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 18, 2023

Currently I'm trying to create an automated email that provides information overview regarding open issues. I've created a {{lookupIssue}} to filter the tickets. The lookup filter works and im able to display info from fields such as "summary, assignee, reporter.name, status.name" however, {{priority.name}} doesn't return a value.

 


<table>
{{#lookupIssues}}
<tr>
<td>
<p>
{{created}}</p>
</td>
<td>
<p>
{{status.name}}</p>
</td>
<td>
<p>
{{priority.name}}</p>
</td>
</tr>
{{/}}
</table>
image.png
image.png


2 answers

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

1 vote
Answer accepted
Joseph Chung Yin
Community Champion
September 18, 2023

@James Warrington -

Welcome to the community.  

((priority.name}} smart value syntax is correct. 

You can use the command below to determine if priority is there for your lookup issues in question.

https://<yourinstanceurl>/rest/api/2/issue/<issuekey>?expand=names

 Hope this also helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

James Warrington
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 19, 2023

Thanks for the response Joseph. I figured out what the cause was. I had a on "issue update" trigger which would then start a "lookupIssues+JQL" action. I've replaced this with the "Scheduled+JQL" trigger. this now allows me to access custom fields within each issue.

 

On side note, for Linked Issues ( tag - {{issuelinks}} ). should I able to loop through them with the following?


<ul>
{{issuelinks}}
<li>{{outwardIssue}}</li>
{{/}}
</ul>

2 votes
Esteban Diaz
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
September 18, 2023

Hi @James Warrington 

I've got a similar automation where the Send Email component looks like this:

<ul>
{{#lookupIssues}}
<li>
<a href="{{url}}">{{key}}</a> - {{Summary}} - <b>
{{priority.name}}
({{Reporter.Displayname}})</b>
</li>
{{/}}
</ul>

And works fine ... showing the priority name in the sent email body.

 

Cheers, 

Esteban

TAGS
AUG Leaders

Atlassian Community Events