Improve 'Manage Sprint' permissions when the filter is complex

Problem Definition

Currently, as explained in Using Manage Sprints permission for advanced cases:

When boards have complex filter queries
A filter query is considered complex when Jira Software can't determine which projects will be returned by the query. When this happens, Jira Software 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.

This means that the users also need to have Manage Sprints permission in the JIRA Service Desk projects as well as have JIRA Service Desk licence.

Suggested Solution

Improve Manage Sprint permissions when the filter is complex, so that the user doesn't also needs a Service Desk licence.