nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Due Date and Priority smart values are blank in automation email

Chase Bradshaw

Hi all,

I am trying to figure out what I am doing wrong here. I get the email sent with the right list, summary, etc. But, the stated issue priority and due dates are always blank (even though the issues have data populated for the lookupissues JQL. Any ideas what I am doing wrong with the following syntax?

<ul>
{{#lookupIssues}}
<li><a href="{{url}}">{{key}}</a> - {{summary}} - {{issue.priority.name}} - Due - {{issue.duedate.fullDate}} </li>
{{/}}
</ul>

Accepted answers

Tom Williams

Hi @Chase Bradshaw ,

@Darryl Lee is correct these are fields aren't included yet. (Annoying!!)

A couple of useful links to monitor;

List of supported fields;

https://support.atlassian.com/jira-software-cloud/docs/automation-actions/#Automationactions-Lookupissues

This post will be updated once custom fields are included;

https://community.atlassian.com/t5/Automation-articles/Send-a-list-of-issues-in-Slack-with-Jira-automation-s-newest/ba-p/1411819

All comments

Darryl Lee

Maybe because you're iterating through a list you can omit the "issue." and just use {{priority.name}} and {{duedate.fullDate}}.

Just an idea - I'm on my phone and can't test.

Chase Bradshaw

I tried dropping the leading "issue." from the syntax, but still same result.

Darryl Lee

Huh. Sounds like it treats priority and duedate like custom fields, in that they're not accessible within the list context:

https://community.atlassian.com/t5/Automation-questions/Custom-fields-in-lookupIssues/qaq-p/1432144

That's unfortunate.

Tom Williams

Hi @Chase Bradshaw ,

@Darryl Lee is correct these are fields aren't included yet. (Annoying!!)

A couple of useful links to monitor;

List of supported fields;

https://support.atlassian.com/jira-software-cloud/docs/automation-actions/#Automationactions-Lookupissues

This post will be updated once custom fields are included;

https://community.atlassian.com/t5/Automation-articles/Send-a-list-of-issues-in-Slack-with-Jira-automation-s-newest/ba-p/1411819

Bill Sheboy

Hi @Chase Bradshaw

Yes, and... to the other responses: here a couple of suggestions that you may want to review and vote for to improve Lookup Issues functions:

https://jira.atlassian.com/browse/JRACLOUD-75314

https://jira.atlassian.com/browse/JRACLOUD-75018

Best regards,

Bill

Chase Bradshaw

Thank you all! I think I will default to using some of the other available smart values referenced in the links above until more are available. Largely, I think they will communicate similar concepts.

@Darryl Lee @Bill Sheboy @Tom

nagisha.vasudev

Heyy!

I got a way of getting the fields populated.

If you use your browser's inspect tool for an already existing ticket, you would be able to find the key for Priority and Due Date.

Elaborating the steps for ease:

Land on to any ticket of your project.
Right click on your browser to open the Inspect>Network tool.
Refresh the page.
You will find a header name in the beginning like : https://xxxx.atlassian.net/rest/graphql/1/ where xxxx will be the name of your organization. This will be called in the beginning as soon as the page is reloaded.
Navigate to the Preview section of this particular call.
Keep expanding the arrows till you find fields.
Within the fields section, look for the keys of Priority and Due Date for your project.
And that's it, you are done! Pick up the keys and paste it in the automation rule.
You'll see the values assigned to the keys will get populated.