Date ranges should adapt to sprint changes

If you have a record assigned to one sprint and it later gets pushed to a later sprint, the date range (when set to calculate from sprints) does not reflect the full time spent in multiple sprints

The date range is not reflective of how much time was actually spent on the record

The sprint date range should adapt to multiple sprints with an accumulative date range from the earliest sprint start date to the furthest sprint end date for sprints this record has belonged to