Automation Rules with Two Branches Not Working As Expected.

Nicole Gosling_hjfw3r

Hi.  I am trying to modify an existing automation rule (AR) that has been working since it was created three years ago.  

This scheduled automation rule is runs every one hour and retrieve records where the "issue type equals Epic and project equals CC and status equals Invoicing and Approvals."

If all of the stories linked to the Epic are in "Done" or "Completed" status, the Epic transitions from "Invoicing and Approvals" to "Construction and Commissioning" status. 

 

 

I need to add a new condition to this rule that checks if the Operations Contact field is empty.  If it is not, the Epic transitions from "Invoicing and Approvals" to "Construction and Commissioning" status, just like the current AR does.  However, if the Operations Contact field on the EPIC is empty, then the Epic status doesn't change and an email is set to a group mailbox to populated the Operations Contact field.

I have read multiple knowledge articles, Atlassian documentation, but I can't find an resolution to my issue.

I made the following AR configurations but can't seem to get them to work properly.

1) If/Else - it would send email for Epics where the "Operations Contact" field was populated. I read the If/Else functionality can be tricky so I tried simpler approach (#2)

 

2) Multiple Branches - in addition to the conditions in the current automation rule, I add a check for the Operations Contact.  This one was looking promising however when I was digging into the audit logs I noticed that an email was sent for an Epic that had open stories and no operations contact.  Because I used "And" and not "Or" I would have expected the Epic to not pass the first condition in the second branch and do nothing.

Any help you can offer is greatly appreciated.

 

Thanks,

Nicole

Bill Sheboy

Hi @Nicole Gosling 

I would expect the updated rule you show with the If / Else block to work for this scenario, although the branch on current issue is not needed...and neither is the condition on the Else: you could just assume the field is empty.

Without changing anything, would you please post an image showing the audit log details for the rule execution which did not work as you expect?  That may provide some context to help explain the symptom.

 

Regarding multiple branches, I would not try that for your scenario.  Such branches execute in parallel and so it will be difficult to diagnose what is happening for any timing-related problems.

 

Kind regards,
Bill