Issue Summary

Jira Automation audit logs fail to display branch execution details when using Conditional Branching with the execution mode set to "First match". While the automation actions (such as adding comments or creating tickets) execute successfully, the audit log only shows the trigger and initial actions, omitting the full branch path and subsequent actions.

Steps to Reproduce

1. Create a Jira Automation rule with a trigger (e.g., Manual trigger).

1. Add a Conditional Branching component.

1. Set the execution mode of the branch to "First match".

1. Add one or more conditions and actions within the branch (e.g., "Log action" or "Add comment").

1. Trigger the automation rule so that one of the branch conditions is met.

1. Navigate to the Audit Log for the rule and inspect the execution entry.

Expected Results

The audit log should display the full execution path, including the branch entered, the condition that matched, and all actions executed within that branch.

Actual Results

The audit log shows the trigger and any actions outside the branch, but the branch execution details and internal branch actions are missing from the log display.

Workaround

Change the execution mode of the Conditional Branching component from "First match" to "Any match". This allows the audit log to correctly record and display the branch execution details.