Automation For Jira only lists the first 50 versions in the "Issue Field Condition" component

Issue Summary

Automation For Jira only lists the first 50 versions in the Issue Field Condition component, even though there are more available.

Because of that, when we have 50+ versions (Projects > Releases), the Fix Version/s field in the Issue fields condition does not show all the options in the “value” dropdown.

Additionally, the dropdown ignores the query typed by the user to search for a specific version. As a result, even if we type the actual version we are looking for, this version will never be found if this version is located after the first 50 versions.

Steps to Reproduce

1. Create a JSW project. Go to Projects > Releases. Create 50+ (minimum 50) versions.
2. Create a simple A4J rule to fetch those versions and set them in the "Fix Version/s" field.
   

Expected Results

All Versions should be displayed in the dropdown. Also dropdown should list the 'matching' versions as per the input entered.

Actual Results

A4J displays only 50 versions. The versions entered after 50th are omitted.
Dropdown does not list the versions 'matching' the input characters. It just lists the versions irrespective of the input and we need to scroll manually to find the required version. This would be exhaustive when there are 100+ versions in the dropdown.

Workaround

Note that this bug only occurs when the rule is configured with a scope limited to one project:

• If the rule is configured to be executed on all projects, the bug does not occur
• The reason behind this behavior difference is because Automation For Jira uses a different Jira REST API end point, depending on the scope of the rule

The workaround consists in creating an automation rule with the Scope set to All projects (since the version dropdown search works with this scope configuration), and to add an "issue field condition" block so that the rule is only executed for issues that belong to a specific project.

Please note that this workaround can only be used by Jira Administrators, and not by Project Administrators. That's because for a rule to be configured on all projects, this rule needs to be configured via the page ⚙ > System > Automation Rules, and such page is only accessible by Jira Administrators.

Please find the workaround steps below:

• Log into Jira as a Jira Administrator
• Go to the page ⚙ > System > Automation Rules
• Create a new automation rule with the configuration below:
  • Go to the Rule Details page and set the Scope set to All projects
    
  • Add the trigger of your choice
  • Add an "Issue Field Condition" block with the Project field set to the project for which you need the automation rule to be executed
  • Add another "Issue Field Condition", used for the version field. Verify that now, if you type a specific version, that version will be found and other versions will be filtered out: