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
Next: Root
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.
Hi,
I tried using the auto-schedule and it scheduled some of the sprints to be over-allocated. at first I thought it was a release dead-line issue, but another sprint within the same release is under-allocated. nevertheless I removed the limitation on changing releases and it still did the same scheduling. Now what I am missing is:
1. Why does it choose to over-allocate the sprint? Is there any way to see some constraints that caused it? what tools do I have to understand the logic behind it?
2. What tools do I have to fix it except for manually changing the scheduling?