Currently we can rename the title of the Salesforce widget. We can also customize all the text within the Ideas portal in Aha. For us, we want to use this connection but we don't want to call them ideas, but rather e.g. Requirements. This is possi...

We are working integrations with some other systems, and the way part of it needs to be handled is via CSV file (Master Feature) - but Goal and Aha Score is not available for this import. This would be very helpful for our integration.

What is the challenge? We would like to have the ability to refresh the Aha record based on Jira updates. Currently, inside the integrated Aha ticket, users can only resend the updates they made in Aha into Jira, but not the other way around. We w...

What is the challenge? Currently, Aha AI agents are not permitted to run Jira integrations, or import available records on those integrations. What is the impact? This is one of our main current use cases for an AI agent, as we have hundre...

We anticipate having 150+ integrations based on a template (with the Rally integration). In order to add fields to the integrations, we edit the template and those updates/new fields flow to the individual integrations based on the template, howev...

It makes no sense that this isn't available today. All other idea submissions generate such notifications on status changes. This at least should be an option I can turn on when setting up the integration.

Who would benefit? Users of both Aha and those who are not direct users of Aha on a daily basis but who relay on outputs from the platform. What impact would it have? It would simply data sharing and through Microsoft products such as Teams, Word,...

Right now we leverage personas to describe who a release is targeting, where we'd love to be able to push the text value into our JIRA mapping

What is the challenge? If a KB visitor reviews the documentation and is not able to find the answers they need, we want to provide them two options for getting further help: Submit a Salesforce case directly from the Knowledge Base Open up a chat ...

Currently we cannot push work back from Azure to Aha correctly as the releases/Iterations do not sync which causes manual work to move a card to the correct Aha release once imported. Iterations can be nested in ADO, and when you try to send recor...