sprint

[xin_wang]

Sarah's team has 10 completed issues in the current active sprint.

As a Jira administrator, what is the minimum permission Sarah needs to complete the sprint?

1. Manage Sprints
2. Schedule Issues
3. Transition Issues
4. Move Issues
5. Browse Projects
6. Edit Issues

[Chitra Nagdeo]

Hey @xin_wang ,

Welcome to Atlassian Community Forum, My name is Chitra and I am part of Jira Cloud support team in Atlassian. I understand you want to know the basic permission needed for a user to complete an active sprint.

To complete a sprint in Jira, a user must have the following minimum permissions:

• Manage Sprints permission on all projects included in the board's filter and on all projects that have issues in the sprint.

• Schedule Issues permission is also recommended, as it controls the ability to set dates and scheduling for the sprint.

Key points:

• If the board filter includes multiple projects, the user needs Manage Sprints permission for all those projects. (Configure Board --> General --> Board Filter)

• If the board filter is complex (e.g., does not specify projects), the user may need Manage Sprints permission for all projects in the instance. (Configure Board --> General --> Filter details --> Projects in Board)

• If the sprint originated from a different board, permissions are checked against the origin board's filter as well. Article Knowing when you have a Shared Sprint

• Click on the shared sprint and it will show all the Boards the Sprint is associated with. Check the Board filter query and thus the projects the user must have Manage sprint and Schedule issue permission.

Summary:
The essential permission is Manage Sprints on all relevant projects. Without this, the user will not be able to complete the sprint, even if they have other permissions. Refer attached screenshots explaining the above scenarios

Thanks and Regards
Chitra Nagdeo
Atlassian Cloud Support
ATLASSIAN

[Priyanka Khare]

Only users with the Manage Sprints permission (granted at the project level) can:

• Start, complete, or re-open sprints
• Edit sprint names and dates
• Move issues between sprints

Other permissions like Transition Issues, Edit Issues, or Schedule Issues relate to individual issue changes — not sprint actions.

[Staffan Redelius]

Hi @xin_wang 

Assuming this is a Company managed project I would sa 1 and 5 would be sufficient for closing a sprint.

• Browse projects for the actual project, otherwise she will not see the project at all.
• Manage sprints permission in all projects included in the sprint filter to be able to create, start an end sprints.

You can connect the permissions to a project roles for increased flexibility

• Create a Project role called "Sprint manager")
• Add the permission "Browse project" and "Manage Sprints" to that role in the permission scheme.
• Give the user the Sprint manager role in each project that has work items included in the sprint

Does anyone in the community have other suggestions?