After JIRA upgrade to 7.6, some sprints won't close. Perms?

[Brad Taplin]

Hello. We upgraded JIRA 6.4 to 7.6. Most of 8000+ users are happy, but in a few projects admins cannot close sprints. In at least one of these projects the perm scheme does grant Manage Sprints to all admins, but not explicitly to the Scrum Master role.

I just added her to that role, and it to that perm. Are there other factors? Other projects' sprints can be closed by their admins We are looking for differences between projects.

BTW we saw the same in a nearly duplicate (UAT) environment, tried cache-clearing per https://community.atlassian.com/t5/Questions/Cannot-close-a-sprint-in-Greenhopper-Project-admin-required-for/qaq-p/263708, but she confirmed that even after we did so the problem persisted there. It was just one test, we could dig deeper.

[Tzu Hau Chai]

Does the board JQL filter where the sprint is located covers issues across different projects? If so, you will need permissions in all the projects in order to close the sprint.

You can verify what projects are in scope in the board config > general >projects in board