Issue Summary

Sprints: User is not informed that when moving Sprint from one PI to another, the sprint is mapped to very first Anchor from new PI

Steps to Reproduce

1. Login
2. Open any PI with Sprints.
3. Open any Sprint in it
   #Reassign Sprint to different PI

Expected Results

Map the anchor to the date range that includes the sprint's end date, or to the Anchor that is closest to Sprint's End date

Actual Results

Sprint is mapped to First Anchor of the new PI

Workaround

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