Custom field value limits in automation?

[Pedro Lopez]

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 Claspill · Accepted solution]

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.

[Andrea_Lawrence]

I'm having this issue as well but the value I need is not showing up when I start typing it. It's not an option at all.

[Trudy Claspill]

Can you provide a screen image of what you see in the Automation rule, and the custom field definition showing the value available?

[Andrea_Lawrence]

@Trudy Claspill sure! 

Here are all of my Issue Types for this specific project:

I have an automation rule configured already with an IF condition for "External" but I want to modify the rule to add an ELSE condition (or another IF) for "Internal".

Here's the step that exists already for External:

When I add an ELSE condition for Issue Type and type "Internal", my issue type is not appearing. In fact, none of my issue types for this particular project show up as options.

What I did notice though, originally the scope for my rule was multiple projects since I have a step that creates a ticket in another project. I duplicated the rule but changed the scope to a single project and then my issue types showed up.

I made the Else block with my Internal issue type and saved the rule (still with single project scope). Then I went to global automation settings and changed the project scope back to multiple projects and saved.

[Trudy Claspill]

That sounds familiar - a problem with selecting issue types in a Condition when the rule is scoped for multiple projects.

I'm not currently finding where I read about that before, though.

[Pedro Lopez]

Nope, that was the issue! All my values are in text, so the values at the bottom of the alphabet were being excluded. Typing in the first letter does cause it to appear, so now I could find the missing values. It was all on my end. Thanks for the fix! I appreciate it.