For client data protection reasons, only 4 resources on our project are allowed user management rights. There are other users who run scrum teams and need to be able to set up sprints on the Agile Boards. It appears that you can only grant permissions to create, start and complete sprints by assigning the Administer Project role - which also includes permission to assign administrator rights to others.
Am I missing something?
Is there a way to control sprint management permissions distinct from other permissions?
If not, is there a plan to do so in future?
Indeed you are right. Without the Administer Project the user won't be able to start, create.. Etc. sprints. The reason behind it, in the normal world of Agile, namely the project lead the one starts, plans the sprints, so without this permission, that wouldn't make sense for any user to start or plan because is not confirming the real world scenario.
Thanks for getting back to me.
I'm not sure I agree that there is a "normal world of Agile". Across the projects I've worked, each client and project team has implemented a slightly different flavour adhering in varying degrees to the Agile principles and with different organisation structures that reflect the work they have to do or the landscape they're operating in.
I can understand why this simplification has been made, but are there any plans to split Administer Sprint from Administer Project?
As a Belgian, beer-lover and home brewer, beer is one of my great passions. I love the fact that with just a few ingredients (usually just water, hop and malt) you can create so many different tastes...
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