User can't manage sprints despite having permission in all projects in board query?

[Krista Nicol]

I'm an administrator for my company and we had a user report that they were unable to edit or create new sprints on their board.

By default, any logged in user has access to Manage Sprints - majority of the projects in our organization use this permission scheme.

I've taken the board query and identified any external projects that were being brought into this board, and there was only one other project. That project also allows for any logged in user to manage sprints.

I have used the permission helper with issues on both of the projects and it says that the user should be able to manage sprints, but they aren't able to.

We've removed and reinstated access for the user, had them clear their cache and cookies, and reboot their system, but this hasn't resolved the issue. 

[Trudy Claspill · Accepted solution]

Hello @Krista Nicol 

Can you please show us the filter query used for the board?

Does it explicitly specify the projects to include? If it does not, then Jira evaluates that to mean that any project in the entire Jira instance may have relevant issues, and the user would have to have Browse Projects and Manage Sprints in every project in the instance.

[Krista Nicol]

Thank you @Trudy Claspill !

I'm not able to share the exact query due to security reasons, but I've recreated it below with the specific project, component, and label names omitted.

project = "Source Project" AND labels in (First) OR project = "Source Project" AND component in ("Comp1", "comp2", "comp3", "comp4", "comp5", "comp6", "comp7", "comp8") OR labels = Second Order by Rank ASC

Since the first half of the query was specific only to issues within the source project, I assumed the last bit pulling in the "Second" label was what was causing the issues. I ran a query that was just "labels = second" and there was only one project that was using that label, and that project has the browse projects & manage sprints permissions for any logged in user as well. 

[Trudy Claspill]

Hello @Krista Nicol 

Tell me if I am interpreting your query as you intend.

1. You want to get all issues from "Source Project" where the Labels includes "First"

project = "Source Project" AND labels in (First)

2. In addition to those issues, you want all issues for "Source Project" where the Component field contains any one or more of the Components you listed.

 OR project = "Source Project" AND component in ("Comp1", "comp2", "comp3", "comp4", "comp5", "comp6", "comp7", "comp8") 

3. In addition to that you want issues from ANY project in all of Jira where the Labels field includes "Second".

OR labels = Second 

If I have interpreted that correctly, then the issue is caused by the third piece.

It does not matter how many different projects actual include issues where "Second" is a Labels value. The way Jira looks at this is that you want those issues from any project. In that case you must have the Manage Sprints permission in EVERY project in your Jira instance regardless of the type of project. You need to add an explicit list of projects to that portion of your query to avoid this problem.

(project = "Source Project" AND labels in (First)) OR (project = "Source Project" AND component in ("Comp1", "comp2", "comp3", "comp4", "comp5", "comp6", "comp7", "comp8")) OR (project in (<comma separated list of project>) and labels = Second) Order by Rank ASC

[Krista Nicol]

Got it! I figured that the last part of the query was causing the issue but I didn't know the permission settings would apply to all projects that could use the label, rather than the ones who are currently using it. Good to know! Thanks @Trudy Claspill !