Issue Summary

Automation condition for "Issue Type" does not display sub-task as selectable values

Description:
When configuring an automation rule and adding a condition to match on "Issue Type," the dropdown displays all standard issue types but does not include sub-task as a selectable value.

This prevents users from creating automation rules that specifically target sub-task issue types.

Steps to Reproduce

1. Go to Project Settings > Automation.
2. Create or edit an automation rule.
3. Add a condition: "Issue fields condition" > Field: "Issue Type".
4. Open the value dropdown for "Issue Type".

Expected Results

All available issue types, including sub-task issue types, should be displayed and selectable.

Actual Results

Only standard issue types are shown. Sub-task issue types are missing from the list.

Workaround

1. Using smart value:

{{issue.issueType.name}}

                                                                            (OR)

2. Use a “JQL condition” instead of the “Work item fields condition.” JQL allows for the specification of both standard and sub-task issue types. An example JQL query is:

issuetype = "Sub-task" OR issuetype = "Test subtask" 

Replace "Sub-task" and "Test subtask" with the actual names of your sub-task work types.

                                                                            (OR)

3. Alternatively, you can copy an existing rule that already includes the sub-task condition and modify it as needed.