Map fields between Aha! and your development system (Jira, Rally, Azure DevOps, Asana, Github, Trello)
The Aha! development tool integrations allow Aha! users to fully customize how Aha! record fields and records themselves are mapped to your development system.
Click any of the following links to skip ahead:
How it works
Once you create an integration and define which Aha! records you wish to map to your development system, you will be able to see the available field mappings in your integration configuration.
Integrations support mapping the following Aha! records:
Initiatives
Releases / Schedules
Epics
Features / Activities
Requirements
After specifying how you wish Aha! records to be mapped, select the field mapping option to customize how the fields for that record are mapped between Aha! and your development system. For each record, we provide a default set of mappings based on what is most commonly used among Aha! customers. You can revise these mappings to fit the needs of your organization.
Tip: If you have configured required fields in your development system, we recommend setting the Required flag on those fields in the custom layout associated to your product. This will ensure that any required fields are populated when records are created on the Aha! record creation form.
Choose a mapping direction
For each field mapping, you can specify the mapped Aha! and development system fields. You can also specify the direction of the mapping by clicking the blue arrow icon. The directional options include:
One way: Allows the field to only be synced in one direction — either from Aha! or from the development system.
One way (set once): Allows the field to only be synced in one direction and for that sync to be a one-time event.
Two way: Allows full two-way communication between Aha! and the development system for the field.
Configure field mappings
When mapping certain fields, such as a record's Status, or custom fields such as the Predefined choice list or Predefined tags fields, a Configure option will appear at the right side of the row to allow value mapping for the field between Aha! and your development system.
After clicking Configure, a modal will open. You can automatically map matching values by clicking the Match like values button. You can then manually drag values into place to finalize preferred mappings and map them as one-to-one or one-to-many.
List of mappable fields
The following table provides a comprehensive list of standard Aha! fields that can be mapped within each record type.
Initiative | Release | Epic | Feature | Requirement | |
Aha! score | x | x | |||
Assigned to user | x | x | x | ||
Attachments | x | x | x | x | |
Comments* | x | x | x | x | |
Constant | x | x | x | x | x |
Created by user | x | x | x | x | |
Created timestamp | x | x | x | x | x |
Description | x | x | x | x | |
Due date | x | x | |||
End date | x | ||||
In parking lot? | x | ||||
Last updated timestamp | x | x | x | x | x |
Epic | x | ||||
Name | x | x | x | x | x |
Original estimate | x | x | x | ||
Position | x | x | x | x | |
x | x | x | x | ||
x | x | x | x | ||
Reference num | x | x | x | x | |
Release date | x | ||||
Release URL | x | ||||
Remaining estimate | x | x | x | ||
Start date | x | x | x | x | |
Status | x | x | x | x | x |
Tags | x | x | |||
Time frame | x | ||||
Type | x | x | |||
URL | x | x | x | x | |
Work done | x | x | x | ||
Work units | x | x | x |
*Comments:
When you first send an Aha! record to an integrated tool, Aha! does not send any existing comments. This is so that you can complete your strategic plans in Aha! before sending records to engineering.
Though you can edit comments in Aha!, edits to comments will not be sent to integrated tools.
**Record relationships:
For Jira 2.0 integrations only.
One-way directional fields
Nearly all standard Aha! fields support all of the directional options when setting up an integration. However, the following Aha! fields only support a one-way connection due to the nature of the data being communicated:
Constant
Remaining estimate
URL
Release URL
Created timestamp
Last updated timestamp
In parking lot?
Record relationship fields (e.g. the initiative or epic record relationships on a feature card)
Technically, the <record→ % complete field supports a two-way connection, but we strongly advise against it.
Note: If you find yourself setting up a mapping with limited directionality and it is not on this list of limited fields, the problem is generally due to an API limitation with the field you are trying to sync to in the development system.
Constant field
The Constant field is an Aha! field mapping option. This field allows you to specify a constant value that will be passed to your development system.
Custom fields
In addition to mapping default Aha! fields, you can also map Aha! custom fields to your integrated system. You can customize their mapping just like you would a default Aha! field.
Aha! supports the following custom field types for mapping to your development system:
|
|
When mapping the Predefined choice list or Predefined tags fields, a Configure option will appear at the right side of the row to allow value mapping for the field between Aha! and your development system.
After clicking Configure, a modal will open. You can automatically map matching values by clicking the Match like values button. You can then manually drag values into place to finalize preferred mappings and map them as one-to-one or one-to-many.
Troubleshoot field mapping
If you have trouble with your field mappings, often all it takes is a conversation. Please reach out to our Customer Success team at support@aha.io. They respond super fast.
