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 no longer populating in automated emails

Alicia_a9jjyu

We are using Jira v9.12.2 and we send out reminder emails based on the due date. However the value for the due date is no longer passing in the email.

Body— Reminder

Please provide requested details for

Issue key {{key}} Summary: {{summary}} by Due Date: {{dueDate}}

Thank you

we have tried {{issue.dueadate}} {{issue.due}} {{due}}

All the other fields populate without issue except the due date.

Thank you

Accepted answers

All comments

Kalyan Sattaluri_iinm1n

Hello @Alicia

Was it working and suddenly stopped?

Please try --> {{issue.Due date}}

There is a space between Due and date.

Alicia_a9jjyu

About 2 months ago, the automation rule began to error on the due date, so I removed it. Now that I’m trying to leverage it again the value is blank.

{{issue. Due date}} did not work.

Kalyan Sattaluri_iinm1n

Hello @Alicia

Its {{issue.Due date}} Not {{issue. Due date}}

Also, if your set up has a customfield also called Due date, apart from the default field.. and you are using the new field... then you need to reference the field using customfield value.

Do you know if you have more than 1 Due date field?

As a test,

Open Jira
In new browser tab, put below url, replace bolded part with your jira instance and an issue key of an issue where Due date field is populated. Hit enter.

https://yourdomain.net/rest/api/2/issue/ISSUEKEY?expand=names

If you see a response, copy all JSON to a notepad, Cntrl+F to find the date which was entered in the issue and find the field name beside it.
Also, scroll all the way down and it will have a list of all fields available for this issue, scan that list as well to see any occurences of "Due date" and if there is any reference to custom field..

Please see below link for more details on above steps:

https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

So that may be another reason why you are not seeing this value populated even though it looks like issue has it.

John Funk

Hi Alicia,

You say "We are using Jira v9.12.2" but this post says you are using Cloud. Which platform are you on? And can you share a screenshot of your actual rule?

Alicia_a9jjyu

Seems to be in issue only when I use {{#lookupIssues}}. If I run automation to add the due date to a comment, single email, description works fine.

John Funk

Once again, can you share the actual rule?

Kalyan Sattaluri_iinm1n

As John has mentioned, please share actual rule.

Your original post did not mention lookupIssues. You tagged it as Cloud but we deduced it DC/Server.

Just FYI- In DC Edition, lookupIssues DOES NOT return all field values like in Cloud. So {{lookupIssues.Due Date}} will not return anything and is expected behavior.

Help us help you by sharing details of what you are trying to do and actual rule screenshot so we can help see if there are alternatives to get this data instead of relying on lookupIssues.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

automation