It would be great to have a dedicated integration user instead of having to use a user license for this purpose. I would love to keep my user and the updates from integrations (Jira, TFS,...etc) separate so that it is clear who made the update in ...

Our Sales and Support teams use HubSpot CRM for all of their daily operations. I would love to have the same two-way sync that is provided for Salesforce within HubSpot. Essentially, the ability to associate contacts to ideas within HubSpot

What is the challenge? When importing features from ADO the parent epic is automatically brought into Aha! Epics can live in separate projects and the team does not always want them to display within Aha! What is the impact? Difficulty in ...

What is the challenge? If an ADO user has done things like add new projects, or add new area paths to their projects, the only way to see these in the selection dropdowns for the integration wizard is to go back and re-submit the previous step. ...

What is the challenge? Today, the Salesforce–Aha! integration automatically excludes Ideas in a shipped status from search results by default. This creates confusion because those same Ideas can still be found if a user manually selects the ship...

What is the challenge? Currently, Aha integration with ADO syncs dependencies at Features level only. We need to also be able to sync the dependencies at Requirements/UserStories level.Including dependencies between Features and User Stories. What...

What is the challenge? Bi-directional sync of the Jira team field is only supported for some Aha! custom fields What is the impact? Mapping to a predefined choice list is not ideal because it requires us to manually update and map each tea...

What is the challenge? When statuses are mapped as bi-directional in integrations (Jira etc.) - transitioning rapidly between statuses in a fixed workflow in Aha! does not send each transition to the dev tool. With a fixed workflow in the dev tool...

Would be great if there was in integration into Monday.com. We have users in our organization that use this tool for managing their UI concepts and workload.

What is the challenge? Currently, Aha! does not support expandable macros (e.g., collapsible sections) coming from Jira Description. What is the impact? This leads to significant data loss — important contextual information, formatting, or...