Automation to update epic when fields are changed in issue sets values to none when new issue create

[Danielle Hutchins]

I have the below two automation rules setup that seem to work on their own; however, when new issues are automatically created upon transitions, the custom fields in the epic are reset back to none. 

1. Update Epic when fields are changed in child issues

• Allow rule trigger is not enabled

2. Update child issues when fields are changed in Epic

• Allow rule trigger is enable

Since the Allow Rule Tigger is not enabled in the first rule, I would assume that issues created through automation should not trigger the first rule to run. 

[Bill Sheboy]

Hi @Danielle Hutchins 

Without more details about your rule specifics, I suggest that "timing...is everything."  ;^)

The rule engine seems to queue execution of rules (and their component parts) asynchronously.  The Allow Rule Trigger is to prevent (or allow) overlapping rule execution, and it is not a one-stop, full solution.  So it can prevent a run-away race track condition, but it cannot stop triggering when enough time has passed (...I hypothesize).

For a better prediction on rule behavior, I suggest:

• map out what you want to accomplish
• check where there could be overlaps between rule executions
• confirm that the triggers will fire (or not fire) for each rule by making them unique

I have used custom fields (or comments) as semaphores to consistently manage rules creating events that other rules can catch in triggers...or to prevent them triggering.

Please consider posting the details of your rules so the community can provide any additional ideas.  Thanks!

Best regards,

Bill