Pinned ideas
PINNED
Chrome extension to capture feedback from anywhere
What is the challenge? We work in many applications and Aha! can not build custom integrations for all of them. This makes it very hard to users of those applications to capture feedback and store it all in Aha! ideas. What is the impact? This res...
Integrations
Sort by:
Trending
Status:
Showing 983
42
VOTE
Rally Project name change should be reflecting in the Aha! Integration
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...
1
Already exists
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
10
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
3
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
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
12
VOTE
Sending child records to one ADO project should not error out if parent record is integrated to a different Workspace and ADO project
What is the challenge? Users are now able to support linking work between multiple Aha! workspaces and multiple ADO projects with parent/child relationships spanning this; however one scenario is producing an error. When a parent record is integra...
1
Likely to implement
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
205
VOTE
Dedicated Integration User
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 ...
16
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
17
VOTE
Ability to sync Jira's "Team" bidirectionally
What is the challenge? Out-of-the-box Jira field values cannot be synced, causing the inability to bidirectionally sync that field between Aha and Jira. What is the impact? Aha is meant to be the singular solution for Product teams to set their st...
0
Likely to implement
© 2025 Aha! Labs Inc.•All rights reserved