You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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.
Anyone has any clue why does this happen?
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.