Integrations

What is the challenge? Rally Project name is updated but the project name is not updating in the Aha Integration Project Tab? What is the impact? Users see the wrong project name in the Aha integration and think they need to create a new integrati...

What is the challenge? I would like to integrate Aha! activity logs into my SIEM but cannot access the information from the Account > Activity table via the API. What is the impact? Unable to integrate with the corporate SIEM without th...

What is the challenge? We wanted to set up MCP access using the instructions here: https://www.aha.io/blog/introducing-the-aha-software-mcp-server What is the impact? The connection fails in Claude with an error message after the Aha authorizatio...

Currently we use Confluence PRD documents: https://confluence.atlassian.com/display/DOC/Product+Requirements+Blueprint It would be great if we could find some way to combine this with Aha. Otherwise, we spend time duplicating information from insi...

What is the challenge? Today, it appears that Epic records are not support with MCP server integration What is the impact? Unable to retrieve details of epics using AI tools Limits the usefulness of Aha + MCP integration Describe your idea...

The AHA window size in the visualforce pages is so small and users have to scroll to view the entire list of ideas related to an Account/Case/Opportunity. It would be great if we can customize the AHA layout in Salesforce(adjust the height of the ...

We use Aha for both Feature Requests and Defects and need to be able to designate if the JIRA issue type is an Epic, Story or Bug when linking to JIRA.

I would like to be able to integrate "Epics" from different "Projects" in Jira under common "Themes".

There are a few instances when it would be valuable to report on the name of the integration that an object is using to connect with an external development system. This would help to identify when integrations are being 'cut over' in order to tra...

Currently, when a feature or epic is created in Jira and pulled over to Aha! via the integration webhook, the created by user defaults to the Aha! user who is the webhook "run as" user. Even if there is mapping setup to map the Jira "Reporter" to ...