Issue Summary

Automation For Jira only lists the first 50 issue types in any component, even though they are more than 50 types in the project the rule is configured for.

Some examples of components that are impacted by this bug are listed below:

• the Edit Issue action
  
• the Create Issue action
  
• the Issue Field Condition condition
  

Steps to Replicate

• Create more than 50 issue types and add them to an issue type scheme associated to 1 Jira project
• Configure a new automation rule and set the rule scope to that 1 Jira project
• Use the trigger of your choice
• Add an "Edit Issue" (or "Create Issue") action
• Select the "Issue Type" field as a field to be set by this action
• Scroll down in the value dropdown to look for any issue type above the 50 limit

Expected results

All issue types should be found in the dropdown menu

Actual results

• Any issue type that is above the 50 limit is missing from the dropdown
• Directly typing the missing issue type in the dropdown does not help either, as no match is found

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 issue type dropdown search works with this scope configuration), set the issue type, save the rule, and change the scope bask to 1 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 to All projects
  • Add the trigger of your choice
  • When adding any component (action, condition...) that has a dropdown for the Issue Type field, all the Issue Types will be displayed as illustrated below:
    
  • After the rule is saved, change the scope of the rule back to 1 single project