Integrations
Sort by:
Trending
Status:
Future consideration
Showing 646
4
VOTE
Display Dashboards / Webpages in Tableau
For security reasons, we cannot have Aha! set to "allow anyone to access." Still, we need the ability to provide a seamless experience for our Executives and users to derive value from the Aha! data. We want to be able to display these in Tableau ...
2
Future consideration
1
VOTE
Sync the change of parent link made in Aha! across 2 Azure DevOps integrations
Who would benefit? Customers with multiple integrations set up to ADO who are wanting to move features to different Epics as their plans change. What impact would it make? How should it work? The parent/child relationship should be tracked across ...
0
Future consideration
9
VOTE
Support parent-child moving across workspaces and Jira projects
In the Aha! we have Features that reference a parent Epic in another workspace. In Jira we have issues that are children of an Epic in another project. This cross workspace/project relationship is supported in Aha! and Jira, but the integration do...
4
Future consideration
1
VOTE
Defect: Jira Integration record mapping doesn't use custom terminology
Who would benefit? Anyone with custom names for "Epic" or "Feature" who is setting up a Jira integration. What impact would it make? Prevent failure of the integration (which took us several hours to figure out). This was particularly egregious fo...
0
Future consideration
1
VOTE
Allow project access token to be used instead of personal token for GitLab integration
Who would benefit? anyone using the integration with aha and GitLab What impact would it make? improves resiliency and stability of the integration How should it work? Currently, to set up the GitLab integration a user in GitLab must use a persona...
0
Future consideration
1
VOTE
Iteration to Release not Retaining Parent Relationship with other Records (AzDo Integration)
Who would benefit? Aha users What impact would it make? Elimination of lost records (Azdo integration) How should it work? When using iteration to release, the integration would look at the area path of that record as well as the iteration path. S...
0
Future consideration
18
VOTE
Map JIRA Fix Version to Aha Release Phase
We would like to be able to map a JIRA fix version (and its dates) to an Aha Release phase
Why? We like to plan in Aha using a monthly program increment primarily with features, similar to SAFe. But as a continuous delivery shop using Kanban key ...
8
Future consideration
5
VOTE
Map Created By User from Jira
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 ...
1
Future consideration
30
VOTE
Zendesk integration has reportable idea status
We are trying to close the feedback loop for our customers. As product ideas come in through ZenDesk, they are kicked to Aha! and then the product team updates each ticket with a status. That status, while reflected in the ZenDesk issue detail, do...
2
Future consideration
5
VOTE
Project level automation with Jira
Requesting a change to Aha! Jira integration to allow for project level automation. Project level webhooks send payloads differently than system level payloads. If support for project level webhook payloads were added, we could enable multitudes o...
0
Future consideration