Provide the ability to run Jira Automation rules and branching sequentially

Problem

There are scenarios where Jira Automation rules are needed to be run sequentially or in serial. Currently rules and branches run in parallel, meaning in certain scenarios elements further down the automation rule which are dependent of the outcome of a specific branch are fired too early and a false positive or failure occurs.

Scenario or Use Case

An example of how the current behavior can impact an automation rule can be seen in the below example (extremely high level overview):

1. Trigger a rule when the request participants (Jira Service Management) are edited
2. Re-fetch the data and using Advanced branching loop through each value
3. Match these values against a regex condition
4. Set a custom label when this regex condition is met
5. Once the above for each action on the Advanced branch completes, check if the label is present
6. If the label is present, take an action ie post a comment

In the above scenario, it's possible that while points 2, 3 and 4 are happening, in parallel the check in point 5 is completed. If the user is at the end of a longer list of participants, it's possible that the action (adding of the label) was not completed at the time the presence of it is checked.

Due to this, the rule will either provide a false positive or fail. Being able to adjust in which manner the automation rule is running (serial vs parallel), we can provide an improved user experience, expanding on the ability to create new rules similar to the above and a consistent experience.