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, ...

What is the challenge? Sometime when Epics are used, Feature dont move with the Epic by mistake What is the impact? Shipped features that miss the release are incorrectly attached to a future release to ship Describe your idea. Allow shipped rel...

What is the challenge? My custom table looks for values entered in USD x 1,000. I formatted the fields for currency but Aha adds two decimal places automatically. What is the impact? The value displayed is confusing because USD x 1,000 amo...

What is the challenge? When layouts are changed and fields are added or removed an event is logged under the account settings > activity area, but the events are not clearly labeled. What is the impact? Able to see a change has been ...

What is the challenge? We require that all the people on the research team attend the call (interviewer, note taker, UX). The current scheduling integration with calendars is exactly what we need, except that it offers times that any one of the ...

What is the challenge? Today we are using To-dos for various reasons - Action Items, Financial reasons, Filtering activities that are needed to move to next stage etc. But we are not able to visualize all at an object level similar to Related ta...

What is the challenge? Currently, workspace reviewers that have the ability to edit workspace documents such as whiteboards cannot edit embedded whiteboards in record descriptions What is the impact? Reduced collaboration between Aha! cont...

I'd love to be able to highlight a line of text in a field formatted as a note (description/comment etc) and create a to-do (or even a story/requirement/approval/work request with the highlighted text as the title of the task. It would also be gre...

Providing a template would help our users work in Aha! rather than creating one outside and uploading it. Our users need a bit more help than the Vision Description in the Strategy section.

Right now, even after we manually click "Send to JIRA" for the first time for a release, subsequent changes to that release ( for eg. Addition of a feature under that release) do not automatically go through to JIRA. We'd want to have all changes ...