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; } } }

Show due date on automated e-mail

Phillip Bucknell

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,

email Jira.PNG

Accepted answers

All comments

Trudy P Claspill

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?

Emre Bodur

Please check this thread: https://community.atlassian.com/t5/Automation-questions/Due-Date-and-Priority-smart-values-are-blank-in-automation-email/qaq-p/1569860

Phillip Bucknell

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)

email Jira2.PNG

Phillip Bucknell

Hello Emre, Many thanks. Which of all the replys do I focus in ?

Phillip Bucknell

I am seeing that it is not supported yet?

Emre Bodur

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.

Bill Sheboy

Hi @Phillip Bucknell

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:

using a webrequest in your rule, call the Jira Cloud REST API for a JQL search, using the JQL replacing your Lookup Issues call
use text and list functions to parse the response into a list for the email, perhaps with a created variable for intermediate results, and using markup tagging

Kind regards,
Bill

Emre Bodur

@Phillip Bucknell Totally forgot, this workaround from @Bill Sheboy is the best way to go. The ugly version would be abusing the fixVersion field.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud