A couple of my users are unable to see the filter results as they are not members of stated "NOT IN" Projects.
Surely the NOT IN X is a statement that negates the access check of said excluded projects from results.
This is a significant logic flaw in Jira filters.
If the results are to exclude said projects then there is no issue with the results being shown as the project will not be shown !!!
Hi @Matt Smith
The behaviour you are experiencing is as expected.
The filter tries to show information based on the clause, but upfront the permission of the user executing the filter are not being evaluated, but during the execution
Your only solution is to change the JQL to projects in ().
Lol - so for the sake of 3 specific Projects I have to create and IN for 70+ Projects !....
Also update the filter every time a new project is added
All that needs to happen is the logic is updated to run the access protocol for only included projects.....
"Expected" behavior is not necessarily good or correct behavior ;-)
I stand by my point this is flawed logic
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I know.
JQL is in basis simply SQL, this acrts in the same way.
If you would create a view in a db, based on data from different tables, and a user accessing the view with no access to certain tables will also get no results in the view
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.