Issue Summary

When a rule has a Scheduled Trigger with a JQL query and uses advanced components, custom smart values exported/imported between rule groups show inconsistent data hydration. Each issue returned by the JQL query runs in its own branch execution, but the data is being incorrectly mapped — values belonging to one issue are being hydrated into another.

Steps to Reproduce

 1.  Create a rule with a Scheduled Trigger and configure a JQL query.
 2.  Add a Create Custom Smart Values action to the rule.
 3.  Export the custom smart value and import it into the next rule group.
 4.  Add a Log action to output the custom smart value.
 5.  Trigger multiple simultaneous runs and observe the audit log output.

Expected Results

Each branch execution should maintain its own isolated context. The custom smart values created for a given issue (e.g., Issue X) should only be accessible and hydrated within that issue's branch execution. Data should never leak across branches, the log action should consistently print the correct smart value for its corresponding issue.

Actual Results

Under concurrent execution, custom smart values are being incorrectly mapped across branch executions. Data belonging to one issue (e.g., Issue X) is appearing in the context of another issue (e.g., Issue Y), and vice versa. This results in unpredictable and incorrect output, making the rule unreliable when processing multiple issues simultaneously.

Workaround

There is currently no workaround when using advanced components with custom smart values that are exported and imported between rule groups. As a temporary measure, consider one of the following alternatives:
•  Use the available built-in smart values directly, without creating custom smart values.
•  Create a new rule without advanced components.