Account settings
Sort by:
Trending
Status:
Showing 638
1
VOTE
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...
0
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
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
37
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...
5
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
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
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
4
VOTE
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...
0
Future consideration
3
VOTE
Create Custom Layouts for Custom Tables
What is the challenge? I can´t create custom layouts for custom tables What is the impact? I can´t group fields depending on the end user priorities, I can´t turn field to read-only if needed, I can´t edit relationship data with other records Desc...
0
Future consideration
2
VOTE
Better way to find custom fields on the edit layout screen
What is the challenge? When editing a custom layout, we only show one page of custom fields. If the field you are looking for is not on that page, you have to search for it. What is the impact? Describe your idea Allow for the user to page through...
0
Future consideration