RELATED IDEAS
Improve mapping capabilities for "Idea category" custom field.
What is the challenge? |
You can add a custom field on epics, features, etc. for "Idea categories". When an idea is promoted, the idea's category will be copied to the epic or feature automatically. This can be mapped one-way from Aha! to Jira to a text field. However, if you try to map this to a multi-select type of field in Jira, you can't configure what categories in Aha! map to the field options in Jira, so updates to this field don't work. Also, updates from Jira to Aha! will not work. |
|---|---|
What is the impact? |
This necessitates the need for a separate custom field that is not tied to the idea category, so it can be mapped to Jira two-ways. |
Describe your idea |
Support the "idea categories" custom field with a two-way integration with multi-select fields in Jira. |
© 2026 Aha! Labs Inc.•All rights reserved
I have a similar problem with integration to Azure DevOps
We have a custom field 'Suggested Priority' with alpha numeric drop down options
When integrating to Azure we want it to map to the Priority field which is a numeric field, but this is not possible so I have had to add another custom field to convert the alpha numeric to numeric, just to accommodate the integration to Azure (and you cannot hide custom fields so it also clutters the fields in features)
A mapping option in Integration set up would allow us to map a Aha! fields drop down options, to corresponding options in Azure and remove the extra unnecessary custom field