Hi All, I'm struggling to find out whats wrong with some permissions that I have created. Basically, I wanted to give all our squad leads the ability to manage sprints without giving them full admin access to our Jira instance. I followed this article on the atlassian support pages, but it's still not working. There's probably a bit of background that needs to go with this post too, as we run things a little differently, please bear with me: * We have 9 squads, and each of these squads have their own boards. When a new project is created we use the category in project settings to allocate a squad to the project * We then use a JQL filter on the squad board to pull in the issues from the new project based on the project using that category. The JQL is very basic category = "Squad 1" ORDER BY Rank ASC This allows us to manage multiple projects for a single squad in 1 board The issue I'm having is that even though I've given our squad leads the Manage Sprint permission following the article referenced above, the Create Sprint and ability to start a sprint is still greyed out for them Has anyone come across this previously? *** Edit *** I've noticed that when trying to create or start a sprint this dialogue is present

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; } } }

Using manage sprints permission

Phil Hayes_ckbf5f

Hi All,

I'm struggling to find out whats wrong with some permissions that I have created.

Basically, I wanted to give all our squad leads the ability to manage sprints without giving them full admin access to our Jira instance. I followed this article on the atlassian support pages, but it's still not working.

There's probably a bit of background that needs to go with this post too, as we run things a little differently, please bear with me:

We have 9 squads, and each of these squads have their own boards. When a new project is created we use the category in project settings to allocate a squad to the project
We then use a JQL filter on the squad board to pull in the issues from the new project based on the project using that category. The JQL is very basic

category = "Squad 1" ORDER BY Rank ASC

This allows us to manage multiple projects for a single squad in 1 board

The issue I'm having is that even though I've given our squad leads the Manage Sprint permission following the article referenced above, the Create Sprint and ability to start a sprint is still greyed out for them

Has anyone come across this previously?

*** Edit ***

I've noticed that when trying to create or start a sprint this dialogue is present

Screenshot 2022-12-20 at 14.44.23.png

Accepted answers

Ravi Sagar _Sparxsys_

Hi @Phil Hayes

Modify your JQL and limit it to those project.

Do you have 9 squad boards and 1 common board for everyone? In any case specifying the projects in the board filter's JQL should work.

Ravi

All comments

Rilwan Ahmed

Hi @Phil Hayes ,

"Start Sprint" will be available only when there are no active sprints. Please check if there are any active sprints in your board.

Phil Hayes_ckbf5f

Thanks for your input, I've been a Jira admin for a long time so I know the reasons around not being able to start a sprint etc., but that doesn't explain why I can't create a sprint even with what looks like the correct permissions applied according to the article

Marta Woźniak-Semeniuk_m044pw

Do the squad leads have "Manage Sprints" permission in all projects that are included in the board query?

Phil Hayes_ckbf5f

Yes, we only use the default project permission set

I've double checked and all the projects have the "Sprint Manager" group added under the Manage Sprint permission

Ravi Sagar _Sparxsys_

Hi @Phil Hayes

Modify your JQL and limit it to those project.

Do you have 9 squad boards and 1 common board for everyone? In any case specifying the projects in the board filter's JQL should work.

Ravi

Phil Hayes_ckbf5f

Hi @Ravi Sagar _Sparxsys_

I was trying to avoid having to update the JQL each time we add a project, hence using the categories to in essence automatically add them

I have 9 squad boards, each of them setup in the same way. I don't have 1 common board that sows everything, that would be information overload

Trudy P Claspill

You must explicitly declare the in scope projects in the JQL filter. You can't use criteria to select the projects (i.e. using the project category.)

Otherwise Jira will assume that any and all projects may have issues that are within the scope of the board, and the users must then have Manage Sprint permissions for all projects on the Jira instance.

Matt Doar_tzgiej

I find debugging sprint permissions can get tricky, even for experienced Jira admins. One approach I sometime use is to start with a new board to see if I can reproduce it using the smallest possible configuration. Though I think your current board seems pretty simple already. If the problem were just for Closing sprints, then there are a bunch of other possible reasons such as an issue being moved out of the scope of the board filter.

Still, a new board in staging with just a few issues and one of the users creating new sprint is a good data point

Phil Hayes_ckbf5f

I'm guessing that this is the issue I'm having, trying to minimise the overhead of constantly updating the JQL by using categories, but even though the JQL is simple there's too much for Jira to work out

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud