Account settings
Sort by:
Trending
Filter by:
Status
Showing 471 of 8115
1
VOTE
2
VOTE
Maintain item ID when Promoting/demoting
When changing a feature to master feature, to initiative and back (demoting), the item is recreated, resulting in a new id, and a new link. If a team is documenting the features/master features etc with links, this documentation will lose value wh...
0
Future consideration
1
VOTE
In Account Admin, allow workspaces to be sorted alphabetically.
When creating a new workspace in a line, it adds that workspace to the bottom. If there are already many workspaces (that happen to be sorted alphabetically, it would be nice to be able to reorder the list to sort the new workspace where it belong...
0
Future consideration
2
VOTE
Allows us to use Display Name with OKTA
OKTA has a username & display name option, however, Aha! doesn't pull in the Display name to give you the option to visualize that or give you the option to edit the name. This is a frequent request from my users who do not go by a legal name....
1
Future consideration
3
VOTE
Increase available text area in system broadcast when an image is not specified.
The new broadcast message format looks good when an image is specified, however when an image is not used it would be great if the message text could expand to make better use of the available space.
1
Future consideration
1
VOTE
Simplify management of custom field list values
The "Configure options for" a predefined list custom field forces the user to click on "edit" to go a separate screen to do either name change or color change. These two can be accomplished easily on the original field edict screen list as well wi...
0
Future consideration
1
VOTE
Account User Management Efficiency
Ability to bulk edit a set of users would be beneficial when onboarding new folks or there are organizational changes that impact access. When working with contractors, we only allow access to specific workspaces - thus, when that team(s) changes ...
0
Future consideration
1
VOTE
Aha Configuration: use the custom terminology from the topmost Product Line
We use Aha's terminology option to remap several Aha terms to the words we use in our software lifecycle (thank you for that!). For instance, epics are re-labeled "initiatives", features are "epics", and requirements are "stories". However, the de...
0
Future consideration
2
VOTE
One Field Directory for Records
It is very tedious as an admin to have to recreate fields numerous times that are used across all record types. Most systems that I have built out (SFDC, JIRA, etc.) have one entity database that is shared across all record types and it would be i...
0
Future consideration
1
VOTE
