Pinned ideas
PINNED
Chrome extension to capture feedback from anywhere
What is the challenge? We work in many applications and Aha! can not build custom integrations for all of them. This makes it very hard to users of those applications to capture feedback and store it all in Aha! ideas. What is the impact? This res...
All ideas
Sort by:
Trending
Status:
Showing 9713
8
VOTE
Include Requirements when using AI Draft Release notes from a release
Who would benefit? PMs What impact would it make? Save time from creating a list report How should it work? Using AI Draft Release notes directly from a release doesn't allow you to pull in requirements of features that are contained within that r...
1
Future consideration
3
VOTE
Allow epics to inherit prioritisation scores from features
What is the challenge? We prioritise features, not epics. However, it's still useful for many reasons (e.g. reporting) to have a prioritised view of epics as well. There's no way that we will spend the time to score epics separately though. What i...
0
Future consideration
28
VOTE
7
VOTE
Allow updating child initiatives based on parent initiative fields in automations
Who would benefit? Those using roll-up initiatives to manage strategic work. What impact would it make? After updating a parent initiative, this would allow users to quickly have child initiatives update with relevant info without having to go thr...
0
Future consideration
18
VOTE
View in Aha! the author of a comment created in Azure DevOps
In integrations with Azure DevOps, comments created in ADO show the integration name rather than the individual as the creator of the comment when looking at it in Aha!. This can cause confusion for Aha! users who can't easily understand the conte...
1
Future consideration
14
VOTE
Follow custom workspace line terminology when viewing Roll up to workspace goals
When a workspace line references its parent, the naming of that parent should match the parent level, not the workspace level. By not reflecting the customized terminology we are introducing layers of confusion for the team members who don’t spend...
1
Future consideration
4
VOTE
Allow automations to update records created by the same automation
What is the challenge? Automations can be used to create new to-do, approvals, work-requests, and even requirements on features. It would be helpful to be able to populate certain fields on the newly created records at the same time that they are ...
0
Future consideration
3
VOTE
Configure default record link type used when work requests are accepted
What is the challenge? Looking for the ability to request work from other workspaces, but the default record link type is a dependency. What is the impact? Today when a work request is accepted the new record and original record are connected thro...
0
Future consideration
20
VOTE
Support parent-child linking across workspaces and Rally projects through integration.
In the Aha! we have Features that reference a parent Epic in another workspace. In Rally we have portfolio items that are children of a Capability in another project. This cross workspace/project relationship is supported in Aha! and Rally, but th...
1
Future consideration
16
VOTE
© 2025 Aha! Labs Inc.•All rights reserved