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

Has anyone noticed a bug with the 8.20.8 update - where there are two new Sprint roles?

Jeramy S_zb23fy

A few days ago, we upgraded our Jira instance (Jira DC) to version 8.20.8. The very next day during the sprint planning agile ceremony, our Scrum Master noticed that she could not end a sprint nor could she start a new one. As the Jira Admin, I looked at the project's roles/permissions. I noticed (immediately) that there were two "new" roles for sprints. There was the Edit Sprint and Start/Complete roles. For some reason, these two new roles were assigned to the jira-administrators role (which our SM is not a part of). Our Scrum Master had the Manage Sprint role, so after reading the documentation related to this change, I assumed the issue was something else. I assumed this because the documentation says, and I quote, "If they have the Manage Sprint role, they have full control of the sprint."

I believe that I found a bug. Has anyone experienced something similar? If so, how did you resolve the issue? If this is a bug, where do I go to let Atlassian know?

Thank you!

Accepted answers

Filipi Lima

Hello, Jeramy! Welcome to the Community!

These more granular permissions were introduced in Jira 8.6 - you can find it on the release notes below:

https://confluence.atlassian.com/jirasoftware/jira-software-8-6-x-release-notes-978220007.html

This is the documentation around those new permissions:

https://confluence.atlassian.com/adminjiraserver0820/sprint-permissions-and-defined-processes-1095776944.html

Cheers!

All comments

Filipi Lima

Hello, Jeramy! Welcome to the Community!

These more granular permissions were introduced in Jira 8.6 - you can find it on the release notes below:

https://confluence.atlassian.com/jirasoftware/jira-software-8-6-x-release-notes-978220007.html

This is the documentation around those new permissions:

https://confluence.atlassian.com/adminjiraserver0820/sprint-permissions-and-defined-processes-1095776944.html

Cheers!

Jeramy S_zb23fy

Hi @Filipi Lima ,

Thank you and thank you for the quick reply.

Before submitting this question, I reviewed the release notes and the documentation, but I believe that I found a bug with that enhancement.

Reading the documentation, the permissions hierarchy goes like this:

Manage Sprint

Edit Sprint and Open/Complete Sprint

In my scenario, my scrum master had the Manage Sprint permission. They should have been able to close the sprint and open a new one. However, they were not able to do this because the other two permissions were assigned to the default jira-administrators group. They were not able to manage the sprint until I put them in those other two groups.

Here's where I think I found a bug. If those permissions are assigned to the default jira-administrators group, I think it somehow takes a higher order in the hierarchy and overrides the Manage Sprint permission.