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 978
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
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
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
200
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
17
VOTE
The ability to review previously ignored integration candidates and undo the ignore
What is the challenge? Once you ignore an integration candidate, it is ignored forever unless you manually import or link the ignored record. If someone ignores a record by mistake there is no recourse to review those potential errors and correct ...
4
Future consideration
26
VOTE
Azure DevOps Integration - Sync dependencies at UserStories/Requirements level
What is the challenge? Currently, Aha integration with ADO syncs dependencies at Features level only. We need to also be able to sync the dependencies at Requirements/UserStories level.Including dependencies between Features and User Stories. What...
0
Future consideration
30
VOTE
Microsoft Teams Copilot Integration
Who would benefit? Product Managers What impact would it make? PdMs would benefit to have line-of-sight for updates that could impact them and their system of responsibility (“Copilot, tell me when the networking team will be upgrading their exter...
6
Future consideration
15
VOTE
Add support for GitHub Issue Types
What is the challenge? GitHub is introducing support for Issue Types In beta/preview mode currently https://docs.github.com/en/issues/tracking-your-work-with-issues/configuring-issues/managing-issue-types-in-an-organization https://github.blog/cha...
1
Future consideration
16
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
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
© 2025 Aha! Labs Inc.•All rights reserved