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
Filter by:
Status
Showing 985 of 9565
7
VOTE
2
VOTE
Moving integrated Jira records to a new project should update the Jira link and key in Aha!
What is the challenge? When following the guidance in this help article to move Jira records between Jira projects with Jira, https://support.aha.io/aha-roadmaps/integrations/integration-guides/move-records-with-jira-or-rally~7444656710918981281#p...
0
Future consideration
6
VOTE
Easily share relevant research documents on features through integration
What is the challenge? With the Research tab, many teams are creating documents to contain their research, technical requirements, and wireframes. But once I send a feature into Jira, I cannot pass along the relevant documents I want my engineerin...
0
Future consideration
4
VOTE
Activity webhook triggered by a specific custom field
What is the challenge? Our custom integration between Salesforce and AHA is not being triggered. What is the impact? Custom field is not updated in SF when it is the only field updated on an idea. Describe your idea Allow activity webhook configur...
3
Future consideration
16
VOTE
Allow record mapping to Asana Projects
Asana best practices recommend projects represent distinct bodies of work with start and end dates. The Aha! integration requires, in the set up, selection of an Asana Project to connect the workspace to. This requires a new integration for every ...
0
Future consideration
15
VOTE
Jira integration user name
In both Jira and Aha!, you need to have a user that has the appropriate permissions which is often a highly privileged user. However, when setting up the integration, there is no way to indicate an alias name to use for the integration. Consequent...
0
Future consideration
19
VOTE
Ability to create a report of integration errors across multiple workspaces
Currently the only way to look at the integration errors across multiple workspaces is to bring up the Integration Updates dialog and use the Send outgoing changes tab. But you can't filter on error text, or expand the window to see the everything...
6
Likely to implement
3
VOTE
Allow use of Mapped fields template with one field difference for each integration
What is the challenge? Can't use Mapping Integration template. Have to update multiple integration for every mapping change since one has to be different. What is the impact? Would save a ton of time for our team. Describe your idea We have around...
0
Future consideration
29
VOTE
Keep features in sync when they cross areas in Azure DevOps
This is useful when you have your DevOps areas configured by team. Once the features are pushed from Aha! to DevOps and evaluated by the team they need to be moved into the area for the appropriate team. Any team can work on any feature based on a...
0
Future consideration
7
VOTE
Scheduled Recurring Sync for Integration
Who would benefit? Aha administrators, anyone responsible for maintaining integrations/records between systems What impact would it make? Reduce potential issues with integration records not always synching as expected, resulting in inaccurate or ...
2
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved