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
Hello there,
Just had the same issue, so here's the solution in case anyone else wanders to here.
Very annoying, but at least it has a trivial solution :D
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Maybe some fields are hidden through the project's field configuration?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.