Features and Epics should move to integrated parent Release upon updates

What is the challenge?

If you introduce Version<>Release mapping to an existing integration or you link a record to an existing Jira record, subsequent updates are creating a new Aha! release (linked to the Jira issues's Fixed Version) but they are not moving the child record over to the newly created Aha! release

What is the impact?

This requires manual work to get the release synced up or you must do an Update Records which runs across the entire integration

Describe your idea

If the parent release is created in Aha! the child Feature or Epic should be moved over