Support new GitHub issue custom fields in GitHub integration
What is the challenge? In May 2026, GitHub released a new way to create issue fields: https://github.blog/changelog/2026-05-21-issue-fields-are-now-in-public-preview-for-all-organizations/. This new method of creating issue custom fields is not cu...
Support Mapping Only Specific Issue Types in Github Integration
What is the challenge? To import only certain GitHub issue types into Aha!, customers must use constant mapping. But GitHub can have many more issue types than Aha! can map. When all issue types aren't mapped all issue types are set to the default...
Jessica Morgan
26 days ago
in IntegrationsFuture consideration
What is the challenge? Only Aha! owners/contributors can use the MCP server connection
What is the impact? Limits the scope of use of the MCP server
Describe your idea. Enable the MCP server to work similar to the Aha! REST API with user permiss...
Users with the Configure integrations permission can be Recipients of integration notifications
What is the challenge? Currently, only workspace owners can be selected as "Recipients" of integration notifications on the Enable step of the configuration.
What is the impact? Users with a custom role that has the Configure integration permissi...
Ben Hollier
11 days ago
in JiraLikely to implement
Ability to sync Releases to Azure Dev Ops as a Linked Item
What is the challenge? We do not manage our releases as iterations in Azure Dev Ops - we have a dedicated work item type 'Release' that we associate with all items within a release. As we use Epics, we currently need our integration to be configur...
Zendesk Bug promotion straight to Roadmap Parking Lot
What is the challenge? I want to be able to promote bugs from Zendesk directly to my Roadmap parking lot and bypass the need for the idea portal or the Develop team.
What is the impact? Additional workload to push bugs to the idea portal and then...
Matthew W
4 months ago
in IntegrationsFuture consideration
Allow aggregating multiple Jira stories into a single Aha! requirement (summary sync option)
What is the challenge? The Aha!–Jira integration requires a 1:1 sync between Jira stories and Aha! requirements. For teams managing large epics, this creates excessive noise in Aha! and makes it difficult to maintain clean, high-level views for po...
Katie Tokarz
about 1 month ago
in JiraFuture consideration
What is the challenge? What Project Name is an integration connecting to for Rally Integrations What is the impact? Cannot create a list report showing what Project Name is an integration connecting to in Rally Describe your idea Add the 'Project'...
Mike Jacobson
over 1 year ago
in RallyFuture consideration
ADO integrations are sending to legacy domain "https://fredwin.visualstudio.com" instead of sending to "https://dev.azure.com/fredwin". Though the integration works as expected, clicking the link to the integrated record sends to the incorrect dom...
Guest
10 months ago
in IntegrationsFuture consideration
It would be great to have a dedicated integration user instead of having to use a user license for this purpose. I would love to keep my user and the updates from integrations (Jira, TFS,...etc) separate so that it is clear who made the update in ...
Guest
over 9 years ago
in Integrations / JiraFuture consideration