nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Scrum Admin cant start Sprint even though they have manage sprint on all permission schemes.

Matthew_Evans_evjxdp

Hi,

I'm new to permissions so this may be obvious. I am trying to allow all users that are defined as scrum masters to be able to start sprints.

They can start sprints for any boards that do not have complex filters on but we have team boards (boards filtered by team names) which are complex filter boards.

These boards the scrum masters are unable to manage sprint (hovering over the start sprint button brings up the tool tip "You need the Manage Sprints permission for all projects in the origin board to manage this sprint.").

As far as I can tell, I have added the scrum master group to every single permission scheme we have so all projects should have them assigned with the manage sprint permission yet they still are unable to start sprints on the team boards. We are currently on version 7.1 server.

Any help would be greatly appreciated as I am at a loss here.

Accepted answers

All comments

Randy_dyxb6i

1. Create a project role on your system called "Scrum Masters"

2. Modify your permission scheme(s) to allow the project role "Scrum Masters" to have "Manage Sprints" permission

3. Verify that all projects in your board leverage the permission scheme with the above change

4. For every project, set the user to be part of the "Scrum Masters" project role

5. In your board filter query, start the query by explicitly defining the projects that should be included in the board even if it's redundant. e.g. "project in (ABC, DEF, GHI)"

If the above still doesnt work, spin up a new scrum board with the board filter query reduced to just one of the projects. Is the user able to start the sprint then? if so, layer in additional projects one at a time until you run into issues.

Hope this helps.

Matthew_Evans_evjxdp

Hi, Thanks for the reply!

I have done all this, and it works perfectly for boards with single projects (or small numbers of projects that can be defined).

The issue I have is with a team board and sprint. We currently have 620+ projects that the team could be working on so defining them all on each teams board would be an issue. I just need to figure out why, even though the scrum admins have manage sprint rights, they cant start sprints on boards with complex filters yet a full admin can. We obviously dont want to give full admin to our scrum masters, so thats not a great solution.

This is an example filter used on one of our teams boards.

issuetype in standardIssueTypes() AND team = teamname ORDER BY Rank ASC

Any more advice and help would be greatly appreciated, thank you.

Randy_dyxb6i

I've found that boards behave weird when you dont explicitly include the project keys in the board query. You can test if this is what's affecting you by adding a few of the project keys to the query and observe if the button becomes functional.

I would start there to at least narrow down to wether it's the query or something else.

Matthew_Evans_evjxdp

Apologies for the long wait between replies.

I have tried adding multiple projects to the board query and with multiple projects, people can start sprints.

The issues is, i would have to define 600+ projects on each board, which seems....not ideal. Is there a way around this issue so the team boards can have sprints started by scrum admins rather than full admins?

Thanks.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-server

atl-gruland