What encompass "Ability to manage sprints" in permission scheme?

[Sherwin Soriano]

What is the scope of this permission scheme?

[Karan Sachdev]

Hey @Sherwin Soriano

The Manage Sprints permission allows user to create, start, and complete sprints in your project. If your board filter contains multiple projects, the user must have permissions in all the projects.

More details about permissions here: https://support.atlassian.com/jira-cloud-administration/docs/permissions-for-company-managed-projects/

Thanks!

[Sherwin Soriano]

Can I restrict users from moving tickets from backlog to a specific sprint cycle? I am assuming it will be a permission or a scheme that is revolving in the sprint field? If not, where can I put this restriction?

[Staffan Redelius]

Hi @Sherwin Soriano and welcome to the community.

As @Karan Sachdev pointed out the permission "Manage sprints" covers the starting, ending and completion of sprints.

The permission "Schedule issues" restricts who can change the order of the backlog, add work items to a sprint in the backlog view, and set due dates on work items.

Another possibility is to add a Condition in the workflow for work items so that only people who are members of a certain group can transition a work item to i.e "Ready to work on" or what status you have set as start state for work items in a sprint. 

Let me know if this helps!

Best regards,
/Staffan

[Karan Sachdev]

Hey @Sherwin Soriano

In this context, Manage Sprints permission can be viewed as the one that allows you to perform project admin related tasks, like start the sprint, set sprint dates or complete it etc.

The users need both 'Edit Issues' and 'Schedule Issues' permissions to be able to update the Sprint field on work items. So if you remove the Schedule Issues permissions, they won't be able to edit the Sprint on the work items (or move it to a given sprint from the backlog view).

However, they will also lose the ability to add a Due Date on the work items.

Thanks!