Support Movement of Requirements to Different Features in Other Workspaces

We recently integrated JIRA stories mapped to Aha! requirements but are running into an issue with stories moving from JIRA epic to JIRA epic. Currently, Aha! supports stories moving from epic to epic, but only if those epics are mapped to features that live in the same Aha! workspace.

However, our teams are cross-functional and work across multiple workspaces. Stories frequently move from epic to epic. Linked Aha! records currently do not move from one workspace to another based on how their linked Jira records are moved.

This is what we hope to achieve:

• Workspace A is integrated with a JIRA Project 1.

• Workspace B is integrated with Project 1.

• Workspace A has a feature with a child requirement that is linked to an epic and story in Project 1.

• Workspace B has a feature with a child requirement that is linked to a different epic and story in Project 1.

• The story that's linked with the requirement in Workspace A is moved to the other epic that's linked to the feature in Workspace B.

• The requirement that's originally in Workspace A should move to Workspace B.

Lastly, Aha! should ideally support another scenario in which Workspace B is integrated with Project 2. If a story moves from one epic to another epic that lives in a different JIRA project, we hope to achieve the same outcome: the Aha! requirement moves to the right feature.