Custom fields on screens without any content will not be shown, even when explicitely present on the view screen of a ticket. Although it's logical to hide empty custom fields, there is one specific field I want people to be able to always see and they should be able to edit it, but never make it mandatory. Adding it to a workflow-step as mandatory field is therefore not desirable.
In this case, I've added a custom text field and gave it a default value -. Now this works well: the field is always shown and editable.
However, I can't seem to search on this field with jql. When searching with the basic view, I get a parsing error:
When escaping the character with a backslash, \- , I get 0 results while I would expect hundreds.
If you use the advanced search option, I either get 0 results (project = XXX AND YYY ~ "\\-") or an error:
Can someone help with solving this issue? Should I simply give a different default value to solve the issue or is there a way to search on the - character?
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.