What is the challenge?
When multiple Aha! Roadmaps workspaces are integrated to the same development project, Automatically import all records is unavailable because a record could land in the wrong workspace.
Administrators can set import filters on each integration, but those filters cannot be used to automatically route new standalone records to a single workspace in this setup.
What is the impact?
Product teams must review and approve imports manually, even when only one workspace's filter matches. Records that land in the wrong workspace need to be moved.
Describe your idea.
Let administrators use per-integration filters to route automatic imports from a shared development project. Support JQL in Jira and equivalent filters where supported in Azure DevOps and other development systems.
Automatically import a new record when exactly one workspace integration matches. If several match, send it for review without importing it. If none match, leave it unimported.