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

Sprint still has capacity but issue is scheduled in next sprint

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

2018-10-21_105311.png

 

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

2018-10-21_105456.png

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
TAGS
Community showcase
Published in Advanced Roadmaps

3 short videos to help you get started with Advanced Roadmaps

Hi community, I’m Roi, a product manager working on Advanced Roadmaps for Jira. While Advanced Roadmaps is a powerful tool to plan and track work at scale, we know it can be challenging to get star...

3,675 views 23 15
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you