Aha's public API is key for us to manage our backlog of ideas and interconnect Aha with other systems. Therefore, having the ability to merge ideas in an automated manner (API) would allow us to drive more efficiencies when managing ideas on our p...
Guest
almost 6 years ago
in Integrations
0
Shipped
I frequently want to sort incoming ideas based on the value or account owner that was recorded in Salesforce. The Salesforce integration lets me make an idea list and display those pieces of data in their own columns, but there is not a way to fil...
As Aha! is positioned with more detail as an ability to fully deliver a customer experience, it would be great to expand our feature planning capability and embed wireframe capability within, with https://balsamiq.com/products/mockups/plugins/ or ...
Donna Sawyer
over 7 years ago
in Integrations
1
Shipped
We would like to have the ability to create a template for Aha to VSTS Integration that can be shared with all products. This template would include the mapping requirements outlined, and allow that to be shared as a standard for all products. Ide...
Provide an API end point for "Updates records" function inside the Integration
We use the "Update records" button in Aha! to bring the latest data from Jira into Aha! As we have already got the records linked between Aha! and Jira and we are not looking for using a webhook. https://www.aha.io/support/roadmaps/integrations/2....
Add missing Rally built in fields "Actual End Date", "Actual Start Date", "Investment Category", "Investments" in Aha! under Integration field mapping
The following fields are available in Rally but are not available in Aha to do field mapping under Aha to Rally Integration. Please add these fields so that teams can map them. Rally Built in field names that are not available in Aha! for mapping ...
Uma Prabhala
almost 4 years ago
in Features / Rally
0
Shipped
Improve warning for integrations "Update Records" action
For a development tool integration (i.e. Jira), there's an "Update Records" button. When clicked, you get this attached warning. This doesn't warn you that Aha! will send data for any one-way mapped fields (Aha! --> Jira) as well. It would be h...
When a feature is linked to an existing epic in Jira, sync the child stories to Aha! as requirements
We map Aha! features to epics in Jira, with Aha! requirements as stories. When an epic already exist in Jira with child stories, I want to link that epic to a feature in Aha! and have the child stories immediately sync over as requirements.