Account settings
Sort by:
Popular
Status:
Showing 649
13
VOTE
Preserve history when converting from one object type to another
Currently when an object is converted to another object type from within Aha! the history is cleared on the new object (Initiative to Master Feature, for example)
From an audit and logging perspective it would be preferable if the history was pres...
1
Already exists
13
VOTE
12
VOTE
Amount of changes made by a user when Account Level permissions
What is the challenge? Business Problem to Solve: Utilization report: We would like to know who is utilizing the Aha Account Level? How can we manage the amount of changes made by a user when Account Level permissions have been granted? License co...
1
Future consideration
12
VOTE
Allow to define the scope of tags/choice list custom field values (account vs. workspace)
It should be possible to define whether the values of choice list and tags custom fields (predefined or editable) are shared at account level (current behavior) or limited to workspace level such that workspaces can share a configuration but have ...
0
Future consideration
12
VOTE
12
VOTE
Enable Conversion of Product Workspace to Product Line
In the creation / setup phase of workspaces and product lines, we cannot change the workspace designation to a product line. Instead we have to move the data objects from the existing workspace to other workspaces, then delete the workspace that c...
1
Future consideration
12
VOTE
Auto assign default permissions for all new users
Appreciate this can be achieved via SSO but it would be a great admin feature to have on the AHA side of the interface. As an admin i would like to be able to set a default permission for product & role rather than have to dialogue with our IT...
4
Future consideration
12
VOTE
Separate Scorecard for Epics
I would like to know if there is a way to establish a scorecard for Master Features that is separate from the scorecard used for Features. We would like to use a specific scorecard at the Master Feature level such as estimated revenue, cost saving...
3
Future consideration
12
VOTE
Bulk edit "custom table relationship" custom fields
Bulk edit is not currently available for "Aha! record relationships" custom fields, nor "custom table relationship" custom fields.
Adding the ability, at least for "custom table relationship" custom fields will go a long way to increasing usabili...
0
Future consideration
11
VOTE
Delivery Risks - Ability to Inherent to Child Workspace
What is the challenge? If one product line (parent workspace) wants to implement Delivery Risks, we would need to individually go through the settings on each child workspace to configure. What is the impact? It is very time consuming for large pr...
2
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved