Please let me know why this is not solved since ages?

BR

Heiko

Atlassian treats this a "Not a bug" , but it is not logical to me. And it looks like most of the Jira users expect just another behavior - which seems more logical to me.

At least Atlassian should offer another solution how we can achieve it.

The improvement https://jira.atlassian.com/browse/JRASERVER-40245 is open since 2014 and still in status "Gathering interest"

I've been noticing the same thing in the REST Api (/search?jql='jql'), when searching for project=x OR project = y (y does not exist), I get no return issues even though project x exists.

this applies to other fields. eg.

... project=x OR status=notastatus
{
  "errorMessages": [
    "The value 'notastatus' does not exist for the field 'status'."
  ],
  "errors": {}
}

Obviously I would have liked to get the results of project=x since there are some values where this is true. I just find it a little less intuitive since I'm coming from SQL.

Anyway, I know this is an old thread, but does anyone know if this sort of thing has been resolved?

Hi intersol_OLD,

I understand where you are coming from when you say:

Project in should just return nothing if some values from the list are invalid, otherwise you end-up with tens of broken filters every time you perform a change on projects (renames, key renames, archived, ....)

Unfortunately, that was the design that was selected when JQL was implemented (all values have to be valid).

Having said that, there's an open suggestion to change the existing design of query processing in the issue navigator to cater for these use cases at https://jira.atlassian.com/browse/JRA-40245 Please feel free to add your vote and feedback on that issue.

Regards,

Oswaldo Hernández.
JIRA Bugmaster.
[Atlassian].

Oswaldo, I do understand the ambiguity of the message but the way "project in (...)" works is broken because of the current behaviour. Project in should just return nothing if some values from the list are invalid, otherwise you end-up with tens of broken filters every time you perform a change on projects (renames, key renames, archived, ....)

So I can only see two things:

• bug fix: removing the error and performing the query, ignoring the unmatched values.
• improvement: display a warning instead of the error, but perform the query and return matched results.

A broken query can have disastrous effects, and worse is very hard to detect as it can be used in many places, including outside of jira (confluence).

This is intentional and by design.

The message is ambiguous for security, such that unauthorised users can not find out which projects they have visibility over and which ones they don't.

Regards,

Oswaldo Hernández.
JIRA Bugmaster.
[Atlassian].