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

Sprint still has capacity but issue is scheduled in next sprint

I have a sprint (Sprint2) which there is still 24 hours free capacity.



However, another issue which only has 8 hours is scheduled to next sprint (Sprint3) instead of Sprint2. 


Here is the information for these 2 issue, wmam-316 is the one in Sprint2, wmam-317 is the one in Sprint3 and can't be scheduled to Sprint2. There is no dependency between these 2.2018-10-21_105756.png

Anyone has any clue why does this happen?

1 answer

1 accepted

0 votes
Answer accepted

Answer for myself, it turned out that if earliest start is greater than the date that sprint start, it will be pushed to next sprint.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events