Context

In Jira Automation, the "Field value changed" trigger currently displays a maximum of 50 custom fields in its selection dropdown. As a result, not all relevant fields are available for selection when configuring automation rules.

Workaround

• Export the automation rule as JSON, manually add the custom field ID for the desired field in the trigger, and re-import the rule.

• Alternatively, use scheduled or JQL-based triggers, which are less precise and may not fully meet our needs.

Impact

• Unable to select certain custom fields in the automation trigger, as they do not appear in the limited dropdown list.

• The limitation negatively affects the customers ability to efficiently manage and update automation rules, especially as their number of custom fields grows.

• The above workarounds are time-consuming and not sustainable for ongoing maintenance.

Suggested Improvement

• Remove or increase the limit on the number of custom fields displayed in the "Field value changed" trigger dropdown.

• Alternatively, provide a searchable or filterable field selection interface, allowing users to find and select any custom field by name or ID, regardless of the total number of fields.

• This enhancement would greatly improve the usability and scalability of Jira Automation for organisations with many custom fields.