Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Due Date and Priority smart values are blank in automation email

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?


<li><a href="{{url}}">{{key}}</a> - {{summary}} - {{}} - Due - {{issue.duedate.fullDate}} </li>

3 answers

1 accepted

0 votes
Answer accepted

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; 

This post will be updated once custom fields are included;

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


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 :  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.

Hope this helps :) 

These steps definitely worked for me!

Attaching a screenshot for your reference.



Hi @nagisha.vasudev -- Welcome to the Atlassian Community! could use the steps in this how-to article for finding smart values:

Best regards,

0 votes
Darryl Lee Community Leader Jan 04, 2021

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

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

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

Darryl Lee Community Leader Jan 04, 2021

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

That's unfortunate.

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:

Best regards,


Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Automation

New to Jira Automation - goodbye Cron (sort of), hello new project created trigger, new additions to

Hey Everyone! Simeon from the Automation team here. I'm delighted to share some new features and improvements that we are shipping to Jira automation (Cloud only). Firstly, @Sam Harding&nbsp...

2,873 views 10 23
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you