-
Type:
Bug
-
Resolution: Invalid
-
Priority:
Low
-
Component/s: Condition - Advanced Compare
-
None
-
Minor
-
Confluence
Issue Summary
Automation rules exit when the first condition is evaluated as false
Steps to Reproduce
- Create an automation rule;
- Set Manual trigger from page as the trigger;
- Add an Advanced compare condition for example, "page.labels"(smart value) contains label-name;
- This condition should be evaluated as a False
- Add an action, for example, the Change page status and set any page status;
- Add an Advanced compare condition for example, "page.labels"(smart value) does not contain label-name;
- This condition should be evaluated as a True
- Add an action, for example, the Add label and set any label;
- Save and then run the automation rule from any page;
Expected Results
- If the first condition evaluates as False, the next condition(in this case, True) should be verified and then execute the defined action.
Actual Results
- Once the first condition is evaluated as False, the rule exits and does not execute any further action. The Audit log displays "No actions performed"
Workaround
- Change the order of the Advanced compare condition however, given how the results are evaluated, this bug might keep happening.