nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Search by radio button custom field won't give results

Hadas Hamerovv

I've created a looped workflow that works like charm.

It is based on a custom field named 'open question'.

users can ask for more info if the field is empty and others can answer if the field is set to 'Yes' (radio button)

Post function and condition works like charm.

However when I search with jql for the issues with open questions I receive no results.

Can someone explain what's going on?

The JQL is: "Open Question[Radio Buttons]" = Yes

I also tried: "Open Question[Radio Buttons]" is not EMPTY

Accepted answers

Suvarna Gaikwad_3o435r

Hi @Hadas Hamerovv The second JQL you mentioned indeed works. I tested it on my instance.

"Open Question[Radio Buttons]" is not EMPTY

The only possibility I could think on why JQL is not working as of now is to check if there are any spaces (leading or trailing) in custom field name you created or any duplicate field names.

All comments

Suvarna Gaikwad_3o435r

Hi @Hadas Hamerovv The second JQL you mentioned indeed works. I tested it on my instance.

"Open Question[Radio Buttons]" is not EMPTY

The only possibility I could think on why JQL is not working as of now is to check if there are any spaces (leading or trailing) in custom field name you created or any duplicate field names.

Hadas Hamerovv

NO, this is not the case. In fact jira itself autocompletes the JQL so there is no error in the naming.

Bernice_roh8f5

@Hadas Hamerovv The reason why you do not see these field values while searching is because you have hidden this field from the field configuration section.

In fact, the option to hide will only remove the field value from the issue view screen and from the Issue navigator page, so you will not be able to search for the field in JQL queries.

The only way to be able to search for these field values are by any of the below options

- Configuring the field to show in the issue view again

- Must be checked in Jira DB (if server version)

Hope this helps!

Hadas Hamerovv

But I don’t want the field to show. Can I remove it from the screen and still change its value behind the scene with automation?

Bernice_roh8f5

Unfortunately no, because your screen must have this field even for the automation to trigger it or you may receive an error stating that the field is not available in the screen to make these changes.

Hadas Hamerovv

This is such a bad logic.

How can we than store values that serve automation without loading the screens with fields that the users has nothing to do with?

Bernice_roh8f5

@Hadas Hamerovv - You can still hide the field in the field configuration and have the field in the screen, then, use the automation to add values to this field. But you must make sure that the rule actor is Automation for Jira.

As your initial query is only about searching the issues in JQL for this hidden field with the value yes, we need the field to be available on the screen Hope this clarifies!

Let me know in case of any help!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud