Cannot start/close sprint since latest Cloud release

Summary

According the documentation:

• https://confluence.atlassian.com/cloud/blog/2015/12/jira-software-sprint-management-first-release

  As previously blogged, we're now shipping the first release of the Manage Sprints permission changes on 6th December 2015. With the first release, the Manage Sprints permission will be created, and existing users with the Administer Project permission will be assigned the new permission for the same projects. The same sprint actions will check for the new permission, so it will be business as usual.
  The following sprint-related actions will now be assigned to specific users in your team, thereby separating these from the actions that come with the Administer Project permission:

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

Users should now be able to manage Sprints, this include Starting and completing sprints, by only having this new implemented permission: "Manage Sprints" permission.
However, some users who have both "Manage Sprints" and "Administer Projects" are not being able to fulfil any of the actions above unless they are also "JIRA Administrators", a permission that shouldn't be needed.

Environment

JIRA Agile Cloud

Steps to Reproduce

1. Create a board and a new project;
2. Create a user with only Manage Sprints permission on this project;
3. Try to start the Sprint with this user.

Expected Results

Having the Manage Sprints permission should be enough to enable the user to complete the actions described above.

Actual Results

Even with Manage Sprints, Edit Issue, Schedule issue and Administer Projects over all projects retrieved by the board's filter, the user can't start/complete

Workarounds

Suggested

• Provide user "Manage Sprint" permission across all permission schemes

Alternatives

• Create another temporary board without any sub query Eg: Project = TEST order by RANK ASC, create the sprint there. Use quick filter to filter the fields instead.
• To start sprint, get administrator to initiate the sprint at this moment.
• Provide a user "JIRA Administrator" Global Permission to Start/Stop any sprint