Recommended Free Tools
When a Jira automation rule appears to fail, start with its audit log. Then test the trigger, inspect the smart values the rule actually receives, and compare its actions with the issue’s history. A controlled run using a Manual trigger or a copied rule can help isolate the fault without risking unwanted changes to live issues.
How to test a Jira automation rule safely
- Define one expected result. Choose a representative issue and record the event that should trigger the rule, which conditions should pass, what action should occur, and the expected final field or status. This makes it easier to compare the run with the issue’s history.
- Check the audit log. Open the rule’s audit log and inspect the entry at the time of the test. Check trigger details, condition results, action outcomes, and errors. Atlassian recommends checking the audit log first in its Cloud guide to debugging an automation flow.
- If no entry appears, investigate the trigger. Confirm the trigger type, scope, and filters, and make sure the test event matches them. No entry points first toward a trigger that did not fire; an entry can show that the rule ran but stopped at a later condition.
- Use a controlled run. If the rule could make unwanted edits, copy it and disable the production version while testing. Alternatively, use a Manual trigger on a known work item. Atlassian also documents a Scheduled trigger as a way to execute a test flow. See its debugging guidance.
- Log the values before the failing step. Add a temporary Log action immediately before the suspect condition or action. Include the relevant smart values, field identifiers, and values the action is meant to set. Run the test and read the log output in the audit record; remove the temporary logging when finished. Atlassian explains automation actions, including Log and Re-fetch work item data, and how to test smart values.
- Compare the log with the issue’s result. Check the issue history and current state against what the rule logged and what it was expected to do. If the values look correct but the action did not succeed, use the audit error to investigate configuration, permissions, or workflow constraints.
What to check when the rule did not trigger
First establish whether the audit log contains a run for the event. If it does not, focus on the trigger configuration and filters rather than debugging a later action that never ran. Check the expected event type, project or issue scope, and any trigger criteria. For Jira Data Center, Atlassian’s troubleshooting guide for rules that are not triggered also covers event and cluster-node diagnostics. Node-level checks are Data Center guidance, not Cloud steps.
As an Amazon Associate I earn from qualifying purchases.
How to diagnose unexpected smart values
A condition or action can behave unexpectedly if a smart value resolves to an empty or different value than expected. Use a Log action to print the value immediately before the step that uses it. For field paths you are unsure of, check Atlassian’s guide to finding a smart value for a Jira issue field and compare the path with the audit output.
Refresh issue data when a rule changes and then reads an issue
In a flow that edits an issue and then reads it again, the {{issue}} smart value may still reflect the values from the start of the flow. Add a Re-fetch work item data action before the later read when refreshed values are needed. Atlassian documents this behavior in its Jira automation actions reference.
#1 Best Overall
What audit errors and failed actions can mean
Use the specific audit error to guide the next check rather than treating every failed action as a trigger problem. Atlassian’s Cloud troubleshooting examples include deleted custom fields and incomplete field values; its guide to finding the root cause of an audit-log error explains how to investigate those cases. Also check whether the rule actor has the permission required for the action and whether the workflow allows the requested transition.
For a transition that does not reach its destination, log the resolved destination value and check that the workflow permits a transition from the issue’s current status. Atlassian’s transition troubleshooting guide covers these checks.
How to check an incoming webhook rule
A successful HTTP response from a webhook sender does not by itself prove that the Jira rule ran. Look for a corresponding audit-log entry and inspect the recorded trigger payload. If the expected run is missing, use Atlassian’s webhook trigger verification guide to check the trigger and payload.
Cloud and Data Center checks are not interchangeable
The controlled-test, smart-value, audit-log, and action guidance linked above is for Jira Cloud unless the linked page says otherwise. For Jira Data Center, use the Data Center troubleshooting guide for missed events and cluster-node checks. Do not apply its node-specific diagnostics to Cloud.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
