Debugging automation rules

There are many reasons why automation rules can, and will, fail. These could be due to underlying configuration changes within Jira, or the rule author may not have anticipated an edge case scenario when planning and implementing the rule.

When rules start failing, it is necessary to understand what caused the rule to fail and to either fix the underlying cause or to adjust the automation rule to take into consideration the changes that caused it to fail.

However, debugging is not only about finding and fixing deficiencies in your automation rules or underlying Jira configurations. We can use the same techniques during planning and developing to ensure that we deliver robust rules that are likely to have a higher success rate.

In this section, we will look at how using the audit log for automation rules can help to identify issues and how we can make use of it when debugging our automation rules.

Firstly, let's take a look at the audit log...