Lookup issues in automation rules then display Due Date field value in email

[VVC]

My automation rule sends email with a list of issues report from the lookup. Though other fields data is visible in the email but the due date value is never returned.

It looks like a known issue or limitation and did anyone had a workaround to display this field value in the list report via email from automation rules in Jira data center?

<table>
{{#lookupIssues}}
<tr>
<td><a href="{{url}}">{{key}}</a></td>
<td><em>{{created.format("MM/dd/yyyy")}}</em></td>
<td><em>{{duedate}}</em></td>
</tr>
{{/}}
</tbody>
</table>

[John Funk · Accepted solution]

Hi VVC,

Try using {{issue.duedate.shortDate}} or {{issue.duedate.longDate}} depending on how you want the date to appear. 

[VVC]

Hello @John Funk I was wondering if it actually worked for you, as this syntax didn't work for me when using the LookupIssues.

I have only 2 issues to report which had the due date and though the Issue key, Created Date fields are showing the results, but the due date didn't even with shortDate and longDate syntax. I did see some known issues with reference to due date field in the community threads and Atlassian support.

[John Funk]

Ah, sorry, I forgot that you were using Data Center. I don't think the duedate field works with lookupIssues there. See this: https://jira.atlassian.com/browse/JIRAAUTOSERVER-877

You might try copying the value to a hidden date field and then use that with your lookupIssues and see if that works.  It might just be Dates in general don't work, which would be a shame. 

[VVC]

"Created" Date field works with lookup issues but NOT due date. The due date field is being used by most issuetypes in our Jira and I will see if this is worth to go the route of creating another custom date field just to copy the due date then try using that in our lookupissues. Thanks for proposing this workaround.

[John Funk]

Hey @VVC  - Any update?

[VVC]

Hello @John Funk - We skipped the Due Date system field for now on our reports and just capturing only the Created system field value, which works fine. I haven't got a chance to test other custom date field types.