Problem

Customers with over 30 Conditions in their automation rules struggle to find the exact condition that caused the automation rule to skip performing operations on an issue. The Log action component is a workaround, but automation rules are limited to 65 components and one customer already has that many components

Suggested Solution

The "Issue fields condition" component should have an optional "label" field so the Audit log will be:

Issue condition - {label name}
The following issues did not match the condition:

Why This Is Important

This will make it easier to troubleshoot automation rules that have a lot of conditions by linking the audit log to the exact condition

Workaround

• Using a Log action component, but this is impacted by the limit on the number of components per rule.