User with Manage Sprint permission not able to Create Sprint

[Kaitlin Madsen]

I've got a user who CAN manage sprints in one board, but not another. The filters are fairly similar (although not written well). 

The filter for the board he CAN manage sprints is: 

component in ([name]1, [name]2) order by "Epic link" asc, priority desc, cf[10072] asc

The filter for the board he CANNOT manage sprints is: 

component = [name] and project !=[project name] ORDER by Rank ASC

Instead of giving him project admin access on every Jira project, I added a group he was part of (Project Managers) to the Manage Sprints permission in the permission scheme. But it's still not working. 

Any other ideas of what I need to check? (I did suggest we change the filter, but that doesn't catch any weird instances of a rogue issue being assigned to their sprint, so I thought I would try to just do a catch-all through the permission.)

[John Funk]

Hi Kaitlin,

It's almost certainly a permission issue with all of the projects that would be included in your filter. So if I am reading the filter correctly, the board shows every project in your Jira instance, except one?? That is probably borderline unmanageable depending on how many projects you have. 

The other thing to try is to go to the Permission Scheme and use the Permission Helper. Try various projects and the Manage Sprints permission to see what kind of feedback you get. 

[Prachi Bolar]

Hi Kaitlin,

Welcome to community 

As Sprints can include issues from multiple projects, we will need to ensure that the mentioned user has access to all the issues in the sprint. Additionally, the user should have Manage sprints permission in all projects whose issues are added to the Sprint.

In case the Sprint includes issues from a single project, it is important to verify the Board filter.

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.

This means that they will manually need to check all the projects on the site, including Jira Service Management, Jira Work Management, and Jira Product Discovery projects, even if they are TMPs.

Thank You,

Prachi

[John Fetzik]

Yeah, they need to have the Manage Sprints permission in ALL the Projects that the Board can possibly return Issues from. 

This is true even if the Board is not currently displaying any Issues from one or more Projects. The permission is still needed for those Projects, because permissions are at the Project level not the Issue level.