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:
Shipped
Showing 987
6
VOTE
Ability to configure integrations not to create new records in Aha
In the 1.0 integrations I had configured it to not try to create new Aha! records when records were created in JIRA.
I would like to be able to do the same in the 2.0 integrations. Currently when someone creates a new issue in JIRA I see this appe...
0
Future consideration
5
VOTE
Enable Field Filters for when to Sync to Aha
I would like to be able to set a filter in my Integration for which Jira Issues to sync up. An example would be to not push stories into Aha until there is a point value or time estimate entered in Jira. Another would be to only push to Jira if it...
0
Future consideration
5
VOTE
Add a way to push all features from a master release to Jira at once
I am managing a few master releases right now with dates that are moving around, and it is currently time-consuming to send updated release dates of all sub-releases to Jira (and easy to miss one!). I’d also like the ability to reshape features, e...
2
Future consideration
1
VOTE
Add context with Slack integrations
What is the challenge? A Slack Messages used to add comments to aha records or create ideas, by default, does not have context around who sent the message, when, what slack channel What is the impact? Either the context around the message is lost,...
0
Future consideration
3
VOTE
7
VOTE
4
VOTE
Add filters to integrations to prevent sending records that meet criteria
It would be useful to be able to create filters to prevent certain records from being sent to Azure, JIRA, or other integrations. For many workflows, there may be "raw" working records in a release backlog that are not ready to go to engineering t...
2
Future consideration
2
VOTE
Allow link of a requirement to a release (sprint)
We have features that are mapped to a specific sprint, but within that feature, we have requirements (user stories) that could be mapped to two different sprints. The assumption with Aha! is that a feature would be completed in one sprint, which i...
1
Future consideration
3
VOTE
Synchronize Organization with Azure DevOps
We are storing a client name on user stories and bugs in ADO and it would be great to be able to be able to sync this field between ADO and Aha! using the organization field that has now been made available to all Aha! objects (and not only ideas)...
0
Future consideration
6
VOTE
Integrations 2.0: JIRA Default map Aha! URL to JIRA Aha! Reference field
1.0 did this; 2.0 does not.
As a user I have to manually add the mapping between the URL field for an Aha! record and the Aha! Reference field for the JIRA record.
For Releases we automatically map the URL to the description field.
For Features/...
0
Will not implement
© 2025 Aha! Labs Inc.•All rights reserved