My ideas: Integrations

What is the challenge? With many Ideas, my sales teams needs a way to sort, filter or export the long list of Ideas displayed in the SFDC widget What is the impact? Eliminates requirement to click on each Idea to understand when it might h...

What is the challenge? The Salesforce widget is using a Salesforce component that has a hard limit of 1000 rows. When the limit is exceeded it generates an error like "Collection size 1,020 exceeds maximum size of 1,000" What is the impact? ...

What is the challenge? Aha! currently supports Duo for two-factor authentication (2FA). However, many organizations standardize on other MFA providers such as Microsoft Authenticator, Okta Verify, or Google Authenticator. Relying solely on Duo c...

What is the challenge? When viewing feedback in Salesforce, tables don’t render very user-friendly. It would be helpful to have a link to the portal view of the item for quicker review. What is the impact? The Salesforce plugin renders tab...

What is the challenge? The current salesforce plugin does not support rich text fields well. What is the impact? This makes for a poor and confusing viewing experience for those trying to submit proxy votes. Describe your idea Better...

We are currently using Aha! Roadmaps and asking for consideration of implementing OAuth authentication when setting up the integration to Azure DevOps Services. With Microsoft making the push towards strengthening their customers security posture,...

What is the challenge? We are using aha for the whole product lifecycle from discovery to delivery. However post delivery isn't tracked on aha for that 360 view of feature impact and progress towards goals and initiatives What is the impact?...

What is the challenge? Aha! webhooks can currently be triggered only by changes to a set of standard fields (name, description, status, assigned user, dates, etc.). Many teams rely heavily on tags, record links but changes to these fields cannot...

What is the challenge? The release field is available in the Jira integration under the Aha! feature/epic record. It works as expected when initially sending the Aha! feature to Jira. (Note: this is not the use case of mapping the release as a s...

What is the challenge? Our organization has transitioned recently and so we got new domain for employees, currently both the domains are valid for employees. In few application like Aha! we have old domain itself, but in the new applications we ...