Account settings
Sort by:
Trending
Status:
Showing 681
4
VOTE
Batch changing of users from Password to SAML/SSO
We recently instituted SSO on our Aha account, but currenlty have a couple of dozens folks who have the typical username/PW login profile active. I'd like to make a universal/batch change to force all users to log in via SSO, however there is no c...
4
Unlikely to implement
1
VOTE
Allow Timeframe to be used for filtering in Worksheet fields
As part of our maturity review we want to quickly understand if a particular workspace has planned their Initiatives and Goals in the current Timeframe (e.g. this year). To do this we'd like to create a worksheet on the workspace object, but the f...
0
Future consideration
1
VOTE
Provide help with consequences of merging custom fields
The Aha! KB article on merging and converting custom fields explains that there are implications for integrations and reports when merging fields. Specifically: If an integration included the old custom field, you will need to update the field map...
0
Future consideration
2
VOTE
Assign Custom fields to a parent workspace
We have over 250+ custom fields being utilized by various workspaces. Because we cannot assign a custom field to a particular workspace all 250+ fields are visible in every filter in every workspace. If we could have the ability to define which wo...
4
Future consideration
2
VOTE
Inconsistent / Broken Terminology
Within Marketing, Business and Project Lines, the customize terminology setting is broken and creates an inconsistent user experience that confuses users. Within the 'Customize Terminology' setting (Settings > Product Line > Terminology), if...
0
Future consideration
4
VOTE
Extend product tree to support different configurations of a product line
I manage a product line where each product has different configurations. Currently I get around it by making different releases, but it really doesn't solve the problem because the different configurations have different requirements. So, being ab...
1
Unlikely to implement
4
VOTE
1
VOTE
Prevent non-billing admin workspace owners from adding paid seats outside their owned paid seat groups
The cure was determined to be worse than the ailment. Moved to an idea, tracked here: https://big.ideas.aha.io/ideas/A-I-13997 Currently there is an edge case where project owners are able to add users that take up paid seats outside the paid seat...
0
Will not implement
2
VOTE
Line and Workspace management - stop collapsing the Line / Workspace hierarchy each time you complete a Line
If we leverage UX / UI, when a user-persona leaves a data structure in a window, they should expect it to remain the way they left it when they return, or complete a task Currently, when I go to the Customized Workspaces --> then expand some or...
0
Future consideration
4
VOTE
In workflows, add the ability to limit setting a certain status to certain users.
In workflows, most of the time a status like "approved" is available. However, at the moment everybody can set this status, so it pretty useless.
If only certain users (e.g. with a certain role) could set the status to approved it suddenly gets v...
2
Unlikely to implement
© 2025 Aha! Labs Inc.•All rights reserved