This article is part of a series of settings overview articles:
Account |
Workspace |
Integrations |
Personal |
If you have connected your Aha! Roadmaps account with Aha! Develop or Aha! Teamwork, you can configure the connection with these settings.
Click any of the links below to skip ahead:
Configure (Aha! Develop or Aha! Teamwork Advanced plan)
First, you can import reported issues from an ideas portal in Aha! Roadmaps directly into Aha! Develop or Aha! Teamwork to streamline service requests. To do this, you first need to configure an Aha! Roadmaps workspace to allow Aha! Develop or Aha! Teamwork teams to import ideas from portals associated with that workspace.
Import ideas: Check this box to allow Aha! Develop or Aha! Teamwork teams to import ideas from your workspace.
Click Update Aha! Develop configuration when you are done.
Second, you can associate your Aha! Roadmaps workspace with an Aha! Develop or Aha! Teamwork team (or many teams). When you do, you can compare the settings that will most affect your collaboration.
Add a related team: Choose an Aha! Develop or Aha! Teamwork team to associate with your workspace. When you do, you will see a comparative view of your Capacity planning and Terminology settings, and whether you have automated workflow statuses.
Click on any setting to adjust it. To adjust an Aha! Develop or Aha! Teamwork team's status, you must have owner permissions to that team.
Click More options, then Remove mapping to undo your workspace's association with that team.
Status automation (Aha! Develop or Aha! Teamwork Advanced plan)
Next, you can automatically update record statuses in Aha! Roadmaps as engineering work progresses. Connected accounts share records (epics, features, and requirements) so product, project, and engineering teams can focus on the same work items. But since product, project, and engineering teams have unique workflows, there are two statuses on each in connected accounts — one for product teams and one for engineering and project.
Sometimes the product workflow relies on engineering or project status updates — a PM review cannot start until the engineering team has completed development, for example. Instead of relying on manual status updates, you can map Aha! Develop or Aha! Teamwork team statuses to your Aha! Roadmaps workflow. This way, changes to a record's status in Aha! Develop or Aha! Teamwork would automatically update that record's status in Aha! Roadmaps.
Team status mapping flows one way, from engineering and project to product. Changes to the Aha! Develop or Aha! Teamwork team status trigger updates to the Aha! Roadmaps workspace status.
To do this, you need to be a workspace owner in the Aha! Roadmaps workspace where you want to add the status mappings and have at least viewer permissions to the Aha! Develop or Aha! Teamwork team(s) you want to map to your workspace.
If your workspace is not yet connected to any Aha! Develop or Aha! Teamwork teams, select a team first. Then you will see the Aha! Develop or Aha! Teamwork team's workflow statuses on the left of a card. Under the Epics, Features, or Requirements columns, click on any status dropdown to map the Aha! Develop or Aha! Teamwork team status to your Aha! Roadmaps workflow status for that record type.
Note: If you do not see an option to map epic statuses, make sure you have enabled epics in your workspace.
For example, you may want to focus on features. So you map the Aha! Develop team status "Ready for review" to the Aha! Roadmaps workflow status "In PM review." This mapping means that any time an Aha! Develop feature moves to the "Ready to review" status, the Aha! Roadmaps status on that feature will change to "In PM review" and your team will know they have work to do.
Note: 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.
Click Update team mappings to save your work. You can repeat this process with as many Aha! Develop or Aha! Teamwork teams as you like.