JIRA Component or custom field mapping (One-way)
Aha! enables you to map custom fields from Aha! to Components and other fields in JIRA. In both cases the integration is one-way from Aha! to JIRA. This means that changes in JIRA will not be reflected back to Aha!
Mapping to JIRA Components: Since JIRA restricts the values that these fields can take, you must ensure all of the following conditions are met:
- Configure the custom field in Aha! to only allow values that are valid for your JIRA configuration.
- The field can be named anything, but its type must be "Predefined tags field".
- The tag values must exactly correspond to the possible Component values that are configured in JIRA.
- For each feature or requirement you want to send to JIRA, make sure at least one component is chosen. If you do not choose a component that is required in JIRA you may receive an error: Remote error for ‘create_feature’: Data not accepted: components: Component/s is required.
Mapping non-Component custom fields to JIRA
The process for mapping custom Aha! fields to default or custom fields in JIRA is the same as above except you may use the other custom fields (not only "predefined tags field"). Also, linking Aha! custom fields to JIRA custom fields does provide a 2-way sync. Ensure that the values in each field match those that are in JIRA. For example, if you may only select one value in JIRA, you will set up a custom field as Pre-defined choice list type.
Steps to set up mapping of fields in Aha! to JIRA fields
- Set up the custom fields in Aha!
- Go to your integration configuration page in Aha! and click "Load project data" to trigger a refresh of available JIRA fields to which you can map.
- Add a field mapping between the custom field you created and the Component field in JIRA.
- Test by sending a feature with the custom field values selected to JIRA (via the Actions menu).
Note (JIRA Sprints): It is common to attempt to map a custom field in Aha! to the JIRA Agile sprint field. However, the sprint field is key to the operation of JIRA Agile. Changing the sprint affects a number of things. The JIRA UI is able to display the sprint in a friendly way, but the API does not support translating the internal representation into a form that is useful to external systems. Unfortunately, this means that Aha! (and other external systems) cannot integrate.