Looks like ScriptRunner doesn't fancy some collection functions in JQL.
For example, a query:
project = ABC and "Project Link" is NOT EMPTY
would produce an error "The operator 'is not' is not supported by the 'Project Link' field."
On the other hand this JQL works fine and basically produces the expected results
project = ABC and "Project Link" != ABC-0001
where "Project Link" is my customField of IssuePicker type with single value select
While this particular workaround solves "is not empty" case, the other function i.e. "in (<subset>)" doesn't work.
I suspect that " Issue Picker searcher" component is broken/incomplete. Anybody else ran into the same problem?
If you have a license for ScriptRunner and its JQL functions, then an equivalent to the "IS EMPTY" clause for those that really need to know whether it's empty could be:
issueFunction in issueFieldMatch("", "Name of Your Issue Picker Field", "^$")
At least this appears to work for me.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event