Using the Autoscheduler with multiple epics on Jira Plans could cause Epics to stretch over a team's capacity

Issue Summary

When using Jira Plans (Advanced Roadmaps) and trying to use the Auto Scheduler functionality with a large amount of Epics, in some cases it stretches one of them for many many days (+400) even though its start and end dates are already set and it doesn't have any dependencies or child issues.

If you change the rank of the Epic that is being stretched over many days, then another one gets stretched.

Steps to Reproduce

It's not easy to reproduce as it depends mainly on the structure of the plans and the nature of the Epics included.

1. Create a project with multiple Epics, some of them with child issues, some of them without. Set some start/end dates for them.
2. Create a few releases, teams and sprints and assign them to some of the epics.
3. Run the auto scheduler, selecting "All values" for sprints, teams and releases.

Expected Results

The epics should be scheduled accordingly, respecting the team's capacity and the sprints.

Actual Results

In some cases, one of the Epics gets stretched over many days without any reason in particular.

Workaround

The easiest way to overcome this, is to just accept what the auto scheduler is setting and then change the dates on the Epic manually.