Integrations
Sort by:
Trending
Status:
Future consideration
Showing 945
4
VOTE
Integrations 2.0 Import candidates notification should appear regardless of the selected product
As a product owner managing multiple products in Aha!, it is time consuming to have to switch between each product I manage in order to see if there are new import candidates. The notification should appear for me when there are import candidates ...
0
Future consideration
3
VOTE
Ability to enforce mandatory fields on Starter Roadmap, User Story Map, Strategy Roadmap, and Gannt
We have mandatory fields when creating initiatives, master features and features. These can be avoided when creating records via the Starter Roadmap, User Story Map, Strategy roadmap and Gantt views (there are probably some others I'm missing here...
0
Future consideration
3
VOTE
5
VOTE
Provide the ability to ingest issues created directly in a linked Github repository
I am currently utilizing Aha! and have it linked to several of our team's Github repos. The functionality to create issues in Aha and send to to Github works great. However we often have cases where issues get created in repos directly. When those...
0
Unlikely to implement
1
VOTE
Provide applicable error message when a Jira integration can't authenticate due to a captcha challenge issue
When attempting to set up a Jira integration, authentication can fail with a 403: CAPTCHA_CHALLENGE error we can see in the logs, but there is no applicable message on the integration-set up screen. It just says "We could not connect to your Jira ...
0
Future consideration
4
VOTE
JIRA Integration - allow bidirectional mapping of the "time frame" field
for those who map epics to initiatives, and like to keep their platforms bidirectionally synced as much as possible, it's possible to have a custom "time frame" field in JIRA set up to match that in Aha, yet it's not possible at the moment to bidi...
1
Future consideration
2
VOTE
Ability to map Jira Web Links with Aha! URL at Integration
Why is it useful? Web links at Jira are used to show all the links associated to an issue/record. Who would benefits from it? Its easy for all users to view Aha! link at Jira epic or story rather than having it at a custom field. How should it wor...
0
Future consideration
2
VOTE
JIRA integration to track correct users in history of issues
Today the Aha JIRA integration will leverage the user account setup in the integration settings as the actor for all integration sends between the systems. This creates a lot of confusion for who actually made changes in one system or the other. F...
1
Future consideration
4
VOTE
Provide Rally User name in Notification Updates
When a change is made in Rally, the Notification message always states that the user whose account is used for the integration to Rally is the one that made the change. This is not useful. Therefore I request that the name of the user in Rally who...
1
Future consideration
1
VOTE
Integrated icon or color on release column of board views to show integration linked
My users are expected to help keep their roadmap releases integrated to the tools of the engineering team (jira or Azure Devops). They need to link the release to the jira release or ADO iteration path, to keep roadmaps and scope alligned in both ...
0
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved