2 equivalent JQL queries with different result set

[Volker Lenz]

According to JQL tech docs, one would expect the following 2 JQL queries to produce the same output:

query 1: sprint = 480 OR sprint in openSprints()

query 2: sprint in (480, openSprints())

However, we found in our JIRA project that while query 1 always delivers expected results query 2 does not. For some - not all - unsers, query 2 prints error messages, stating that the user is not entitled to see the content of sprints. 

This can hardly be understood as a permission issue, as query 1 is supposed to run through the same subset of sprints as query 2 does. 

Anyone else here, who is familiar with this case and can explain?

[Tom Lister]

Hi @Volker Lenz 

How do they JQL queries behave for user when run separately?

sprint in (480)

sprint in (openSprints())

[Volker Lenz]

Both queries, when executed seperately, deliver correct results.

[Volker Lenz]

we also tested with the following query: sprint in (sprint A, sprint B), where sprint A is an open sprint and sprint B is not. That statement also worked for all users.

[Volker Lenz]

so the impression is there is something weird going on when you use functions like openSprints() as arguments of the list operator IN.