Audit Jira Automation Runs
Use automation run logs to trace the trigger, evaluated conditions and attempted actions. A successful execution label does not prove the workflow produced the business outcome you expected.
Step-by-step guide
Check access and scope
You need administration access to the relevant automation scope. Preserve useful investigation details promptly because audit retention is limited.
Find the automation run
Open the relevant automation flow or rule and its audit log.
Match trigger time
Find a run matching the issue and expected trigger time.
- Worked example: If a security-review request was not assigned, check whether the trigger fired, whether its field condition matched and whether the actor could edit the issue. Avoid replacing the entire flow before identifying the failing step.
Expand execution steps
Expand each execution step and inspect conditions and errors. Expand each step to distinguish a false condition from an action error; compare the run timestamp with issue history.
Compare issue history
Compare logged changes with the issue history.
Test the narrow correction
Test a narrow correction and document the cause and owner.
Verify the result
A controlled test changes the intended record and the log explains the resulting action.
Common mistakes
Avoid the main failure mode
No run entry can indicate an incorrect trigger or filter rather than an action failure. Start at the beginning of the execution path.
Check the handoff edge case
A success status can still accompany an unintended business result. Compare actual issue changes with the intended outcome.
Sources and verification
Based on product documentation checked on 2026-10-24. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.