Account settings
Sort by:
Trending
Status:
Future consideration
Showing 383
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
8
VOTE
Hide parking lot from certain user roles
Who would benefit? everyone What impact would it make? limits information leakage and information misuse to parts of the organization who don't need to see in progress epic development before it's put in an official release How should it work? wit...
0
Future consideration
29
VOTE
Automation rule that adds a new row to a custom table
In my use case we have a custom table on releases to track changes to the release date. I would like to set up an automation rule so that "when the release is updated and the date field changes to anything" then "add a row to the custom table with...
1
Future consideration
10
VOTE
Paid Seat group "profiles" for SSO provisioning
As a paid seat group owner, I would like to establish standard permissions for users in my paid seat group that I can apply through SSO at the time of seat provisioning. These permissions include both roles (owner, contributor, custom role) as wel...
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
12
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
3
VOTE
32
VOTE
Ability to add PO functions to a Custom Role
We have recently implemented Custom Roles in our space that bumped the PO role to Contributor + Custom (eliminating the ability to add new product and granting paid seat access, etc - see attached) We would like the ability to change some of the t...
8
Future consideration
9
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...
1
Future consideration
2
VOTE
Automation that pulls parent information when child field created
What is the challenge? Currently passing fields from parents to children (epic to feature or initiative to epic) can only be done when the parent is updated. This means when you create an epic under an initiative the fields are not automatically u...
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved