Move epic/feature to default release when integrations unlink the release

What is the challenge?

When an integrated epic or feature is moved in a dev tool (Jira or Rally) to an "unscheduled" release, the relationship in Aha! is null and no change occurs. This is problematic because the release was changed but the Aha! relationship, roadmaps and reports do not reflect the correct plan

What is the impact?

Jira and Rally users can have plans out of sync

Describe your idea

When an integration includes releases in the mappings, an epic or feature in the dev tool is removed from a linked release and the release link is blank, move the epic or feature to the workspace default release setting to reflect the change made from the dev tool