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...
Joe Carpenter
over 9 years ago
in Account settings
4
Unlikely to implement
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...
Jake Ludwinski
almost 5 years ago
in Account settings
4
Future consideration
Number of functionalities in Main Menu contain different types of views we can use. However, not all these views might be useful or updated and it would be great to have the option to choose what views we use and we don't and hide the unused ones ...
When you login in from the aha.io page it spawns a new browser page. Stop this behavior and log me in from the current tab. I did not ask for a new tab to open and this ends to an endless number of useless tabs being opened. Please change how this...
Guest
over 2 years ago
in Account settings
0
Future consideration
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...
Carl Ambrus
almost 5 years ago
in Account settings
0
Future consideration
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...
Guest
almost 5 years ago
in Account settings
0
Future consideration
Opening 2-factor authentication to other providers
aha!'s 2-factor authentication implies signing up with a designated 3rd party. We would like to include aha! with the other solutions in our IT portfolio, for which 2-factor authentication is supported by a different supplier than aha!'s partner.
Guest
almost 5 years ago
in Account settings
1
Future consideration
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...
David Spada
almost 10 years ago
in Account settings
1
Unlikely to implement
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...
Guest
almost 10 years ago
in Account settings
2
Unlikely to implement