Integrations

In the default integration for Microsoft Teams and the Idea Portal, I would like to customize the automated post when a new idea is submitted to include custom fields (e.g. category).

We move customers from opportunity into lead generally before we can capture their ideas. They are then leads for their lifetime with our business. With the current Aha! Salesforce integration, we can't capture their ideas through Salesforce.

When a user moves to a new workflow in a workspace or team, there can be a loss of data related to the statuses like cycle time, time in status, etc. I would like to understand these consequences before making the change so I am not surprised with...

Sometimes I'd just like to fix a record or two that have gotten out of sync. When I click on the Integrations menu for a particular feature, I have the option to resend all fields to my development tool (Aha -> ADO), or, to delete the link. IDE...

This is the open source ticketing tool that Facebook released.

What is the challenge? Currently when we navigate to Integration updates to import any record which we need we need to manually navigate to multiple pages for accessing the required record to map with Aha! What is the impact? When the list of impo...

I would like an out of the box integration NetSuite CRM integration to push ideas into Aha. This would work similar to the integration with SalesForce.

The default behaviour of how the TFS/VSTS integration sends time Estimates in minutes is very limiting. I don't know any agile team that would be estimating Features or Requirements down to minutes, so it doesn't make sense for the integration to ...

What is the challenge? Currently we have cases where RnD would open a theme (we categorize it) , and that is for mostly themes with technical nature. as such PM will not initiate them, but we still want the PM to be aware of them in planning and p...

Key problem: the "Parent" field in ADO can contain only one value. In ADO, a feature is automatically associated to the same theme as its' parent epic, but in Aha! this is not the case. So when features import, we associate them with the correct p...