Compare Epic's due date with all child due dates

[Maurice Beuting]

Dear community, 

I need your support. 

I'd like to create following rule: 

1. Every Thursday 
2. Lookup issues with some filter criteria
3. and check if the due date of child tickets is greater than the due date of the parent epic. 
4. Then send ONE email with all epics that have child issues which exceed the epic's due date. 

I tried the condition the following condition but It did not work. 

{{lookupIssues.parent.dueDate}} is lower than {{lookupIssues.dueDate}}

Any clue how to solve that? Thanks! 

[Vishal Biyani]

@Maurice Beuting 

I wrote this sample rule. See if this gets you going. Assumption is if any of the child issue has a due date > than parent, then it needs to be flagged.

Therefore, I used max to simplify the logic.

[Maurice Beuting]

Hi @Vishal Biyani,

thank you, that check works. But with that rule, all lookup issues are displayed in the audit log. Do you know how to add only those issues that correspond to the condition? 

Thank you! 

[Vishal Biyani]

adding this condition

{{#lookupIssues}} {{ if( due date.isAfter(parent.due Date) ) }} {{key}} {{parent.key}} {{/}}

gives True if issues due date is after parent due Date otherwise it does not print anything.

This logic you can build in email template to send issues that match the condition

[Vishal Biyani]

@Maurice Beuting 

There was slight error in the above. use this and you will get the required issue keys.

{{#lookupIssues}} {{ if (due date.isAfter(parent.due Date), key) }} {{/}}

If this helps you, please accept the answer so that others can also benefit

[Maurice Beuting]

thank you, Vishal!
 
If the condition matches, the output works fine. But for those issues the condition does not match, empty rows are displayed in my email output, screenshot below: 


Is there something like an "else function", so if the condition does not match, do not create a row in the table? 

and secondly, I'd like to have a scheduled trigger and not a manual trigger. If I just replace it, the branch reports an error like no issues found. 

Do you know how to fix that? Thanks!