Integrations
Sort by:
Trending
Filter by:
Status
Showing 993 of 9641
2
VOTE
Allow automatic imports of child records when parent records exist in a different workspace
What is the challenge? Currently, for Jira integrations, when you have parent/child records in Jira that span multiple Jira projects connected to multiple Aha! workspaces, all child records created will need to be manually approved as an integrati...
0
Future consideration
13
VOTE
Allow additional Link Types in the 'Links to' field
Within AHA we are mapping
Releases -> ADO Release Work Item
Master Feature -> ADO Epics
Features -> ADO Features.
Master Features need to be located in the Release in which they complete. But Features (that contribute to this Master F...
2
Future consideration
16
VOTE
Onedrive for Business Group file libraries
You have implemented OneDrive for Business - however it only allows attaching files from my own document library. I'd like to be able to attach files from other Sharepoint online document libraries - such as those created through 365 Groups and Te...
4
Future consideration
14
VOTE
Allow users to modify the AHA visualforce pages in Salesforce integration
The AHA window size in the visualforce pages is so small and users have to scroll to view the entire list of ideas related to an Account/Case/Opportunity. It would be great if we can customize the AHA layout in Salesforce(adjust the height of the ...
1
Already exists
7
VOTE
Fix field population in Aha/Jira integrations to only rely on email address or other specific data
Today when the Aha/Jira integration runs it looks up users in Jira based on email, then failing to find a match it checks first name, then last name. Jira returns results for these and Aha will select the first return. The problem is that if we ha...
1
Future consideration
13
VOTE
Expose scorecard metrics as integration fields
Currently, scorecard metrics do not appear to be available to integrations. We would like to represent these components in our development system in the interest of transparency to our development teams, but there is no way to get this data across...
3
Future consideration
19
VOTE
6
VOTE
Project level automation with Jira
Requesting a change to Aha! Jira integration to allow for project level automation. Project level webhooks send payloads differently than system level payloads. If support for project level webhook payloads were added, we could enable multitudes o...
0
Future consideration
7
VOTE
12
VOTE
Allow Aha! user name to populate DevOps board user
When working with multiple users, we need to be able who created what, commented on or changed something. As of right now, the user name (Admin) of who configured the Integration (Azure DevOps Services) is the one that appears on every item in Dev...
3
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved