Account settings
Sort by:
Trending
Filter by:
Status
Showing 689 of 9663
2
VOTE
1
VOTE
Business model canvas for customer data
Who would benefit? Product manager and Customer success manager What impact would it make? a page with clear data on each customer How should it work? Customer data in a templatized format will give a handy info to product manager and everyone in ...
1
Future consideration
1
VOTE
Export users from Workspace Settings
Who would benefit? Workspace Owners What impact would it make? This would allow workspace Owners to more effectively request workspace-wide role changes for their users. How should it work? From the Workspace Settings > User screen, there shoul...
0
Future consideration
3
VOTE
A visual map of inheritance, where you can remove or add inheritance in a GUI
For enterprise customers, administrating 100+ Workspaces can be come difficult and changes made at a product line level can be reflected in workspaces that you had not intended. Our Hierachy has grown over time, and now needs to the refreshed and ...
0
Future consideration
4
VOTE
Terminology Changes Affecting Non-Editable Fields
We've renamed Initiatives at the Product level (Epic) which then changes all fields in the Feature record. However, if I'm trying to link to an Initiative at a Product Line - the field in the Feature Record is called something different & user...
0
Will not implement
3
VOTE
Ability to undo changes in the Activities log
When I make a change in Aha! said change is shown in the activities log. The user should have the ability to revert the change made from within the activity log. This functionality should be such that a single change, multiple changes, or date ran...
2
Future consideration
1
VOTE
Ability to set whether a custom number field is allowed to be used by the prioritisation board
Who would benefit? All users What impact would it make? Avoid the potential for data loss How should it work? At the moment, any custom number field that is available on a record's layout is presented as an option to be used to capture the priorit...
1
Future consideration
5
VOTE
permission-restricted release or feature status
We should be able to configure specific release statuses so that they're restricted, editable only by certain users or user groups.
We have a Program Management group which maintains an authoritative list of releases the product organization has c...
1
Unlikely to implement
4
VOTE
Auto-expand tree view in Settings->Configure Products
I understand why the page needs to refresh when I make changes to the hierarchy in tree view (at least I understand why that's easier to code than dynamically resorting the tree). But could the tree at least auto-expand. I spend more time opening ...
0
Unlikely to implement
3
VOTE
In automation rules, evaluate the fields on the triggering object (feature, idea etc.) to set conditional actions
When creating automation rules, we need to know what field value is on the idea that is being created before doing an assign-to action. Right now I can only define an assignment to on ANY idea, which I can already do with default assignees. Give t...
0
Already exists
© 2025 Aha! Labs Inc.•All rights reserved