My ideas: Account settings
Sort by:
Popular
Status:
Future consideration
Showing 645
13
VOTE
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
Make worksheet fields work the same as calculated columns
I can use this equation: if (field("fieldname") >= today(), true, false) -- where the field name is a custom date field in an Epic layout, as a calculated column but it won't work as a custom worksheet field equation because have to give the fi...
0
Future consideration
12
VOTE
Limit Workspace Permissions for User with Product Line Owner Permission
We need an ability to Limit Workspace Permissions for User with Product Line Owner Permission.
Currently "Users with access to product lines also have access to their underlying products."
Use Case:
We have a number of Product Operations Workspace...
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
© 2024 Aha! Labs Inc.•All rights reserved