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?