Automation trigger in Aha! to call external Glean agent and write back results
Craeta an automation or trigger in Aha! that can:
Read a PRD link stored in a custom field on a feature
Call a Glean agent (via API or similar) and pass that PRD link
Receive the generated text response (e.g., roadmap-friendly feature name, ...
Guest
3 days ago
in IntegrationsFuture consideration
Ability to send ideas portal link in Aha! ideas <> Jira integration
It's possible to send the Aha! URL to a Jira field, but most Jira users don't have access to Aha! so it would be beneficial to have the option to send the ideas portal link for the idea instead so that it can be easily accessed from Jira.
Guest
12 days ago
in IntegrationsFuture consideration
Ability to send the email address of the ideas portal that created an idea to Jira
Currently only Aha! users that create an idea can be sent to Jira using the Created By User field. Given that many ideas are created by ideas portal users that are not Aha! users, it would be desirable to be able to send these users' email address...
Guest
12 days ago
in IntegrationsFuture consideration
Integration to delivery tools not proactively sending comments
What is the challenge? Comments do not immediately integrate over
What is the impact? You have to retroactively send comments after the integration so need to add an extra comment
Describe your idea. When an integration is created, send the comm...
Russell Glenn
19 days ago
in RallyFuture consideration
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
25 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...
Ensure when integrating a parent item to Jira that the child items are also mapped
What is the challenge?
When you integrate a parent item like an Aha! feature with a Jira epic the child items of the Jira epic are not automatically integrated as tickets on the Aha! feature.
This means you need to do a separate import of chil...
What is the challenge?
At present you can only select all fields from either Jira or Aha! as the source of truth for integrating an initiative/feature/ticket to Jira.
This presents problems when you have good content on both sides and you want...
What is the challenge?
Severe Context Switching: Product managers, engineers, and stakeholders waste significant time context-switching between Aha! Roadmaps and other enterprise workspaces to look up statuses, strategic alignment, and feature d...
David I.
about 1 month ago
in IntegrationsFuture consideration
Sending records via development integration should allow users to continue working in Aha!
What is the challenge? Currently, when you send a record via a development integration, the Aha! user interface cannot be used until such time the job completes and the integration link appears on the integration field on that record
What is the ...
Terence Osmeña
about 1 month ago
in IntegrationsFuture consideration