I've read as much material as is returned on the topic but am not connecting the dots. I think best practice might be to explicitly set a person with the administrators role under the people project settings?
Nothing was mentioned in this article that by title I would have expected to touch upon this.
Hi Brad -Welcome to the Atlassian Community!
Yes, for every new project you create, you have to manually add someone to the Project Administrator role. Even if you create the project based on an existing project, it will not copy the People over from the original project.
There IS a setting in Settings > System but it would put the same person or group in Administrator project role for ALL company-managed projects, which I don't think you want to do.
Thank you for the quick response. Confirming with my end users now.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi John, my user got back to me today sharing that he's still not able to manage a sprint in the new project I created. Pretty open ended problem that I'm still trying to poke around and find the problem to, but any insights you could suggest would be welcomed.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey Brad - open the Permission Scheme for that project and try the Permission Helper for that user for the Manage Sprints permission. You can choose whatever issue on that project that you like. It should tell you exactly what is wrong.
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.