Integration field mapping (integrations 2.0)

The Aha! development tool integrations allow Aha! users to fully customize how Aha! records, and fields within those records, are mapped to the development system.

How it works

The field mappings are available in your integration configuration after you define which Aha! records you wish to map to your development system.

Integrations support mapping the following Aha! records:

  • Initiatives
  • Releases
  • Master features
  • Features
  • Requirements

After specifying how you wish Aha! records to be mapped, you can 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.

JIRA-configure-feature-mapping.png

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.

The following table provides a comprehensive list of standard Aha! fields which can be mapped within each record type.

  Initiative Release Master Feature Feature Requirement
Constant x x x x x
Aha! Score     x x  
Assigned to User     x x x
Attachments x   x x x
Comments 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  
Last Updated Timestamp x x x x x
Name x x x x x
Original Estimate     x x x
Position     x x x
Reference Num   x x x x
Remaining Estimate     x x x
Resource     x x  
Start Date x x x x  
Status x x x x x
Tags     x x x
Type     x x  
URL x   x x x
Work Done     x x x
Work Units     x x x
End Date x        
Timeframe x        
In Parking Lot?   x      
Release Date   x      
Release URL   x      

Nearly all standard Aha! fields support all of the directional options when settings 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?

For fields not mentioned above, if you find yourself setting up a mapping that is limited in the directionality, it 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 the specification of a constant value that will be passed to your development system.

Custom fields

In addition to customizing the mapping of default Aha! fields, you can also map Aha! custom fields to your integrated system.

The custom fields supported for integration include:

  • Text field
  • Note
  • Number field
  • Date field
  • URL/Email field
  • Predefined choice list
  • Editable choice list
  • Predefined tags field
  • Tags field
  • User field
Was this article helpful?
1 out of 2 found this helpful
Have more questions? Submit a request

Roadmap software to manage your products.
Finally, connect strategy to execution.

Powered by Zendesk