How to restrict Sprint Scope change permissions in Jira Next-Gen Cloud Projects

[Mark Lombardi]

With Jira Next-Gen Projects (a.k.a Team Managed Projects), how do we restrict Team Members from being able to modify the scope of a Sprint?

That is by restricting who can add and remove items from a Sprint or edit the Sprint field of an Issue?

Bonus points if being able to reorder the Backlog can also be restricted.

[Jack Brickey]

I would refer you to this document on TMP permissions

members are granted sprint permissions.

[Mark Lombardi]

Thanks for responding Jack.

I viewed that page, the permission "Manage Sprints" does not restrict or enable who can change the Scope of a Sprint. It only allows or disables who can modify the Start Date, End Date and Description of a Sprint.

I've also posted feedback on that page to update it with regards to Scheduling Sprint Permissions. Lets see if they update it or not.

Manage project sprints

"This permission allows people to create, start, and complete sprints in your project. This includes adjusting the sprint duration and goal."

In Jira Classic, the permission was "Schedule Issue Permission"

Similar issue, a bit old and may be out of date.

https://community.atlassian.com/t5/Jira-questions/Sprint-permissions-in-Next-Gen/qaq-p/1187833

Related questions, none of which answer the question for Next-Gen Projects though.

https://community.atlassian.com/t5/Jira-questions/Schedule-Issue-permission-on-a-Scrum-Board/qaq-p/972155

https://community.atlassian.com/t5/Jira-questions/User-Permission-for-Sprint-planning-in-JIRA-Agile/qaq-p/345257

https://community.atlassian.com/t5/Jira-questions/Schedule-issue-permission-not-working-correctly/qaq-p/756196