Hello everyone,
We use the same permission scheme across many projects. It works perfectly in all of them but one. In this specific project, people added to the project with the Manage Sprints permission cannot complete a Sprint. The button is greyed out, and they get the message you need the Manage Sprints permission to complete the sprint.
What am I missing?
I completed the Sprint as an admin, and now the team can start and complete sprints again. Not sure what was wrong with that particular Sprint. Thank you all for your suggestions!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @alessioLepaya
Welcome to the Atlassian community!
Can you show us the actual JQL of the board filter?
It must explicitly name the project(s) from which issues will be selected. Trying to filter using Components, Labels, or values for fields that you use in only one project is not the same as explicitly identifying the source project.
If you have an OR clause in the filter, you may have constructed it in such a way that a part of the OR clause is being interpreted as not explicitly identifying the projects.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It is also possible that the sprint had an errant issue from some other project that was not within the board scope. Issues outside the board scope can still be added to sprints by directly editing the Sprint field in the Issue.
You could do a search in Advanced Issue Search for issues in that sprint to double check.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I thought the same, but there weren't issues from other projects in that Sprint. Thank you for your input :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I will suggest you take a second look at the permission scheme and locate the part that says Manage Sprints. Look at the roles on the right that have been mapped to the managed sprint and make sure the user in question has been assigned one of those roles.
If you are not Jira admin but project admin then you can navigate to the permission by clicking on
Project Settings -> Permissions
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @alessioLepaya ,
welcome to the Atlassian community!
Please could you check if that user has also Edit Issue permission?
Fabio
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.