The Aha <->Jira Integration Mappings should be Transparent to User
Presently, the record level mappings between Aha and Jira are opaque to the user. This makes it quite difficult for the user to debug the syncing.Without this info, it is quite challenging to get the Integration working. If the integration does no...
Annoying maintenance task of updating expired webhooks that keep making systems out of sync and we end up using VSTS as the source of truth rather than Aha!
Allowing integration configuration to use queries to limit dataset integrated.
We have a shared devops environment that is managed by others and possibly not configured in the optimal way - especially when we try to integrate. Ideally, the same queries we use to "import" data (that we can modify) could persist to limit the d...
We have a need to migrate our ADO Wishlist Items to Ideas in Aha, for initial setup. We also have a need to migrate our ADO FEATURES to IDEAS in Aha. We do have an integration setup, but it only maps ADO Features to Aha Features. We cannot map Wis...
Better inform users in situations with records linked inside disabled integrations
It is currently possible to link an Aha! record to an existing record in the development system. However, it is not possible to link to an existing Aha! record that is already linked with another record in the integrated system. It would be helpfu...
Chris Zempel
almost 4 years ago
in Integrations
0
Future consideration
Allow for mapping Aha! approvals to Jira via the integration. When a team member moves an item in Jira to a status that requires an approval in Aha!, pass the approval status back to Jira once it is updated in Aha!
Guest
almost 4 years ago
in Jira
2
Future consideration
The use case for this is we have 7 different fields for grouping development teams containing over 50 total teams in Jira. We would like to be able to combine these into a single field in Aha for the purpose of running reports to show which of the...
Jerimiah Rudden
almost 4 years ago
in Jira
0
Future consideration