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

Set up an email notification for a due date 7 days in the future

Brandi Myers-Shank

Hello,

I've done some research and found a few answers but can't seem to get my automation to run without errors.

I want to program Jira to send an email 7 days before the due date as a 7 day out reminder. I have it scheduled to run every day in the morning, what should my JQL entry be for the custom field "due date"?

Accepted answers

Mikael Sandberg

You would add this to your JQL to get issue that are due 7 days out:

due = 7d

Another option to do it is to use smart values to see if the due date is 7 days out, similar to this automation that I have that sends a reminder 90 days out:

Screenshot 2023-10-26 at 3.29.49 PM.png

The reason I'm using smart values is because the due date is not required and there are issues in the project that should not get the notification.

All comments

Mikael Sandberg

You would add this to your JQL to get issue that are due 7 days out:

due = 7d

Another option to do it is to use smart values to see if the due date is 7 days out, similar to this automation that I have that sends a reminder 90 days out:

Screenshot 2023-10-26 at 3.29.49 PM.png

The reason I'm using smart values is because the due date is not required and there are issues in the project that should not get the notification.

Bill Sheboy

Hi @Brandi Myers-Shank

Adding to Mikael's answer:

To whom are you sending this notification?

I ask that question because if you are sending this just to yourself, you may want one email that day, versus an email for each issue. Similarly if you are sending emails to assignees, they may want to only see their issues, not everything due 7 days out (possibly for other assignees).

You may adjust your rule accordingly if you want to handle these cases, using rule components like branching and the Lookup Issues action.

Kind regards,
Bill

Brandi Myers-Shank

Thank you both. The email would go to the assignee(s) of the issue.

Bill Sheboy

Brandi, your rule could be something like below. Please compare it to what you have to help identify the cause of the errors.

trigger: scheduled, but with no JQL
action: lookup issues with JQL to find issues meeting your criteria
advanced compare condition: check if there are issues to process, testing is {{lookupIssues.size|0}} greater than 0
advanced branch: to cover the distinct assignees for the issues
- smart value: {{lookupIssues.assignee.distinct}}
- variable: varAssignee
  - action: lookup issues again, with the same JQL from the earlier lookup, but adding AND assignee = {{varAssignee.accountId}}
  - action: email
    - you may send this to {{varAssignee.emailAddress}}
    - and the issues would be in the lookup, and you can get the fields as described here: https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Lookup-issues

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