I agree with you Matti, however, this is what was mentioned in the comment as the solution. My real problem is that the action should NOT be linked to the Schedule issue permission (as it is now), as this controls the right to edit/view the due date. Hence, connecting it to Manage Sprint permission, I could give this permission to all project members, and still have external users editing the due date, without having the right to add/remove issues from the sprint.

There are different views on this and some Jira users like me prefer the open approach where the team members are allowed in the tool to do this without the need to request the scrum master to do it. This is especially important when your team switches scrum master often. Therefore it would not be good from my view to link adding issues to a sprint into this permission.

We are using JIRA Server 7.1.9. However, users with Schedule Issue but WITHOUT Manage Sprint permission, are still allowed to add issues to the active sprint.
So if this issue was suppose to fix this problem also (as mentioned in multiple comments), it is still not fixed and should be reopened.

Hi paul.thomas1 - the origin board based permissions are in place, they are in the Server 7.1 release and also Cloud.
Further updates would be either in the documentation space, release notes or other related issues here on JIRA.Atlassian.com
Below are links to the documentation for permissions:
Server: https://confluence.atlassian.com/display/JIRASOFTWARESERVER071/Permissions+overview
Cloud: https://confluence.atlassian.com/jirasoftwarecloud/permissions-overview-764478244.html

To better understand your questions for the behaviour above, could you please create a support ticket at https://support.atlassian.com
That way we can provide you with support specific to your circumstances and with higher security. The credentials to access the Support site should be the same as this one (jira.atlassian.com).

Kind regards,
Martin
JIRA Software

Hi @mjopson,

In your comment, under "Consistent Permissions", you mention that this feature will move to all sprint related permissions being based on the projects visible under a board's filter. I've just been experimenting with JIRA Software 7.1.0#71003 and this doesn't appear to be the case. A couple of specific things I have noticed, for a Scrum board looking at two projects (i.e. board filter is "project in (PROJA, PROJB) ORDER BY Rank"):

1. If "User A" has all permissions in PROJA but none in PROJB, they can still create sprints on the board (it seems the list of projects checked is based on those the current user can see). If User A is granted Browse Project permissions in PROJB (but nothing else) then they cannot create sprints (I have PROJB issues in the Backlog, I haven't checked if this is still the case if I remove them).
2. Sprint start/stop permissions still seem to be based on the issues added to that sprint, i.e. User A can start/stop a sprint on the above board provided no PROJB issues are in the sprint.

Have the "origin board" based plans been abandoned? Or will they be in a later release? And is this the best place to keep an eye out for updates?

Thanks very much,

Paul

sharemangomail87928597 - as noted in the versions above this shipped to JIRA Software Cloud in the 2016-01-25 release, and to JIRA Software Server in version 7.1.0 which shipped on 11 Feb 2016.

srenou - the documentation you linked to is for an older version of JIRA Agile, this shipped to JIRA Software and so the documentation is located at:
https://confluence.atlassian.com/jirasoftwareserver070/planning-your-sprint-762877269.html
https://confluence.atlassian.com/display/JIRASOFTWARECLOUD/Planning+your+sprint

Kind regards,
Martin
JIRA Software

I have the feeling that the documentation was not updated as I can read at: https://confluence.atlassian.com/agile/jira-agile-user-s-guide/working-with-sprints/creating-a-sprint

You don't have the right permissions: You can only create a new sprint if you have the 'Administer Projects' permission in all projects included in this board's backlog.

As this feature was shipped with 7.1.0 release, that does not seem accurate anymore?
On the other side, I have a user with Manage Sprint permission on all projects of the board, but he still cannot create a new sprint, how can I debug that?

When it got shipped? In which version it is available

As noted previously the new Manage Sprints permission has shipped to both JIRA Software Cloud and Server.

Previously we had discussed the intention to consolidate the add or remove an issue from sprint into the Manage Sprints permission. However, we have determined that this will not be a workable solution for many of you.

The shipped improvements introduced with Manage Sprints permission we expect to alleviate some of the previous problems around sprint management. An origin board’s permissions are considered when starting or stopping a sprint and so an issue added in error from outside that scope will no longer impede the team using the sprint. Additionally, we will be improving the context and identity for sprints within JIRA to further reduce unintentional use of incorrect sprints.

Further details are available in this blog post.

Kind regards,
Martin
JIRA Software

This feature is now available for both JIRA Software Cloud and JIRA Software Server, the server release version is 7.1.0.

Kind regards,
Martin
JIRA Software