Aha!
Overview
Aha! is a cloud-based product roadmap solution that allows practitioners to capture their visions and goals while keeping track of the release that encompasses the work involved.
The tool enables product managers, engineers, and product development teams to drive product strategy and bring raw concepts to finished product. Practitioners are able to link strategic goals and initiatives to their work, create visual roadmaps for upcoming plans, and manage agile development.
Connector Setup Details
This section describes the basic steps needed to prepare your Aha! instance for use with Viz.
Minimal User Permissions & Viz User
We recommend that you create a new user within your external tool, to be used only for Viz. This is the user information you will enter when setting up your tool connection within Planview Viz. By creating a new user, you will ensure that the correct permissions are granted.
In general, your Viz user account should have sufficient permissions to read artifacts in your tool.
Your user should have a secure password or token. Please be aware that Viz will not allow you to save a tool connection utilizing a weak password/token, such as 'tasktop.'
Connecting to the Aha! Repository
Standard Authentication
Required Fields:
-
Location/Connection URL
-
Example Format: https://server.aha.io
-
-
Username
-
Password
API Key
Required Fields:
-
Location/Connection URL
-
Example Format: https://server.aha.io
-
-
API Key
Supported Artifacts
Supported Work Items
|
Supported Work Item Type |
Applicable Repository Versions |
Unique URL? |
|---|---|---|
|
Idea |
Any supported repository version: |
Yes |
|
Feature |
Any supported repository version: |
Yes |
Supported Containers
|
Containers that can be modeled as Flow Items |
Applicable Repository Versions |
Unique URL? |
|---|---|---|
|
N/A |
||
|
Containers used to define which artifacts are included in an Artifact Set |
||
|
Projects See functional limitations table below. |
Any supported repository version: |
N/A |
Supported Field Types
Planview supports configuring rule-based modeling (i.e., conditional modeling) using the field types shown below.
Note: If one field of a given type is supported, others that are also that type in theory should also work. However, sometimes there are instances in which this is not the case due to the repository. So, while we can claim support for fields at the type level, there is a chance that some specific fields of a given type will not function properly.
| Standard Field Type | How is field type referenced in the repository? | Sample Repository fields supported |
|---|---|---|
|
|
Text | Name |
|
|
Choice List | Type |
|
|
Tags Categories |
String
Functional Limitations
|
Category |
Limitation |
Applicable Repository Version |
|---|---|---|
|
Good to Know |
Projects In the Product Modeling tab, selection of projects for an artifact set is possible, however, in the Artifact Modeling tab, artifact types will show 'No Project.' This is because the Aha connector defines the artifact schema with Type separate from Project. |
Any supported repository version: |