Custom field is not applicable for the current project

[Johannes]

Hello,

I am having the issue that when I am trying to search for tickets with specific content in custom fields I can not even select them in the basic search. The error message says "<customField> is not applicable for the current project".

What I have tried so far:

- changed the context of the custom field to match the project/issue type

- set the context of the custom field to be global

- check that a search template is set

- completed reindexing

- deleted the custom field and created a new one

It works fine for some of the (already existing) custom fields of this specific project, but not for others, but I have no idea why.

Does anybody know what the cause for this might be?

Thanks a lot!
Johannes

[Ozren Vojnovic]

Hello there,

Just had the same issue, so here's the solution in case anyone else wanders to here.

RESOLUTION

• Use advanced filter instead of basic

Very annoying, but at least it has a trivial solution :D

[Aurimas Brazaitis]

I found a solution when i choose issue type in the filter which actually has this field. For example: I have 2 issue types in the project, and only in one of them this field is being shown. When I choose in the filter only that issue type, then I am being able to select the field in the filter.

[Maxim Denisuk]

Heh, you will not believe but Advanced search works, if it replaces your naming to cf[....]...
----

So my example: I have extended my Field schema with custom fields named Location (there is a custom format).

When I'm trying to add this field to any filters (like search issue/filter board/etc..) I see the next thing:

But, when I switched to the advanced filter JSM replaced "Location" with jsm-variables like cf[...], and after this field worked correctly.

p.s. Ive tried to use "Location = ..." and JSM showed The operator '~' is not supported by the 'Location' field. 

[Maxim Denisuk]

I have the same issue & no idea how to fix it

[Aurimas Brazaitis]

I found a solution when i choose issue type in the filter which actually has this field. For example: I have 2 issue types in the project, and only in one of them this field is being shown. When I choose in the filter only that issue type, then I am being able to select the field in the filter.

[Walter Buggenhout]

Maybe some fields are hidden through the project's field configuration?

[Johannes]

Hi Walter,

thanks for your response.

No, the field is also added to the field configuration and not hidden.

[Johannes]

The strange thing is that I can add this field as a column to the project's queues but I can not filter for it in this queue.