Hi All,
Usually its the other way around, people are not able to start / complete sprints due to permission issues. My problem is that I have a project where almost anyone can start / stop sprints. The only permission that is asked is the schedule issue permission (if someone does not have this you cant move the stories to the new sprint) but thats it. The Manage sprint permission row is literally completely empty. The permission helper gives the following message: "Status: Kozma Zsolt has the {permission} permission" - which is hilarious.
I'm an org admin and a site admin. I have managed many instances but never seen this.
Am I missing something? :)
Hi @Kozma Zsolt Welcome to the Community!
Please refer to this thead- https://community.atlassian.com/forums/Jira-questions/Can-t-complete-sprint-even-with-Admin-rights-amp-manage-sprint/qaq-p/1384439
Hi Manoj,
Thanks for your reply, but my problem is different. We can manage the sprints, and that is the problem. The sprint involves only 1 project, which has a unique permission scheme. In the permission scheme the Manage sprint permission is not assigned to anyone. Literally there is not a single user or group or role that is assigned to that permission in the scheme. Still many (afaik all of them) people are able to start and close sprints. I even removed the project admin permisson I'm still able to start and close sprints.. I tried to restrict it to groups, roles, single users, none of them works.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.