Assistance with Complex Board Filter Query

[Sarah Aubuchon]

This is my current filter where the user can't manage the sprint despite having permissions to do so:

assignee in membersOf(operators) AND project != "IS Support" AND assignee != A_Ferro ORDER BY Rank

 If I single out each of the projects, rather than saying !=, the user can manage the sprint.

assignee in membersOf(operators) AND project in("IS Support", XP, Lynxgate, "Operations Daily Runsheet Updates") AND assignee != A_Ferro ORDER BY Rank

Is there any way to use the != project and still allow the user to be able to manage the sprint?

Thanks in advance!

[Tarun Sapra · Accepted solution]

Hello @Sarah Aubuchon 

As per JIra guidelines, the user should have "Manage sprint" permissions on all the projects which the underlying JQL filter is fetching.

In your case when the data is fetched from specific projects 

project in("IS Support", XP, Lynxgate, "Operations Daily Runsheet Updates") 

then JIra knows that user has manage sprint permissions on all these projects hence everything works well. But in case of NOT operator Jira doesn't know from how many projects data can come and thus user will need to have manage sprint permissions on all projects except the project in NOT. Thus, it's imperative to mention the project explicitly or make sure user has manage sprint permissions on all the projects can provide the results except the project in the NOT operator.

[Sarah Aubuchon]

Tarun, Thank you for your response. I should have added that I have assigned the user to a group which has manage sprint permissions in each of the permission schemes that goes with any of the NOT projects. Additional suggestions?

Thanks!

[Tarun Sapra]

Hello @Sarah Aubuchon 

If Jira is not able to decide the list of projects returned these kind of permission issues generally arise, thus I suggest to use the JQL which clearly depicts the intended project list. 

Because if you have provided the user manage sprint permissions to all the projects then there shouldn't be an issue, also he should have the "schedule issue" permissions for all the projects as this permission is required for ranking of issues in the backlog.

Still, if you face issues, then I suggest to contact the Atlassian support team.

https://support.atlassian.com/contact/

[Sarah Aubuchon]

Thank again Tarun!

[Sarah Aubuchon]

I just want to add that I had originally only added the manage sprints permission to the projects I thought would appear in the sprint. But as Tarun stated, I needed to add the permission to all projects (permission schemes) for this to work properly. Thanks everyone!

[Radek Janata]

This issue is covered in the official documentation here:
https://confluence.atlassian.com/adminjiraserver/using-manage-sprints-permission-for-advanced-cases-938847165.html