With automation, can we restrict copy due dates from stories if not all stories fill the same?

[Srinivsarao Mutyam]

I have a question regarding automation rule that I created previously.

Scenario: When an Epic contains 4 stories, each with a different DUE DATE filled in, the most recent date should be copied to the Epic along with its linked CLI.

To extend this rule: If out of the 4 stories, one or two stories do not have the due date filled in, then the Epic and its linked CLI should not have their due dates filled in until all stories have their due dates filled.

Thank you 

[Trudy Claspill]

Hello @Srinivsarao Mutyam 

Whenever asking for help with an automation rule please provide a copy of the rule. We need that information in order to give you good advice on how to change it to meet your needs.

I believe it would be possible to add a check to confirm that all the child stories have a due date value before copying the earliest value to the Epic.

Also, what do you mean by "linked CLI"?

[Trudy Claspill]

In rule 1 after your Advanced Compare add another condition like this:

Where I used "duedate" in the JQL you would substitute your custom date field.

This condition will ensure that there are no child issues of the Epic where the custom date field is empty.

[Srinivsarao Mutyam]

"CLI" is nothing but another project Issue which actual Epic(parent) linked

Here is the sample rule: 1 for ETA UAT (Due Date) field copy form chiled to Parent(Epic)same projectA,

Rule:2 for ETA UAT (Due Date) field copy form Epic to linked issue(project B Issue)