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? Giving users the ability to View integration settings or Edit integration Mapping without having ability to Setup/Create new integrations What is the impact? What we have today is users get ALL or Nothing. Admins onl...

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? We have a shared template across all of our Jira integrations to manage the configuration globally. However, using a global template forces us to have the same integration username (mine, the Aha!/Jira admin) across all pr...

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...