Custom field value limits in automation?

Pedro Lopez_nnvl4i

Hey all,

When creating a Automation rule in Jira, I am running into an issue with the "Issue fields condition" rule.

I made a Select list custom field with about 20 values. However, when I go into Automation and use the Issue fields condition, select the custom field I made, use the "is one of" argument, and select my values, only 15 of my 20 values appear. I need all values to make the Automation rule work. I am using this rule to assign Assignees to a ticket if the custom field contains certain values.

I have tried recreating the rule and recreating the custom field values to see if it would fix the issue. My 5 bottom values are the ones that do not appear in Automation.

Has anyone else encountered this issue? Is it a bug or does Jira place limits on the amount of values you can have in the Issue fields condition? Is there something I'm missing? Any help is appreciated!

Trudy P Claspill

Hello @Pedro Lopez 

Welcome to the Atlassian community,

Do you mean when you click in the field to select a value, only 20 values are initially displayed? If so, that is intentional. Jira will not display all options in a selection list by default when there are a large number of options.

You can start typing in some portion of the value you want to find to filter the list.

Example: here is a portion of a large selection list I have defined.

Notice that there are multiple values that include "a".

In an Issue Fields Condition, when I click in the field to select values, the list is automatically sorted alphanumerically, which puts the numbers first, and I get only 15 entries. At the bottom of the list I see only x value with "a" in it.

But if I type in "a", then I get a list of the values that include "a".

 

If you are not able to figure out text to enter to filter the list down to a set from which you can select your values, tell us more about the values in the list and what happens when you try to filter them.