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

[Suvarna Gaikwad · Accepted solution]

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.

[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]

@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! 

[Hadas Hamerovv]

I did exactly that and the automation works like charm. (few issues do not show the button I expect, therefore I wanted to search to see the status of this field however I cannot.

What to do to see all the issues where this field is populated?

[Bernice]

@Hadas Hamerovv I am glad that you were able to use the automation rule. With respect to your query, we need to unhide the field in order to see all the issues.

To explain the reason why we did not provide the option in JQL is because, all users in the project have permission to search issues in the issue navigator so if we allow the permission to display these fields, then any user can search for this field from the issue navigator(advanced issue search). Hence we have hidden it everywhere.

So workaround at the moment is to click on "show" for this field only and then export these issues(if required). Once the list of issues is taken, you can click on "hide" again. 

[Hadas Hamerovv]

Thanks Bernice for the explanation. Sounds like a reasonable reason. 
the workaround however won’t do for me as I have to scan those issues periodically. Having to go to the field configuration each time and again hide and show the field is a hassle. 

there must be an easier way. I a, using scriptrunner. Do you know of a command I can add to the jql via scriptrunner which allow getting a result while the field is hidden? Or if not, maybe some kind of automation that could generate the list ?

[Bernice]

@Hadas Hamerovv I do not have expertise in third-party addons which support this. It would be great to involve the vendor to have it checked. On checking online, I could see some add-ons like Canned Search Gadget and JQL Search Extensions for Jira - the JQL extensions but then we will be able to confirm only by checking with the vendors directly as I have limited scope in that area.

[Bernice]

@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]

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.