Account settings
Sort by:
Trending
Status:
Showing 645
4
VOTE
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
6
VOTE
Add "Dependency Not Scheduled" as a Delivery Risk
Who would benefit? Users who have enabled the Delivery Risks feature What impact would it make? It would allow to immediately capture on a feature if there is a dependency on a body of work that has not been scheduled. How should it work? Add a fu...
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
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
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
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
11
VOTE
Allow to define the scope of tags/choice list custom field values (account vs. workspace)
It should be possible to define whether the values of choice list and tags custom fields (predefined or editable) are shared at account level (current behavior) or limited to workspace level such that workspaces can share a configuration but have ...
0
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
© 2024 Aha! Labs Inc.•All rights reserved