Help with an automation rule

Question

What I need is the rule to go through all new work items in a project and if it doesn`t find a due date on one of these it should shoot a mail back to the reporter so he can add a due date.

I want to start with the fact that our Jira instance does send out mails normally but just doesn`t do so for this automation.

I have this :

* WHEN :  It`s scheduled to run at 10 am every day. The JQL reads as follows : project = MYPROJECT AND duedate is EMPTY
* FOR current work item :

* THEN : Send mail :

But this doesn`t seem to work.

Any help is appreciated!

Thank you!

Mihai

Mihai Vasile · Answer

Hey Jeroen,

I can`t require it at launch because I need this run mostly for subtasks that are automatically created and that need a different date from their parent.

But thank you! This would have been the easiest and cleanest way to resolve the problem.

Kind regards,

Mihai

Bill Sheboy · Answer

Hi @Mihai Vasile -- Welcome to the Atlassian Community!

I agree with the suggestion that requiring the Due Date when the work item is created might be better than sending reminders later.

When you still want to send reminder emails, please consider sending one email per reporter per day in case they submit multiple work items.  This knowledgebase article describes a similar scenario to use as a template.  You may want to adjust the JQL for the Lookup Work Items action to only check work items created in the last 24 hours...and which are not already resolved.

https://support.atlassian.com/automation/kb/automation-rule-to-send-single-email-for-all-issues-per-assignee-due-next/

I also recommend pausing to understand why the Due Date field is required in your process.  That is, what problem are you trying to solve?  This may reveal other possible improvements and mitigate unintended consequences.  (For example, to bypass a required field, people may enter a dummy value when they do not have a date yet, and then clear the value later.)

Kind regards,
Bill

Jeroen Poismans · Answer

Hi Mihai,

The other community members already answered your exact question, so that is covered.

Why don't you force the due date at creation of the work item OR require it on a transition where you really need to have that due date?

This way you fix the behavior at the root instead of patching it afterwards, resulting in a better user experience because your user does not have to revisit and correct?