API
3
VOTE
Support creation of paid seat groups via API
What is the challenge?
Admins who manage users and provisioning programmatically can work with many account settings through the API, but they cannot create paid seat groups there.
This forces teams to leave automated provisioning workflows an...
Future consideration
26
VOTE
Expose Structured TestRail Test Data in Aha! Develop for Reporting and Traceability
What is the challenge?
The TestRail integration displays test data within Aha! Develop but does not expose it as structured, reportable fields. Attributes like Test Case ID, Test Status, Execution Result, and Coverage render as a display only bl...
Future consideration
2
VOTE
Enhance the Audit History API to provide complete user information for both custom User-type fields and system User-type fields. For custom User-type fields, in addition to the existing raw_value (user IDs), expose the corresponding user email addresses (similar to the email_value field returned by the entity retrieval APIs). This would eliminate the need for additional user lookup API calls and keep the Audit History API consistent with the entity retrieval APIs. For system User-type fields (such as Assigned To, Created By, etc.), enhance the Audit History API to expose the underlying user identifiers and email addresses, rather than only the display names. Providing user IDs and email values would enable reliable processing of audit records, avoid ambiguities caused by duplicate display names, and offer a consistent experience across all User-type fields. These enhancements would improve API consistency, reduce integration complexity, and make audit history processing more reliable for customers integrating with Aha!.
What is the challenge? The Audit History API currently provides limited information for User-type fields. For custom User-type fields, it exposes only the user IDs (raw_value) without the corresponding email addresses. For system User-type fields ...
Future consideration
10
VOTE
Add granular scoping controls for API keys
What is the challenge?
API keys inherit the full permissions of the user who creates them, and there does not appear to be a way to scope the key itself to specific workspaces, folders, or record types.
This creates concern internally when bui...
Future consideration
3
VOTE
Update MCP to write to equation-sheet sub-fields in worksheet custom fields
What is the challenge? We have certain worksheet custom fields in our initiatives that calculate things like rolled up capacity over time, etc.
What is the impact? Teams using tools like Claude to manage their workflows can have Claude update ini...
Likely to implement
38
VOTE
Provide Microsoft Power Automate Connector
What is the challenge?
Easily integrating with Aha! using Microsoft integration platforms
What is the impact?
Having to rekey data - costs time
Describe your idea
Microsoft provides a low-code multi-platform integration service calle...
Future consideration
8
VOTE
1
VOTE
2
VOTE
Add an API endpoint (or option) to create/link an integration record (e.g. Aha ↔ Jira) with use_remote/“commit from Jira” behavior, so Jira can overwrite/sync the Aha entity on initial link—matching what the UI supports.
What is the challenge? The current API does not support programmatically creating an integration link and selecting the “use_remote / commit from Jira” option in the same flow (or at all), so the UI can do something the API cannot.
What is the im...
Future consideration
2
VOTE
API for updating Collections on documents
What is the challenge? Updating the Collections on a document is currently a manual process. We have an Employee Handbook published for all employees. It is comprised of folders that come out of various workspaces - in order to make sure authors a...
Future consideration
© 2026 Aha! Labs Inc.•All rights reserved