Issue Summary

When using the field value changed trigger within automation rules and searching for fields within the rule editor, only the first 50 options are displayed. In certain cases, a large number of custom fields might match the search text in which case you can't select the required field.

• Steps to Reproduce

• Create a large number of custom fields that share the same characters. Ensure you create atleast 51+
  1. out
  2. opt-out
  3. route
  4. old route
  5. ...
  6. ...

              55. OU

• Create an automation rule and select field value changes as the trigger
• Try to find the 55th field using the "ou" characters

Searching for "ou" will return the first 50 items in the list with no way to expand them. Trying a variation like "OU " ( with a space after the character ) will not return the 55th option either.

Expected Results

You can search for all fields that have the search character within them

Actual Results

You can only see the top 50 results with no way to expand on them:

Workaround

There is a possible workaround where we can set the field by editing the automation rule JSON and importing it back into the site,

• Navigate to Settings > System > Global automation
• Create a test/template rule that use the field value changed trigger
• Add some test action to log a value or create a variable
• Save the rule
• Export the rule to JSON
• Edit the exported JSON file using an editor
• Find the trigger section with the JSON and edit the value for the field to the required field
   
• Save the file and import the rule back into Jira

Please note that having multiple fields with the same name might still cause issues since the field is selected by name. The only workaround in that case would be to rename one of the fields so values are distinct.