RELATED IDEAS
Support for "Select list (cascading)" field type in JIRA
JIRA has a custom field type that supports cascading. This is a very useful field type that is currently not supported in Aha. Due to this, we cannot make the field required in JIRA and thus compliance drops off. The JIRA API supports this field so it is just a matter of building support on the Aha side.
-
ADMIN RESPONSEMar 17, 2023
You can now map predefined choice or predefined tags fields in Aha! to select list (cascading) fields in Jira.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +1
Any planned implementation timing for this?
For us is common to use a dropdown type field in Jira side,
Is frustrating that not of all field types are available to be mapped (at least as read only from Jira to Aha)
since we need to produce dashboards for tracking using the variety of field types
-including both custom and system fields-
also see https://big.ideas.aha.io/ideas/A-I-11236
Is there any update on this?
We would find this feature very helpful as well. Over 150 teams use 'select list (cascading)' in Jira to help categorize and drive prioritization decisions.
This would be really helpful, and would increase the usage of Aha at our company.
This feature is very highly desired by our group, because it limits the amount of integrating we can do at the feature level. Our company uses cascading dropdowns in JIRA for important categories like Investment area (for engineering allocations and delivery teams). Not being able to map to these fields in JIRA highly constrains the value of the Aha integration and the associated Aha reporting capabilities.
Yes I would love to have this feature.
We need this kind of integration in order to match the fields that we have in JIRA with different select list option (domains, initiative links). It will be a wonderful initative to have this implemented.
We could definitely use this feature as well!
Is there any update on when this is going to be implemented ?