Aha! Roadmaps | Team status mapping

Aha! Develop and Aha! Roadmaps users share work items, but because engineering and product teams have different workflows, there are two status fields on every epic, feature, or requirement shared between the two products. Two teams, two workflows, one record.

However, sometimes the product team's workflow relies on engineering updates. PM review cannot start until the development feature is code complete, for example. To find the perfect balance between independent and collaborative workflows, Aha! Roadmaps users can map Aha! Develop team statuses to their own Aha! Roadmaps workflow statuses. If an Aha! Develop status changes, product managers can decide whether that should automatically trigger an Aha! Roadmaps status change.

To configure team status mapping, navigate to Settings ⚙️ Workspace Status automation in Aha! Roadmaps. To do this, you will need to be a workspace owner in the Aha! Roadmaps workspace and at least a viewer in the Aha! Develop team(s) you want to map together.

Team status mappings pair very well with automation rules — particularly the ability to dynamically assign users. Once a feature enters "In PM Review," for example, you can trigger an automation to assign the correct product manager a to-do to review the feature.

Top