Integrations

Would like to see some way of setting user(s) to be notified if there is an interruption in communication between integrated system.

Aha! needs the ability to support changing a Jira project key. Occasionally teams change their focus and the Jira project name and key need to be changed to reflect that so Aha! needs to be able to support that as well.

With Jira, a single Aha! webhook added at the system level supports updates across all Aha! integrations. This makes scaling integrations simple as after the first setup, a user never has to add another webhook. With Azure DevOps (TFS), each i...

We use custom objects in our Salesforce org to track things like feature requests, bugs and other system support related issues. Allowing us to integrate Aha to a custom object would allow us to use the Aha integration with our existing org struct...

What is the challenge? aha-github assignees integration do not work What is the impact? cannot make use of the assignees sync in the integration Describe your idea In the Aha! Github integration the assignees are not getting synced. In Github we h...

What is the challenge? We have approx 110 workspaces. Previously, I was able to renew the personal access token so that I didn't have to create a new one and update all 110 workspaces. There has been a change and now I must create a new one ever...

Asana best practices recommend projects represent distinct bodies of work with start and end dates. The Aha! integration requires, in the set up, selection of an Asana Project to connect the workspace to. This requires a new integration for every ...

Clubhouse is gaining a full head of steam and being adopted widely as a replacement for Trello and Jira - it strikes a great balance between the two. We're currently evaluating a move from PivotalTracker to Clubhouse, and while we're excited by th...

In both Jira and Aha!, you need to have a user that has the appropriate permissions which is often a highly privileged user. However, when setting up the integration, there is no way to indicate an alias name to use for the integration. Consequent...

While I recognise that moving JIRA issues between projects breaks the AHA integration links, the workarounds proposed here are not helpful. Option 1 ("Relink each record manually") is the only viable workaround, with options 2 and 3 being too haza...