Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Product Q&A
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Events
Community resources

Sprint still has capacity but issue is scheduled in next sprint

sebastianhsu
sebastianhsu
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Get involved
October 20, 2018

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?

Answer
Watch
Like Be the first to like this
492 views

1 answer

1 accepted

0 votes
Answer accepted
sebastianhsu
sebastianhsu
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Get involved
October 21, 2018

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.

Reply

Suggest an answer

Log in or Sign up to answer
Portfolio for Jira
Advanced planning
TAGS
AUG Leaders

Atlassian Community Events

    See all events