Issue Summary

Setting a Complex Board Filter breaks the Manage sprints permission. The documentation page Use manage sprints permission for advanced cases indicates:

A filter query is considered complex when Jira can't determine which projects will be returned by the query. When this happens, Jira will require users to have the 'Manage Sprints' permission for all projects in the instance — essentially, you'll need to manually set users to have this permission for all projects.

But currently, this is not working as expected.

Steps to Reproduce

• Create a Company Managed Project
• Create a Board Filter which doesn't scope down to any specific project as shown below:

assignee = <user-ID>

* Access the board with a non-Jira admin, but having the Manage sprints permission in all the projects in the site.

Expected Results

User is able to Manage sprints in the board as long as they have the Manage Sprints permission for all the projects whose issues are present in the board filter.

Actual Results

The user is unable to Manage sprints in the board even if they have this permission in all the projects in Jira.

Workaround

• Either make the user a Product Admin or Org-Admin
• Or modify the Board Filter query to scope it down to specific projects