Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

How to manage sprint permissions

Hello Community Family...!


Good Morning /Good Afternoon / Good Evening whenever you are reading this article.

In this article, we are going to know about different permissions related to sprint.

1. Sprints usually appear on the Scrum boards.

--> To view a scrum board, the board filter must be set to viewable to user/group/roles in a project.

2. Boards are present in Projects or individuals.  

--> If Jira wants to see the board inside the Jira project. user must have "Browse Projects".

This can be customized by the Jira administrator. The permission can be enabled to Project Roles, Application Access, Groups and etc as below.


3. Sprint-related operations

  • Creating sprints
  • Starting sprints
  • Completing sprints
  • Reopening sprints
  • Reordering future sprints
  • Deleting future sprints
  • Editing sprint information (sprint name and dates)
  • Moving the sprint footer

To perform the above operations user must have the following permission - 'Manage Sprints'.

This permission can also be enabled for the below user scenarios by the Jira administrator.


4. To add issues into a sprint user must have - Schedule Issues

This will helps to re-order the stories in Board & sprint.

5. If the user wants to add a story / Task / Issue into "Active Sprint". He needs the following permissions.

1. Browse Projects Permission

2. Create Issues Permission

3. Edit Issues Permission

4. Schedule issues Permission


Note - When an issue is Added/deleted from "Active Sprint" this will affect the scope of the sprint. The scope can be seen in the "Burndown chart" explained below.

 1.  View and understand the burndown chart 



Anvesh Kagithala


Dave Mathijs Community Leader Jul 20, 2022


Any idea why a user is not able to create a sprint from one board, but is able to do so from another board?

The project role Scrum Masters has the Manage Sprints permission in the permission scheme.

The user has been added to the Scrum Masters project role for all projects that use this permission scheme.

Hello @Dave Mathijs ,

Is the board contains issues from same project or multiple projects.
If multiple projects, may be please check the other projects Permission schemes where the issues are from, sometime project related permissions will cause this issue.


Log in or Sign up to comment

Atlassian Community Events