Details
-
Bug
-
Resolution: Timed out
-
Low
-
None
-
6.3.8
-
6.03
-
Severity 3 - Minor
-
-
Description
Let's assume there is an issue called ABC-4 (ID: 10015) that user Fred doesn't have permission to see.
State of things before https://jira.atlassian.com/browse/JRA-36368:
If Fred tried issue ID 10015 in any of JQL clauses like:
issue != 10015
issue in (10014, 10015)
issue not in (10014, 10015)
issue > 10015
issue >= 10015
issue < 10015
issue <= 10015
he used to get an error and the query wouldn't run.
After fixes for JRA-36368, we no longer load each issue individually to make sure they exist. As a side effect the permission check on the clause is gone. The permission filter is applied when the query runs.
Now, as long as issues exist they can participate in JQL clauses. As a result, these queries return what user expects:
issue != 10015: returns other issues, even though the user can't see this particular one
issue in (10014, 10015): returns only 10014
issue not in (10014, 10015): returns everything else, except these two issues
BUT, these queries still don't return anything:
issue > 10015
issue >= 10015
issue < 10015
issue <= 10015
Attachments
Issue Links
- caused by
-
JDEV-30741 Loading...
- clones
-
JDEV-30838 Loading...