Integrations
Sort by:
Trending
Status:
Future consideration
Showing 619
1
VOTE
Ability to easily update Personal Access Tokens in Integrations
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...
0
Future consideration
2
VOTE
Trigger activity webhook event when a 1:Many custom table value is added or edited
What is the challenge?
An activity webhook is not triggered when a change to a 1:Many custom table is made.
What is the impact?
External systems that rely on the activity webhook do not receive updates when 1:Many custom table records are ...
0
Future consideration
2
VOTE
Activity webhook configuration should account for nested workspace hierarchy
What is the challenge?
I have a workspace hierarchy like so:
Company line
workspace
workspace
Test line
test workspace
test workspace
I would like to build an activity webhook in the Company line and send data to a third party ...
0
Future consideration
67
VOTE
Add Rally "Project" field to integration reports
What is the challenge? What Project Name is an integration connecting to for Rally Integrations What is the impact? Cannot create a list report showing what Project Name is an integration connecting to in Rally Describe your idea Add the 'Project'...
3
Future consideration
4
VOTE
Create Standard Integration to Send Ideas from One Aha! Workspace/Account to Another
What is the challenge?
Different Aha! Workspace in other Aha! Accounts cannot communicate except through a manual import of data or API.
What is the impact?
At larger companies, it is not always feasible to use one Aha! account. We current...
0
Future consideration
4
VOTE
Include history of comments when importing from ADO integration
What is the challenge?
Currently, when importing ADO records via an ADO integration only the latest comment is imported from ADO
What is the impact?
Inability to see comment history can lose critical context and require Aha! users to go to...
0
Future consideration
9
VOTE
Fix date syncing between Aha! and ADO
What is the challenge? Dates added on AHA/ADO are not properly synced and show up on the other tool as +/- 1 day as a result of time differences between the two tools. Expected behaviour: When selecting a date in one tool, the same date appears in...
2
Future consideration
12
VOTE
Improve syncing fixed workflows with integrations
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...
2
Future consideration
3
VOTE
When linking an Aha! record to an existing Jira record, perform a full sync of all fields
What is the challenge?
When "Use Jira and overwrite Aha!" is selected, there is a full sync of all fields, allowing fields to update in Jira. But, when "Use Aha! and overwrite Jira" is selected, that same full sync is not performed, and one-way ...
0
Future consideration
7
VOTE
Support ADO deployment controls syncing to Aha!
What is the challenge? ADO has released the ability to visualize deployment controls within an ADO record. In order to share this information with product management, this information needs to be able to sync back to Aha! via the ADO integration. ...
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved