It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Limit sprint points for scrum sprint

I've search quite a bit and found nothing so I think I may be using the incorrect terminology.

We run JIRA (v7.3.3) and IRA Agile (v7.3.0-DAILY20170302150106) hosted on our servers. 

We successfully use JIRA but there is one major issue we have. There is a constant battle between business and development teams on sprint size/points available. I would like to set a number for a given sprint, 100 for example. They move stories from the backlog to the sprint. For example, 90 points and leave 10 unallocated for things that come up during the sprint. The problem is that more and more stuff gets moved into the sprint and we blow past the 100 mark every sprint. 


What I would like is, once that limit is set for a sprint, when business adds something to the sprint that push points over the limit, the lowest priority thing gets moved out of the sprint into the backlog so that they have a notification of the consequences. It seems like Kanban boards may have this feature, but I can't seem to find it on the scrum boards, which we are already invested in.

Is this, or something similar possible? I'm trying to find a technical solution to a problem where social engineering has repeatedly failed.

I did notice the following thread, but I think that is for newer versions of JIRA Cloud, as I don't have that Agile button they mentioned.

Thank you 


(PS, sorry for the formatting here? I don't see a way to change font size on pasted text).

1 answer

1 vote

Hi Adam,

What you're trying to do would require some scripting but let me see if I can lead you in the right direction.  It appears you have a few needs:

1.  Limit the number of issues that can be added to a sprint
2.  Move the lowest ranking issue to the backlog

In regards to limiting the number of issues that can go into a Sprint, currently that isn't possible.  I would advise going to JAC and creating a Suggestion request to limit the number of issues that can be added to a sprint and add your use case to the comments.

The second part of your request is to move the lowest ranking issue to the backlog.  You can find the issues in the sprint in ascending order using the following rest call/endpoint:


You can test this in the browser with something such as:


In regards to moving the issue to the backlog the Move issues to backlog section of the JIRA Software Cloud REST API reference guide using a POST to the following end point:


That would come out to a cURL of:

curl -D- -u UN:PW -X POST -H "Content-Type: application/json" --data '{"issues":["ISSUE-KEY"]}' "http://localhost:8080/rest/agile/1.0/backlog/issue"

Hopefully that helps!



Suggest an answer

Log in or Sign up to answer
This widget could not be displayed.
This widget could not be displayed.
Community showcase
Published Feb 26, 2019 in Jira Software

How to prevent the propagation of unused project schemes, workflows & screens in Jira software

Atlassian ranks project attributes as the third most important factor impacting performance in the category of data. It’s not surprising, since project attributes are precisely the rules used to ma...

1,130 views 1 13
Read article

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