Issue with Due Date clearing instead of updating in dependent tasks automation

Avi Morali

Hi everyone,

I’ve implemented the automation rule exactly as described in this article:
https://community.atlassian.com/forums/Jira-articles/Updating-dependent-task-s-dates-when-predecessor-task-date/ba-p/2816977

The rule mostly works as expected:

• It correctly detects the dependent (blocked) issues

• It updates the Start Date of the linked issues based on the triggering issue’s Due Date

However, I’m running into a problem with the Due Date of the linked issues:
Instead of being recalculated as Start Date + original duration, the Due Date gets cleared and becomes empty after the rule runs.

In summary:

• Start Date: updated correctly

• Due Date: wiped out instead of being set to the new calculated value

 

In the example below, ticket SERVIMPL-4227 is blocking ticket SERVIMPL-4228:

Could someone please advise how to preserve and correctly update the Due Date so that the original duration of the dependent tasks is maintained?

Thanks in advance for your help!

John Funk

Hi Avi - Welcome to the Atlassian Community!

When a field gets cleared out, it is usually because the value in the field is not valid. So it might be that the variable is not getting set. Add a log action to after the variable to see what it is. 

Also, you might want to put in a Re-fetch action right after the Trigger to ensure it has the latest information.