You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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
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
Hi Tarun, thank you for the fast and useful answer. This means that the description here is wrong. Or at least incomplete: https://confluence.atlassian.com/adminjiracloud/managing-project-permissions-776636362.html?_ga=2.30012473.721349570.1546410451-1647108922.1545127571