Custom field not searchable in search issue page

[Emiliano Visioli]

Hi,

I have a custom field that is not searchable but I don't understand why.

The same field is configured also in a stage env and there it works.

The only difference is that in stage is configured for all projects and issues while in production is configured for specific projects and issue type but the search isn't enabled also if I try in all projects and all issue types.

The field, when filled, contains an issue key like PR-123 where PR is a project and it is a related issue type (that I've included in the custom field configuration).

What can be the problem?

Update: this field is still not searchable and also other custom fields created later have the same problems.

Considering that "Search template" is correctly filled, the only cause is the re-index not performed or there could be other causes?

Thank you,

Emiliano

[Nic Brough -Adaptavist-]

Hi Emiliano,

This will happen when a custom field does not have a "searcher" associated with it.

As an admin, go to admin -> issues -> custom fields and find the missing field in the list of fields.  Click "edit" (not "configure") and you'll see the field name, description and searcher, which I suspect will currently say "none".  Select a searcher from the drop-down, save it, and then try the search again.

The search will not give you the right results on existing data until you have run a full re-index, but it will work for new and edited issues after you've added the searcher.

[Emiliano Visioli]

Hi, actually is already set on "Free text searcher".

[Emiliano Visioli]

Do you have other suggestions?

I have the same issue with a new custom field just created, it has "Multi select searcher" as search template but in the search issue page it's inactive :(

I've also checked here:Can't search on custom field | Jira | Atlassian Documentation but all these settings seems ok to me.

[Nic Brough -Adaptavist-]

Did you re-index after adding the searcher?

[Emiliano Visioli]

Hi I didnt' add the searcher as it was already set.

Excluding the reindex (I'm checking when the last ran), are there other possible causes?