Aha! Roadmaps users share work items with Aha! Develop or Aha! Teamwork users, but because product, project, and engineering teams have different workflows, there are two status fields on every epic, feature/activity, or requirement shared between the two products. Two teams, two workflows, one record.
However, sometimes the product team's workflow relies on engineering or project 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 team statuses to their own Aha! Roadmaps workflow statuses . If an Aha! Develop or Aha! Teamwork 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 or Aha! Teamwork 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.