Regarding the execution order of automation rules

[Moriarty Chiu]

In my project scenario, there is a story that consists of three sub-tasks (A, B, C). A blocks B and C, while B blocks C. When the status of A changes to "Done," the status of B should be changed to "To Do" (C's status remains unchanged because it depends on both A and B being "Done"). Similarly, when the status of B also changes to "Done," the status of C should be changed to "To Do."

I have created the following two rules. These rules satisfy my requirements, but it seems strange that when one rule is executed, the second rule does not execute (there is no execution record in the audit log of Rule 2). For example, when A changes to "Done," both B and C automatically change to "To Do." However, if I manually switch C's status from "To Do" back to "Blocked" while A is already "Done" and B is still "To Do," then switch it back to "To Do," Rule 2 executes as expected. In the audit log, we can see that the rule has been executed and C's status has changed to "Blocked."

I would like to know why this happens and if only one of the rules is executed when two issues transition, and how I need to improve my rules if I want to fulfill my needs.

[Moriarty Chiu]

So, has anyone come up with a solution yet?