Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

How to lock the Sprint so that the team cannot add any more tickets?

I would like to know what would be the detail action items for Jira Software Scrum Project for me to be able to lock the Sprint so that the team cannot add any more tickets throughout the sprint? 



4 answers

2 accepted

1 vote
Answer accepted
Jack Brickey Community Leader Dec 20, 2019

this is controlled thru the "Manage sprints" permission. project settings > permissions

Hi Jack.  What is the permission setting to do this?  We're on Jira Data Center V8.15 and I don't see an option for this.  That is unless you're referring to locking down "Create Issues" for users.


I have the same issue. I assume there has been a Jira update. Was this function removed?

Jack Brickey Community Leader Aug 25, 2021

@chris are you on cloud?

0 votes
Answer accepted

Hi @Donata ,

There is no way to "lock" the scope of a sprint, whether or not the sprint has been started. There was an open request to add this feature, but Atlassian recently decided not to pursue it.


@Donata , the others that have posted are can use permissions to prevent people from adding issues to a sprint.  To clarify my answer...if people can add to a sprint then they can throughout the sprint; there isn’t a way to  allow issues to be added until a point where the sprint gets “locked” and no more issues are added.

Hope this helps,



I did this with automation. When I was ready to lock the sprint down, I created a rule that basically says "if a ticket is edited and they set the sprint value to this particular (closed) sprint, then clear the sprint field (thus moving it back out). If we need to add something authorized, we can just disable the rule.  Next sprint, I'll update it to lock down THAT sprint. Simple but it works.

That's a smart way to do it! Thank you for sharing.

0 votes
Taranjeet Singh Community Leader Dec 20, 2019

@Donata You can achieve this using both "Schedule Issues" and "Edit Issues" permissions for your project to restrict only specific users/groups to have these permissions and thus able to add issues to Sprints.


Please see this page for more details on what permissions are used for which Sprint related actions:


Hope it helps!

Taranjeet Singh Community Leader Jan 03, 2020

@Donata Did my answer help resolving your issue? Please let me know and if there are any further questions. Please don't forget to mark the answer as accepted in case it was useful, it will help others in the community as well.

I think the question is / or my question is Once the sprint has started no one should be able to add any stories. Maybe only 1 role can do it for the active sprint.

Eg Leads can plan Future sprints only mangers can add in current 

Can one us some validator to check if the sprint is active? 

Any suggestions will be appreciated.

Like Gary Shaw likes this

Suggest an answer

Log in or Sign up to answer