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 ...
Leanne Miller
6 months ago
in Account settings
0
Future consideration
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...
Marina Reyna
over 6 years ago
in Account settings
7
Future consideration
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...
Jeanette Resnikoff
over 2 years ago
in Account settings
1
Future consideration
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...
Guest
about 5 years ago
in Account settings
5
Future consideration
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...
Dale Crane
about 1 year ago
in Account settings
0
Future consideration
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...
Stephanie Lechner
12 months ago
in Account settings
0
Future consideration
Using automation, allow features and requirements to inherit a Rollup release name
What is the challenge? Roll up releases are ideal to synchronize releases of services within a platform. As an example, on Service A and Service B in Platform A are both released on the same schedule. Our developers work within Jira and Devops, an...
Steve C
about 2 months ago
in Account settings
0
Future consideration
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...
Karla Johnson
almost 3 years ago
in Account settings
1
Future consideration
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 ...
Karla Johnson
about 2 years ago
in Account settings
0
Future consideration
Option for workspace template to not override all settings when first applied
What is the challenge? When applying a workspace template, even if the settings are marked as unlocked in the template, once applied to a workspace the existing workspace settings will still be changed. This is not always the desired experience. I...
Max Robbins
7 months ago
in Account settings
0
Future consideration