How to lock down a Sprint so that no more tickets can be assigned to it?

We are currently using GreenHopper to manage our Sprints.

How can I lock down a Sprint after a Sprint Planning so that no more tickets can be added to the Sprint for the duration of development?

Can I do this by Role?

3 answers

This widget could not be displayed.
Paul Greig Atlassian Team May 08, 2013

Hi Surinder,

The permission to add issues is controlled by the 'Edit Issues' permission in the Project Permissions. You could provide a role with permission to edit issues, this would however also affected other edit actions on those issues.

Cheers,

Paul

Hi Paul,

Your recommendation does allow me to achieve what I want but it also cripples other roles and their ability to edit issue. I don't think your recommendation is feasible in this scenario.

It would be great if the actions to add/edit/delete Sprints and adding/removing tickets to these sprints be pulled into a different role (e.g. ScrumMaster)

Paul Greig Atlassian Team May 24, 2013
Surinder, while that is not currently possible as the 'administer projects' permission only controls the add/edit/delete of sprints. I would like to point out an open request to incorporate an additional role for addition and removal of issues to sprints: https://jira.atlassian.com/browse/GHS-5977
This widget could not be displayed.

Hi Paul,

Thanks for the link to the open request. How do I resolve this question?

This widget could not be displayed.

It would be great if the actions to add/edit/delete Sprints and adding/removing tickets to these sprints be pulled into a different role (e.g. ScrumMaster)

Doesn't sound right.

While I understand why some people would not like the Sprint backlog to be adjusted further, but Scrum-by-the-book doesn't discourage us from being pramagtic - Scrum is really about inspect and adapt, not just on the Sprint and daily basis but at any time.

The only people who can add, modify, remove things in the Sprint backlog (during the Sprint Planning and Daily Scrum) are the Developers. They should know best about the situation and priority, and collaborate with the Product Owner whenever necessary. The job of the Scrum Master is to facilitate (and remove impediments), not to have her hands to control.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted yesterday in United States

Local Atlassian Research Workshop opportunity on Sep. 28th

We're looking for participants for another workshop at Atlassian! We need Jira admins who have interesting custom workflows, issue views, or boards. Think you have a story to sh...

31 views 0 0
View post

Atlassian User Groups

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!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you