Child records eligible to import to multiple workspaces are automatically importing to the workspace where the parent record is integrated to

What is the challenge?

If I am using an integration template to manage multiple Jira projects which can have parent/child records spanning multiple Aha! Workspaces (many to many relationship), If I add a child record from one Jira project to an integrated parent in another Jira project, and this child record is eligible to import into multiple workspaces, it is automatically assuming I want to import it to the workspace where the parent record lives. That may not be the case as I have other workspaces supporting this work.

What is the impact?

Records may import to the wrong Aha! workspace

Describe your idea

I would like to manually approve this import to designate which workspace I'd like the child record to import to