Auto scheduling doesn't return correct results for time-based estimations with planned capacities

Issue Summary

Auto-scheduling doesn't return correct calculation results for time based estimations with planned capacities

Steps to Reproduce

1. Configure a plan to use time-based planning unit (days or hours)
2. Create a few issues with estimations, for example 20 hours
3. Update the planned capacities for a couple of future sprints, for example 40 hours (the default is 200 hours for 2 weeks)
4. Run auto-scheduling

Expected Results

Planned capacities are considered by auto-scheduling and issues are pushed to further sprints when there is no enough capacity in current sprint

Actual Results

Issues are scheduled into the same sprint and allocated time exceeds the sprint capacity

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available