Parent issue inherits Sprint start date as Scheduled Start Date every time a new Sprint is started containing issues in the Parent

Issue Summary

The 'Scheduled Start Date' of an Epic is not retaining the initial/first 'Sprint Start Date' of the the issues contained in the Epic.

Environment

• JPO 2+ (not including the 'new interface')

Steps to Reproduce

1. Set up project with an Epic and issues, and link issues to the Epic
2. Create Sprint, and add a few issues to it (not all your issues)
3. Set up new Plan with this new Project
4. Start Sprint, and note the scheduled start date applied to the Epic in the Plan
5. Complete Sprint
6. Create new Sprint, and add issues
7. Start Sprint, and observe in plan this new Sprint Start Date is inherited by the Parent/Epic - overwriting the original Scheduled Start Date

Expected Results

Oldest Sprint Start Date held as the Epic's Scheduled Start Date would be held and not overwritten.

Actual Results

Newest Sprint Start date overwrites the Epic Scheduled Start Date

Workaround

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