Site Admin query: JQL for sprint in OpenSprints() and other site admins can't run the query

[Lara_Jones]

I've created a query to check for specific activity across open sprints on our cloud instance.  

We have a couple projects that we don't want to pull data from and I've tried both

NOT IN and !=

to do this.

It appears that the site admins who haven't been added to those projects as project admins cannot run the query unless I remove the NOT IN or != operators and just query all projects for open sprints.

So we can run the query to check for all projects.  

This seems like a bug.  Why can they not exclude projects they don't want to query against if they aren't project admins but they are site admins? 

[Nic Brough -Adaptavist-]

Site admin rights, and, in fact, project admin rights, do not give you the right to see the project.  The "browse project" permission is what lets you see a project.

I am a little stumped on the mention of "not in" though.  I think we need to see the whole query you are using (and an explanation of "can't use" - does that really mean "it does not return everything I expect", or is there an error?)

[Lara_Jones]

I am aware that site admins do not have project level permissions; however, I can run site wide queries even if I am not added to a project as a project admin.  

The issue occurs when I try to exclude a project. 

This works for all site admins

sprint in openSprints() 
AND status not in (Azure,PROD, STAGING, Complete, 
Completed, Done) 
AND assignee is not EMPTY 
ORDER BY project, assignee, issuetype, 
key, status, cf[10042], "Story point estimate" DESC

This does not:

sprint in openSprints() 
AND project != QA-Sample 
AND project != Workflow-poc 
AND project != "Workflow EX 2" 
AND status not in (Azure, PROD, DEV, 
STAGING, Complete, Completed, Done) 
AND assignee is not EMPTY 
ORDER BY project, assignee, 
issuetype, key, status, cf[10042], 
"Story point estimate" DESC

I tried using project

NOT IN (QA-Sample, Workflow-poc, "Workflow EX 2")

And I have the same permission issues.   Site admins who are not added to these projects at the project level cannot run the site wide query.

To me? This does not make sense.  I'm not actually trying to pull information for these projects.  I'm telling the query to ignore it.