Manage Sprint permissions
Asked by Kris Dewachter:

Hi,

I currently have "Manage Sprint" permissions, although I should not be able to.

I have a Jira Software board, that displays issues from 3 Jira projects.

![Screenshot 2024-09-12 at 12.25.58.png](https://community.atlassian.com/t5/image/serverpage/image-id/347024i01B7ACA589C96331/image-dimensions/367x435?v=v2 "Screenshot 2024-09-12 at 12.25.58.png")

All 3 projects use the same permission scheme. I checked with the "permission helper" and this confirms i DO NOT have "Manage Sprint" permissions, on any of the 3 projects.

![Screenshot 2024-09-12 at 12.30.41.png](https://community.atlassian.com/t5/image/serverpage/image-id/347025i4E0E389B0E093FCD/image-dimensions/294x496?v=v2 "Screenshot 2024-09-12 at 12.30.41.png")

However, when I navigate to the backlog of the board, I have the permission to create and manage sprints.

What might be overriding the permission scheme ?

Best regards,

Kris


Answers:
author: Trudy Claspill
body: Hello [@Kris Dewachter](/t5/user/viewprofilepage/user-id/4588367)

What is your level of access in the Jira instance? Are you an administrator for those projects? Are you a Product/Jira Administrator.

Based on my testing, a user with the Product Administrator will be able to Manage Sprints even it that permissions is removed from for the user within the permission scheme.

comments: author: Kris Dewachter
body: Hi [@Trudy Claspill](/t5/user/viewprofilepage/user-id/3569011) ,

Looks like you are right.

After some further testing it seems I can't manage sprints with only the "Manage Sprints" permissions in the permission scheme.

Only after activating the "Product Administrator" permission, I could manage sprints on my board.

This seems strange to me, because this permission also gives you the possibilty to manage other project settings (ex. workflows and permission schemes), and you don't want that.

Best regards,

Kris


author: Trudy Claspill
body: Hello [@Kris Dewachter](/t5/user/viewprofilepage/user-id/4588367)

I'm confused.

Do you need to managed the sprints but cannot, or are you able to manage the sprints when you think the settings should not allow you to do so?

You should not need the Product Admin access to be able to manage sprints if you have the Manage Sprints permission in all projects in scope of the board filter. If you **do** have the Product Admin access then that will override the lack of Manage Sprints permissions.

If you have the Manage Sprints permission and are not able to manage the sprints **without** also having the Product Admin access, we should dig into that to find the root cause.


author: Kris Dewachter
body: Hi [@Trudy Claspill](/t5/user/viewprofilepage/user-id/3569011) ,

I'm struggling with this also.

In my case, I have the "Manage Sprints" permission for all projects in the board, and when I don't have the "Product Admin" permission, i CAN NOT manage sprints.

I can only manage sprints when I also get the "Product Admin" permission.

Best regards,

Kris


author: Trudy Claspill
body: Hello [@Kris Dewachter](/t5/user/viewprofilepage/user-id/4588367)

I'd like to suggest a change to your filter as a test.

Currently your board filter uses:

*category = "Software Development"*

Please try replacing that with selection of the three specific projects:

*project in ("SW Demo 1", SW Demo 2", "Epics")*

Let us know if you are able to manage sprints in the board after that replacement.


author: Kris Dewachter
body: Hi [@Trudy Claspill](/t5/user/viewprofilepage/user-id/3569011) ,

Thank you for this suggestion. I changed the filter and did some more testing. Now, it seems to work correctly. With the "*project in ("SW Demo 1", SW Demo 2", "Epics")*" filter, I can manage sprints without having the "product admin" permissions.

When I remove my "Manage Sprints" permission from one of the projects, I can no longer manage the sprints. So that also seems to work as expected.

So it seems the "*category = "Software Development"*" caused the issue somehow.

Best regards,

Kris


author: Trudy Claspill
body: Jira requires you to have the Manage Sprint permission in all projects that are within scope of the Scrum board filter.

If you do not explicitly specify the projects within the filter, then Jira considers **all projects in the instance** to be within scope, because it does not know which projects will contain matching issues.

Jira cannot dynamically look at the results it actually got, minute by minute, and determine if you have the Manage Sprints permission in the projects that actually yielded the results.

It would seem that using the project Category field as one of the criteria is not considered by Jira to be an explicit project reference.

If my response helped solve your issue, please consider clicking on the Accept Answer button above my response. That will mark your question as Solved, and helps others searching for answers find the posts with validated answers.


author: Fabian Lim
body: Hi [@Kris Dewachter](/t5/user/viewprofilepage/user-id/4588367)

It looks like created a new board with 3 different projects which is fine. You can probably create the sprints, but I don't think you would be able to move tickets from those projects to the sprints.

See if you can edit any of the tickets to your sprint and you should not be able to.


Tags: cloud

jira-service-management

jira-service-management-cloud

jira-software-cloud