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

Schedule Issue permission on a Scrum Board

I am studying for ACP-300 with a few of my colleagues and we are unable to decipher what seems to be at best an ambiguous description regarding adding issues to the sprint.

In the description of the manage sprints permission it says:

In general, sprint actions require the Manage Sprints permission. However, there are some sprint actions (e.g. adding issues to sprints, removing issues from sprints) that require the Schedule Issues and Edit Issues permissions.

It makes sense that Edit Issue permission is needed as the Sprint field on the issue will be updated by adding it to a sprint.

When we look at the Schedule Issues permission it only guards the Due Date field.

Permission to schedule an issue — that is, to edit the 'Due Date' of an issue. In older versions of Jira this also controlled the permission to view the 'Due Date' of an issue.

As far as we can tell experimenting with the Teams in Space project, Due Date is not used, neither set manually ( it is not a part of the screen ) or set as a consequence of adding the issue to a sprint. 

But when trying to add an issue to a sprint with a user that does not have the _Schedule Issues_ permission Jira will not complete the action. This is consistent with the documentation for manage sprints, but as far as we can tell not with the documentation for Schedule Issues.  

Is there anyone with some insight on this seeming inconsistency that can enlighten us?


Thanks in advance

2 answers

1 accepted

4 votes
Answer accepted
Tarun Sapra Community Leader Jan 03, 2019

Hello @Johan Abildskov

The reason "Schedule Issue permission" is required is because when you add/remove issue into sprint then not only you change the Sprint field (edit permission) but you also change the Rank of the issue. And this is where "Schedule issue permission" comes into picture, under the hood it seems that Jira is using this permission for controlling as to who can change the rank of the issue.

Please see here

Tarun Sapra Community Leader Jan 03, 2019


Like Benoit Anger likes this

Hi Tarun, thank you for the fast and useful answer. This means that the description here is wrong. Or at least incomplete:

Tarun Sapra Community Leader Jan 03, 2019

Description seems to be incomplete, I would suggest you to reach out to Atlassian support in this matter, so that they take note of it and update the description.

Rob Horan Community Leader Sep 12, 2020

This makes zero sense.  Why would it not fall under Manage Sprints?

I have the same challenge understanding this "Schedule Issue" permission... 

Suggest an answer

Log in or Sign up to answer