The Aha! Roadmaps development tool integrations allow Aha! Roadmaps users to fully customize how Aha! Roadmaps record fields and records themselves are mapped to your development system.
Note: A field in Aha! Ideas is not able to create a record in an integrated tool (or vice-versa).
Click any of the following links to skip ahead:
How it works
Once you create an integration and define which type of Jira issues you wish to map ideas to, you will be able to see the available field mappings in your integration configuration.
After specifying how you want ideas to be mapped, select the field mapping option to customize how the fields for that record are mapped between Aha! Ideas and your development system. For each record, we provide a default set of mappings based on what is most commonly used among Aha! Ideas customers. You can revise these mappings to fit the needs of your organization.
If you have configured required fields in your development system, we recommend setting the Required flag on those fields in the custom idea layout associated with your Aha! Ideas workspace.
Choose a mapping direction
For each field mapping, you can specify the mapped Aha! Ideas 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! Ideas 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! Ideas and the development system for the field.
One way mapping direction is not the only way to ensure a one-way field sync, however. When you edit a custom layout, you can also mark any field as read-only. Read-only fields block anyone from updating the field through a record's drawer or details view, so that users in your Aha! account have the proper context but cannot accidentally adjust fields that need to stay static.
Read-only fields are not locked fields, however. They can still be updated through integrations, and this is often key to their true value.
Read-only fields can also be updated through the Aha! API and through bulk edits in list reports.
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! Ideas 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.
Mappable fields
Most fields on ideas are generally mappable, including custom fields. Some of the standard fields you may want to map include:
Comments (internal comments only)
Created at
Name
Reference number
Updated at
Workflow status
One-way directional fields
Nearly all standard Aha! Ideas fields support all of the directional options when setting up an integration. However, the following Aha! Ideas fields only support a one-way connection due to the nature of the data being communicated:
Constant
Created timestamp
Last updated timestamp
Record relationship fields (e.g. related ideas)
URL
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! Ideas field mapping option. Use this field to specify a constant value that will be passed to your development system.
You cannot map a Constant field to a multi-select field in Aha! Ideas (like a predefined choice list).
Assignee field
You can map the assignee field (also called Assigned to user) and by default the mapping is bidirectional. Mapping this field gives everyone insight into the person responsible for a particular record, regardless of the tool they use.
However, there are a few nuances to assignee field mapping that are worth noting:
A user's email address must match in each tool if you want to assign a record to the same person.
The Aha! Ideas integration (or the user the integration is running as) must have appropriate user permissions in the integrated tool to see users' email addresses.
If neither of these situations exist, then Aha! Ideas will not be able to assign a record to a user in both tools. And then in that case:
If Aha! Ideas has a Default user configured, then the record will show an assignee in Aha! Ideas but not in the integrated tool.
If you choose to Resend all fields in Aha! Ideas, the assignee will be removed from the record in the integrated tool.
Custom fields
In addition to mapping default Aha! Ideas fields, you can also map custom fields to your integrated system. You can customize their mapping just like you would a default Aha! Ideas field.
Aha! Ideas 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! Ideas 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.