Hi
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
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?
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Once again, can you share the actual rule?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Alicia
Was it working and suddenly stopped?
Please try --> {{issue.Due date}}
There is a space between Due and date.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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,
https://yourdomain.net/rest/api/2/issue/ISSUEKEY?expand=names
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.