We have a sprint which cannot be closed. The error messages says I must be a project admin in the project the sprint is in, and another project. I assumed this was because of issue links, and went back and removed, however it will still not allow the sprint to be closed unless I add myself as admin on the other project. This is not the right procedure. What items could be contaminating my sprint from another project that would block me from completing it in this way? Is there a bug in the system because issue links or other items outside the sprint project are influencing the ability to close the sprint?
To update this sprint you must have Project Administrator permissions for all of the following projects: Project A and Project B
BTW this is for JIRA version 5.2.7 and Greenhopper 6.1.2
We did not have this issue until this latest sprint, and we recently did an upgrade from 5.1.1 JIRA and 6.0.x GH. We are not sure this casued the issue, or if some use case of Greenhopper and JIRA changed with the team, but somethign from Project B is blocking us closing the sprint in Project A, and issue links have been cleared. Still something blocking.
It seem the problem that you encounter was related to file corrupted happen in JIRA instance, please try the following steps to rebuild the file again:
Hope it helps.
I just had this exact issue reported.
Will a background index suffice or do I really need to completely rebuild the index and delete the plugin cache?
If I have to do a complete rebuild, I will likely have to wait until a maitnenance window as we have a large instance and indexing will take some time.
Great suggestion Matt. I had just checked this but the issue history does not show them as being moved.
To test, I created a test user and assigned it as an administrator to the project but the user still could not complete sprint. I added a group this user was in to the Administrator role but with no luck. Interestingly enough, when I added the user to the jira-administrators group they could complete the sprint. Unfortunately, I cannot do that for the real user that is experiencing the problem.
Here is an additional answer that resolved my problem. While all the issues were from a single project the users board filter was set to only look for the fix version. Adding in a filter for the project allowed the user to mark the sprint complete.
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
Hey everyone! My name is Natalie and I'm an editor of the Atlassian Blog and I've got a question for you: What's your favorite quote about teamwork? We've compiled a list here, along with...
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