Account settings
Sort by:
Popular
Status:
Showing 659
25
VOTE
Self Registration Capability for User Acess
We are a large organization with many users. We would like to share Aha! with interested individuals and that number could be hundreds or thousands. In order to alleviate that, the recommendation is to allow a self registration process that would ...
8
Unlikely to implement
24
VOTE
Apply workspace templates to lines
Often settings like layouts, terminology, and navigation for parent lines may be purposefully different than workspaces. It would be helpful to drive standards for lines by allowing templates to be applied at those hierarchy levels. A few examples...
2
Future consideration
24
VOTE
Ability to Customize Formatting on Layouts
It would be useful to be able to customize layouts. For example, add section markers to separate fields for a more organized view, add helper text underneath field names that doesn't disappear as soon as the user starts typing, and arrange related...
4
Future consideration
24
VOTE
Make workflow status description visible for everyone
The configuration of work flow statuses is a great tool to customize your view in aha. Unfortunately the Status descriptions are only visible in the configuration mode (which is only available for a specific typ of user). This leads to confusion f...
5
Future consideration
23
VOTE
23
VOTE
Custom Fields Permissions
When creating custom fields for ideas or features we need ability to select which user group has rights to edit it. We created a field named owners, with multiple select options from which a product owner can select several names of people that ow...
6
Unlikely to implement
22
VOTE
User Report - Additional Filter - Last Activity
Being that we don't have a reliable user access management tool, our Admins clean up the users if no activity after 90 days. Unfortunately, there isn't a way to filter this, so I must click every user on the page in order to disable in bulk. Click...
1
Future consideration
22
VOTE
Recycle Bin - increase the # of days from 7 to 30 days
Being that we had a situation with deleting workspaces & finding a bug, we realize that 7 days is not enough time to recover data in case the situation isn't uncovered within that time frame. If data is changed (bulk edit, deletion, etc), user...
6
Future consideration
22
VOTE
22
VOTE
Allow Requirement Dates to drive that roll up to a Feature to drive that Feature's start & due date.
We integrate with Jira Engineering work at the Requirement level and must see dates associated with Jira Stories as Requirements in Aha! Since addressing the Requirements / Jira User Stories make our Features a reality, we request that a setting b...
4
Unlikely to implement
© 2025 Aha! Labs Inc.•All rights reserved