Issue Summary

Unable to see all sub-tasks on "Create Sub-Task" action when a single project is within scope of the rule and there are more than 50 issue types for the project.

I was able to replicate the issue and it is limited to when a single project is in scope of the rule. Jira will reach this endpoint to fetch the issue types:

<JIRA_BASE_URL>/rest/api/2/issue/createmeta/10000/issuetypes

• It is limited to 50 on the response:

{maxResults: 50, startAt: 0, total: 87, isLast: false,…}

• That causes only the first 50 to be considered and it causes Jira to provide the sub-tasks found within that subset of 50. There are no subsequent calls to get the rest of the elements.
• Even if you type the exact Sub-Task Issue type in the box you'll get an error "No results found".

This is reproducible on Data Center: yes

Steps to Reproduce

1. Create a project with at least 50 issue types.
2. Create one or more sub-tasks issue types associated to the same project.
3. Create a rule with any trigger and access the Create Sub-task action.

Expected Results

You're able to select or type any sub-task within the scope of the project when you click the box to select the sub-task.

Actual Results

You will only see the sub-tasks that are contained within the first 50 issue types created for that project.

Workaround

The first alternative is to reduce the number of issue types within scope of your project.

For the second alternative, if you have any other project added to the scope Jira will change the behavior and send a call to this endpoint instead:

<JIRA_BASE_URL>/rest/api/2/issuetype

• The response here is not limited and will allow you to select any sub-task issue type from your instance.

In summary, you can add any other project to the scope of the rule to bypass the limitation. I'll be opening a bug on this behavior but I wanted to let you know about this workaround.

You could potentially create a very basic project just for this purpose and this workaround would take effect.