Integrations
Sort by:
Trending
Status:
Showing 923
3
VOTE
2
VOTE
Allow integration with custom work item types
Sometime companies use customized templates with custom work item types. Currently the ADO integration only supports integration with the standard types like "initiatives", "features", "Requirements". Our template supports a custom type called "PI...
3
Already exists
2
VOTE
Enable the parent - child hierarchy for Aha tool so that we can see the view for parent-child relationship.
Enable the parent - child hierarchy for Aha tool so that we can see the view for parent-child relationship. Same like Jira we have parent -child relationship concept of subtask we need in Aha same functionality.
3
Already exists
3
VOTE
Remove large delay (5m) from webhook calls.
Webhook callbacks have a delay that hinders a consistency of custom integrations.
This delay, in addition to making the system less dynamic, makes it impossible to integrate more complex.
A great example of webhook deployment is GitHub, which ma...
1
Future consideration
3
VOTE
Ability to search on the Jira Key
We have many users that have asked me for the ability to search for a Feature based on it's Jira Key. Currently the only way to do that using the Search box is for them to add the Jira Key to the Feature description, and they don't want to have to...
1
Already exists
2
VOTE
Support bi-directional flow of data when mapping Aha! releases to Jira sprints as a field mapping for features
Use case: Aha! releases are mapped to Jira sprints as a field mapping under features. Currently this mapping is only supported in one direction, Aha! to Jira. It would be helpful if this mapping supported the flow of data in both directions.
0
Future consideration
1
VOTE
4
VOTE
API - support sending multiple parameters/values in search query
The API currently only accepts a single value search parameter. There is a requirement to be able to pass multiple parameters/values through the API. For example, execute a search through the API for features that contain 3 specific tag values.
1
Future consideration
4
VOTE
GitHub integration automatic log time upon linked issue completion
The intended use of GH integration is the following:
Create features in Aha
Push to GitHub as a handover of control to engineering
Updates in GitHub trigger status changed in Aha
This is a good start.
If control is passed to engineering to manag...
2
Already exists
2
VOTE
Parent version mapped to 2 different releases - let user decide where to import
The same Jira version may be associated with releases from more than one Aha! workspace. This can happen when different products in Aha! are all being released together. When auto-import is enabled on the integrations and a new record is created i...
0
Future consideration