How do I build an automation to fill a "Due date" subtask field?

Question

I would like to run an automation that triggered when an issue is transitioned into the archive column. I would like all the "due date" fields from the issue and the subtasks  [child issues] within that issue, if empty, to be updated to the current date.

[I hope that made sense, I am very new to automations]

This is what I have created so far and it works when there is no "due date" field filled in for the issue, then both the issue and subtask get updated. BUT if the issue's due date already filled in, the automation does not update the cilld issue.

Thank you for your help!

Walter Buggenhout · Accepted Answer

Hi @candice.mackay and welcome to the Community!

Indeed. The first condition in your automation rule checks if the due date on your issue is empty and if this is not the case, the rest of the rule is not executed anymore.

Rather than using a simple condition, you should use an if ... else ... block instead, where you specify what happens in each scenario. The below example does not match your use case, but is an illustration of what it should look like:

You could set up a block that checks if the due date is empty, if so updates the due date field on your issue AND updates all the empty due dates on sub-tasks. And a second block that only updates the sub-tasks if the due date is not empty.

As an alternative, you might also move the condition on due date below the update of your subtasks. That way you don't have to repeat that part in the automation rule. So:

WHEN issue transitioned

THEN

-> Branch for Sub-Tasks: edit due date when empty

and - at the end - IF due date is empty, edit due date of story

Hope this helps!

Trudy P Claspill · Accepted Answer

Hello @candice.mackay

Welcome to the community.

Move the Condition for checking the parent issue Due Date and Editing that field to after the branch where you check the sub-tasks. Then the rule will run through updating the sub-tasks first, and then check if it needs to update the parent issue.

Make sure that those two components are outside of the branch after you move them.

Checking that Condition before the branch for the sub-tasks results in the branch never being executed when the Condition is not met.