Problem Definition

When running an Automation Rule with Branches, currently it is not easy to create a single Smart Value or Variable containing results from each Branch. This would provide a way to do that, as well as other potential uses between Rule Executions as a whole.

Suggested Solution

Provide a Smart Value that is remembered between Automation Rule Executions so that information can be shared between Branches of a Rule as-needed.

As an example, if this were to operate similarly to SQL Transactions - where each attempt to modify the Smart Value is instead recorded in a queue, before the queue is processed in order - it could retain the result of all executions regardless of order once complete.

The issue that is often faced with Branches trying to update something like a Custom Field is that one execution will overwrite another's changes due to their non-deterministic ordering.

This could provide an easy workaround for that issue as well, where the final value of the persistent Smart Value is written to the Custom Field once all Branch executions are complete.

Workaround

At this time, the only viable way to handle this is to not use Branches altogether.
One way to achieve this is to use Dynamic Looping with 2 Rules:

• How to create dynamic looping in Automation for Jira