Setting dueDate of Parent using lookupIssues.dueDate.max not working

[Peter McCann]

As shown in the above photos, I am triggering off a story or task level due date change, jumping into the parent, setting a variable called maxDueDate using the smart value {{lookupIssues.dueDate.max}} looking for the largest due date of the parent's child issies, and then use the edit work item field action to set Due Date to the {{maxDueDate}}. 


The intention here is if someone changes a story's due date, the epic always shows the max due date of it's children. 

Currently this does not work, but the audit log says the branch is executing. 

Can someone tell me why it does not execute? 

As a note, the use of "dueDate" is due to naming of the field in our implementation. Worrying is the smart values helper lookup menu cannot find the "lookupIssues.duedate" option, but it can find them for other "lookupIssues" in the variable creation step. 

Thanks for the help! 

[Bill Sheboy]

Hi @Peter McCann 

To use the {{lookupIssues}} smart value, you need to first add the Lookup Work Items action to the rule.

For your scenario, inside the branch as a first step, add this:

• ...
• branch: to parent
  • action: lookup work items, with JQL of
    • parent = {{issue.key}}
  • action: edit work item fields, to update the Due Date

Kind regards,
Bill