Integrations
Sort by:
Trending
Status:
Future consideration
Showing 607
1
VOTE
2
VOTE
Integrate with 3rd party digital marketing tools API
Importing campaign data from the many different marketing tools we digital marketers use every day can be time-consuming and a little frustrating. In order to monitor meaningful digital ad campaign results that do not show up in Google analytics (...
0
Future consideration
1
VOTE
Improve the Salesforce Ideas UI - Selecting a product
The current UI for selecting a product when raising a new idea in Salesforce doesn't look great and isn't particularly inviting for new users to interact with. Perhaps something more central with our portal logo above. Even better - make this some...
0
Future consideration
1
VOTE
Allow Jira Epics to be Linked to Multiple Aha! Epics
My organization uses Jira to track development work. We create Roadmaps for leadership to track progress. Jira Epics and linked to the Aha! Epics on said Roadmaps. Occasionally we will have one Jira Epic that will relate to multiple Aha! Epics in ...
0
Future consideration
2
VOTE
View Feature List Filter by Integration
It would be useful to be able to use the "Integration" as a filter option for feature views.
For example, I coordinate a project across three different teams, each with their own integrated project outside Aha! This would help me to separate their...
2
Future consideration
1
VOTE
2
VOTE
Exclude users for activity webhook
To help with creating integrations between systems.
The specific case would be an automated system that keeps aha synchronized with an external system. The system needs to log in as an user to make updates, but the system does not need to see webh...
0
Future consideration
2
VOTE
Add Ability to not send a specific release to Rally on Master Feature or Feature
Rally has a concept of Backlog where the Release is set as 'Unscheduled'. But there is no way in Aha! to assign a Master Feature or Feature to something like 'Unscheduled' so that the Release information does not get populated in Rally. We want to...
0
Future consideration
2
VOTE
Add Product Prefix field as a choice in the JIRA integration
We integrate Aha! with multiple JIRA projects and often use the product prefix as the Component to identify the source of the ticket. Today we use a constant and add that manually. Adding it from the prefix would save us a lot of time!
0
Future consideration
2
VOTE
Allow for "approve incoming changes" in Jira integration
There is currently an option to approve outgoing changes or incoming records, but not incoming changes.
The current options are:
- Allow any Jira user to directly impact sensitive Aha roadmap information by changing Jira tickets (we map Epics to F...
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved