Integrations
Sort by:
Trending
Status:
Showing 942
1
VOTE
Map Requirement Due Dates and Assignee to Trello Checklist
We currently have activity mapped to card and requirement to checklist. In Aha!, we are using due dates and assignees on our requirements. In Trello Standard or Premium, due dates and assignees are available at the checklist level, but there is no...
0
Future consideration
1
VOTE
Iteration Path Integration with Aha & ADO
Though we have Iteration path integration between Aha and ADO. This is currently limited to show dynamic values for the integrations. Also the Iteration Path is based on the Area Path, the values of Iteration path cannot be filtered / shown releva...
1
Already exists
1
VOTE
3
VOTE
Feature Email update notification to include link direct to Jira record
From a time saving point of view it would be really handy to include the Jira link in the email notification that comes when an item is updated. This field/link already exists within the feature itself so should be easy enough to add in to the ema...
0
Future consideration
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
1
VOTE
Alternative JSON format for changes property in Activity webhook
We are attempting to read changes to the Ideas record type using the Activity webhook.
Most of the information is straight forward, in an expected JSON format.
But for changes, the data comes through as an array of json objects, instead of p...
1
Future consideration
3
VOTE
3
VOTE
Allow existing Trello comments to be imported
The integration version of Trello import/export doesn't allow importing comments from Trello cards that existed prior to the integration/sync. This prevents us from retaining significant discussion about a feature (or idea) in the Aha copy of the ...
1
Future consideration
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
© 2024 Aha! Labs Inc.•All rights reserved