sprint permissions for board with unknown projects

[Liz Porritt]

We have a lot of projects from which we create sprint boards for work that is shared across the company. We don't define the projects in the query so that anyone can be assigned to the workstream. 

As the sprint management permissions are set at a project level this means that the ability to start and stop sprints isn't possible except for people who have full admin rights - which isn't sensible.

How can we give permissions to people to manage sprints without defining projects in the board query?

[Ste Wright]

Hi @Liz Porritt 

I don't believe it's possible to.

Because Sprints are project-based permissions, without any projects in your filter Jira is assuming an issue could be received from any project - that means that only a user with sprint-based permissions in every project can take action on the boards.

I would advise looking at your project and Scrum board setup, to decipher where project limits can be put in place - for example, have a project per delivery team. This houses all the Epics/Stories a team will work on - whilst other higher levels of hierarchy could live in central product-based projects.

If you'd like help with how to setup your projects to help with the permissions issue, please let us know more about your current setup so we can advise further :)

Ste

[Liz Porritt]

Thanks Stephen

We have two types of teams, some are focused on functionality and some on delivery.  The delivery teams are made up of people and components from various functionality teams and are temporary.

Each functionality team has a project.  The delivery teams don't have projects because of the temporary nature of them.

We have about 15 functionality teams so it seems that for each delivery squad's board  we would have to create a filter that names all 15 projects and make sure that the permission is allowed in each of them -  - is that correct?

[Ste Wright]

Hi @Liz Porritt 

Yes - if all 15 functions are often worked on by all teams, that would be the solution in your current model.

You could filter down which issues are available on their board if there is a unique identifier for those issues as to which team is working on the issue - for example a component, label or custom field.

Ste

[Liz Porritt]

Hi @Ste Wright 

We do have a unique identifier for bringing out the delivery boards and it was my hope that this would be all that would be needed, so that it would be very easy for a new squad to create a board.

Would it be possible to use Project Category so that we can keep the query simple?

[Liz Porritt]

I tested this Project Category approach and it worked - thanks for your help @Ste Wright 

[Ste Wright]

Hi @Liz Porritt 

Just to confirm - slight modification from above answer!

You don't need the category or anything else in the filter I believe - just provide the permission to Manage Sprints to the users who require it across the 15 projects (which you can do via a group, for example).

The reason for this is that as long as they have the permission and those are the only 15 projects which could end up on a board, then the users will always have permission to all possible projects in any of their filters :)

Of course if you add/remove projects regularly, category is a nice, simple way to manage this.

Ste