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
