Hello,
I am trying to include the Due Date in an automated e-mail of Issues as shown on the attached picture.
Why is it not working? Is there a work-around this?
Best regards,
Phillip,
As you have discovered, Lookup Issues does not support that field yet.
A work-around with built-in functions for automation for Jira is to:
Kind regards,
Bill
@Phillip Bucknell Totally forgot, this workaround from @Bill Sheboy is the best way to go. The ugly version would be abusing the fixVersion field.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Trudy,
It is a Daily Rule that gets sent at a certain time.
Although the email gets sent, the due date does not appear, although the rest of the issue content appears ( Summary and Assignee)
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.
Hello Emre, Many thanks. Which of all the replys do I focus in ?
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.
Hi,
yes, "lookup" is new to JIRA Cloud. The supported fields are limited and custom fields are not supported yet to give you a less shitty workaround :-)
Here is the documentation to "lookup":
https://support.atlassian.com/jira-software-cloud/docs/automation-actions/#Automationactions-Lookupissues
The only idea what I have for you is the following:
If you doesn't use the field "fixVersion", you can abuse this field for your due date. For this, create a trigger in JIRA Automation by listening to your field "due date" and copy this date to your "fixVersion" field. With this approach, you can use "lookup" to summarize a list of issues within one email by using the smart value {{fixVersion}}
Another smooth way is to use the API by requesting data from a third party application (Zapier or an own little app) to prepare this data for sending emails.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Phillip Bucknell
Welcome to the community.
Please explain what symptom you are seeing when you say "it is not working".
Also, can you show us the rest of the Rule you have constructed?
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.