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.
When a third-party tool is required or preferred by teams, Planview Hub enables seamless and bidirectional integration to synchronize artifacts between the multiple tools and infrastructure, encouraging accountability and transparency across teams and departments.
Key Features and Benefits
- Improves visibility into the overall status of projects by using boards to visualize project status and WIP (work in progress).
- Visualize incoming data and act as a central point of truth for your projects or project portfolio.
- Eliminates the need to manually update the virtual boards, or use brittle point-to-point integration techniques.
- Synchronizes artifacts to your tool of choice, allowing free flow of information between and improving team collaboration.
Common Integration Patterns
Demo Videos
Connector Setup Details
This section describes the basic steps needed to prepare your Aha! instance for use with supported Planview products. Note that additional fields for synchronization or configuration of queries may be required depending on the requirements of your integration.
Minimal User Permissions & Hub User
We recommend that you create a new user within your external tool, to be used only for your Hub integration. This is the user information you will enter when setting up your repository connection within Planview Hub. By creating a new user, you will ensure that the correct permissions are granted, and allow for traceability of the modifications that are made by the synchronization.
In general, your Hub user account should have sufficient permissions to create, read, and update artifacts in your repository. However, depending on the use case, your user may need different permissions. For example, if you are only interested in flowing data out of your repository, your user may not need to have full CRUD access, as the 'create' and 'update' permissions may not be needed.
Your user should have a secure password or token. Please be aware that Hub will not allow you to save a repository 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
Learn more about how to set up your repository in Planview Hub here.
Other Configuration Settings
Rich Text
Supported rich text elements are:
-
All standard HTML elements (headings, bold, italics, underline, tables, lists, etc)
Person Reconciliation
For person reconciliation, the following fields are available:
|
Fields Used for Hub’s Default Person Reconciliation Algorithm (Standard Field) |
Field Names for Person Reconciliation Extensions |
Label in Aha |
|---|---|---|
|
|
|
Email Address |
|
ID |
id |
ID |
|
Display Name |
name |
Name |
|
Username |
$username |
Username |
Supported Features
Special Features Supported
You can learn more about special features in Planview Hub here.
|
Feature |
Custom Type Supported? |
Applicable Hub Version |
Applicable Repository Versions |
Default Maximum Size in Repository |
|---|---|---|---|---|
|
|
N/A |
N/A |
N/A |
N/A |
|
|
N/A |
Planview Hub: 22.4 and later |
Any supported repository version: |
N/A |
|
|
N/A |
Planview Hub: 22.4 and later |
Any supported repository version: |
N/A |
|
|
Yes |
Planview Hub: 22.4 and later |
Any supported repository version: |
N/A |
Time Worked (Worklogs)
ImpersonationSupported Artifacts
Supported Work Items
|
Supported Work Item Type |
Applicable Hub Versions |
Applicable Repository Version |
Unique URL |
|---|---|---|---|
|
Idea |
Planview Hub: 22.4 and later |
Any supported repository version |
Yes |
|
Feature |
Planview Hub: 22.4 and later |
Any supported repository version |
Yes |
Supported Containers
|
Containers that can synchronize between repositories |
Applicable Hub Versions |
Applicable Repository Versions |
Unique URL? |
|---|---|---|---|
|
N/A |
|||
|
Containers used to define the boundary of a collection (when clicking 'Manage Projects' on a collection) |
|||
|
Projects |
Planview Hub: 22.4 and later |
Any supported repository version: |
N/A |
|
Containers used for artifact routing |
|
|
|
|
Projects |
Planview Hub: 22.4 and later |
Any supported repository version: |
N/A |
Supported Field Types
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 synchronize properly.
|
Standard Field Type |
Does Hub support custom fields of this type? |
How is field type referenced in the repository? |
Sample Repository fields supported |
Particular Repository Fields NOT Supported |
|---|---|---|---|---|
|
|
|
Text |
Name |
|
|
|
|
Choice List |
Type |
|
|
|
|
|
Tags Categories |
|
|
|
|
Date |
Status Changed on Due Date |
|
|
|
|
|
Updated At |
|
|
|
|
Number |
Detailed estimate |
|
|
|
|
|
Score Progress |
|
|
|
|
|
Description |
|
|
|
|
|
URL Reference |
|
|
|
|
|
Promoted to Feature Record Links |
|
String
Functional Limitations
|
Category |
Limitation |
Applicable Planview Version |
Applicable Repository Version |
|---|---|---|---|
|
Third Party API Limitation |
Read Only and Required Custom Fields Due to limitations in the API, Read Only and Required custom field constraints set in Aha's layout settings are not recognized. |
Planview Hub: 22.4 and later |
|
|
Third Party API Limitation |
Person Fields The Aha! connector does not return any errors when it fails to update a person field. |
Planview Hub: 22.4 and later |
|
|
Third Party API Limitation |
Custom Scores Due to limitations in the API, custom scores cannot be synchronized unless they've been updated at least once. |
Planview Hub: 22.4 and later |
|
|
Third Party API Limitation |
Score Fields The 'Score' field is only supported as a read-only field. |
Planview Hub: 22.4 and later |