What is the challenge? When updates to the Salesforce <->Aha! integrations are available, the users who can make the changes should be notified of the availability of the upgrades. Right now the notification is displayed on the announcemen...

When creating new issues in GitHub, an "issue template" can be applied. It's not possible today to specify an issue template when sending an Aha! record to be created as a new issue in GitHub. This is problematic if we also need to send the record...

What is the challenge? Today, the Jira integration supports movement of integrated records across Jira projects via use of an integration template. However, if the integration includes sprint mapping, a board must be selected in the template. Th...

What is the challenge? We have Aha! and Jira in the mix. teams use Jira smart checklists and Aha ! to dos. It will be beneficial to have bidirectional sync between the two. What is the impact? Teams have to manually sync and maintain Aha! ...

What is the challenge? Currently, with integrations like Github, multiple record types are all mapped to Issues, which are of the same underlying type. The integration updates queue appears to just map the first record type that is mapped to an ...

What is the challenge? Currently unable to sort or filter on the list of ideas tied to a customer account in the salesforce widget. The current way ideas appear to be sorted is by name of idea. (at least it is post bulk import) What is the i...

What is the challenge? Very often records fail to be imported due to record status not matching the default Aha values What is the impact? Describe your idea When importing records Aha currently defaults to [System.State] in ('Active...

What is the challenge? Today Aha only allows to send the Release field from Aha to Jira, while we have technical teams that use only Jira (developers) and update the release there, while it can't sync back to Aha. What is the impact? Incon...

What is the challenge? Integration is setup to azure DevOps. When a child feature results in an auto. update in parent Epic, and the feature and Epic are in different azure DevOps integrated projects, a second Epic is created in the integrated a...

What is the challenge? Each time I review Integration Updates I have to manually select the Workspaces, Integrations, and Record Types in varying levels to see the items needing to be addressed. Once I close out, and go back in later, I have to ...