Account settings
Sort by:
Trending
Status:
Likely to implement
Showing 645
50
VOTE
Make admin access multi-level by organization/product line
We have multiple organizations/Business Units/Groups with their own product line in the hierarchy. We would like to be able to make them admin of just that area so that they can make the customizations they need without negatively impacting produc...
7
Future consideration
19
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...
1
Future consideration
38
VOTE
Introduction of further customization user permissions
It would be wonderful if Aha! had the option to customize user permissions when it comes to adding or editing ideas, adding or editing features, etc. For example, one user could have permission to only work with requirements while not having the o...
6
Future consideration
3
VOTE
Support notification on custom table updates
What is the challenge? Would like to send a notification to specific users when a new record has been added to a custom table. What is the impact? Today there is no alert when a custom table record is added or adjusted. Users need to look at repor...
0
Future consideration
4
VOTE
Add ability to set system wide automation rules
What is the challenge? I need to implement automation rules for the entire org for Ideas. What is the impact? I have 50 workspaces that need the same automation rule for Ideas. I cannot use the workspace template because we only require a unified ...
0
Future consideration
1
VOTE
Allow user be be set to "default unassigned" using automation
What is the challenge? I want to remove me the PM from the assigned field once the work has been sent to my development team, so that the right person can assign themselves. What is the impact? I have to remember to remove me from the field. Descr...
0
Future consideration
8
VOTE
Allow Workspace templates to inherit layouts from product line
Who would benefit? Anyone who wants to use a workspace template for things like automation, but wants to use product line inheritance for layout configuration. Our automations are able to improve data quality and reduce administrative overhead for...
0
Future consideration
20
VOTE
Allow ability to limit valid values in Feature fields to only display relevant values for the workspace.
When defining features in a workspace, you should only need access to utilize valid values from selected workspaces. Each workspace owner defines and reports on their valid values very differently. When all valid values from every workspace are di...
1
Future consideration
7
VOTE
Allow Workspace Owners to import users in bulk
Who would benefit? Workspace Owners who are not admins What impact would it make? Workspace owners who are trying to invite several users to their workspace--allowing them to import in bulk increases efficiency so they don't have to add these user...
0
Future consideration
15
VOTE
Pass data in shared fields between objects through linked objects
We would like data to be passed using shared fields across objects the same way promoted objects work. Today, if a field (e.g UCMGID) exists with same API key in IDeas, Features, Epics etc, that data will be passed when the Idea is promoted. What ...
0
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved