Hi folks, I have a scrum master who is getting this error when she tries to close her sprint:
"To update this sprint you must have Project Administrator permissions for all of the following projects: Project X"
She has all the right permissions so I don't see what the problem is. As a JIRA admin, I was able to close the sprint for her. We don't know if she'll have the same problem again on the next sprint.
This issue is similar to others posted, except that other errors require access to more than one project, not just the one we're working in.
Update 11/14/2014: Just found out that when I closed Project X's sprint, I also closed Project Z's sprint. There was no indication in the error or the queries I ran that Project Z was at all implicated in Project X's sprint.
As per our Ending a Sprint documentation: "You must have the JIRA 'Project Administrator' permission for all project(s) with issues included in the sprint to complete it. If you cannot complete a sprint, check whether your sprint has issues from a project where you are not a project administrator.
I'd say to review the issues on the sprint in order to double check if there are no other issues from a different project in that sprint.
Hope it helps to clarify!
I saw that advice earlier and tried that. I ran a query on the sprint ID I'd just closed AND project not in /[current project/]. The search had no results. There were only 84 issues in that sprint and I could see by looking at their issue numbers that they were all in the correct project. The error was not asking for admin rights to multiple projects, but only for the project that we are working in. Very strange.
""You must have the JIRA 'Project Administrator' permission for all project(s) with issues included in the sprint to complete it."
Does this also affect linked issues from another project?
A PM I'm working with has just spent several hours removing issue links and labels from all the issues in his sprint in order to try and get past this error message. All the issues in the sprint are from the same project, but for some weird reason, JIRA Agile says he'd need Project Admin for another project.
Issues from the other project are in a "must be completed before" relationship to issues in his current sprint.
If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot