My ideas: Account settings
Sort by:
Popular
Status:
Unlikely to implement
Showing 651
12
VOTE
Separate Scorecard for Epics
I would like to know if there is a way to establish a scorecard for Master Features that is separate from the scorecard used for Features. We would like to use a specific scorecard at the Master Feature level such as estimated revenue, cost saving...
3
Future consideration
12
VOTE
Bulk edit "custom table relationship" custom fields
Bulk edit is not currently available for "Aha! record relationships" custom fields, nor "custom table relationship" custom fields.
Adding the ability, at least for "custom table relationship" custom fields will go a long way to increasing usabili...
0
Future consideration
11
VOTE
Delivery Risks - Ability to Inherent to Child Workspace
What is the challenge? If one product line (parent workspace) wants to implement Delivery Risks, we would need to individually go through the settings on each child workspace to configure. What is the impact? It is very time consuming for large pr...
2
Future consideration
11
VOTE
Increase Aha Product Workspace Name character limit and confirm product name changes
What is the challenge? Business Problem to Solve If the Product Owner attempts to change the Product Workspace name which exceeds 100 characters then the browser seems to accept the name change but upon refreshing the name change, the browser reve...
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
11
VOTE
Introduce Customization Owners
As a large organisation with several independent product verticals, we need the ability to lock down account-level customizations (e.g. layouts, custom fields, workflows) by owner (+ collaborators) so that we can retain adequate controls without l...
0
Future consideration
11
VOTE
Allow access to Mockup tool for users with reviewer security
Mockup provides a powerful method for idea contributors to communicate their ideas. However the mockup tool is only available to users with contributor or greater permission. But contributor is too permissive, allowing user to create features, str...
0
Future consideration
11
VOTE
A Private View of Comments or Notes
It would be great if we could mark Comments and Notes as private or restricted based on the User's email domain (or something) so that teams who work with external clients (like my firm does) can still have "internal conversations" within Aha but ...
1
Already exists
10
VOTE
Quick navigation to settings pages by name
When working with Aha! customers, one part that slows down users as they set up their account is figuring out how to navigate through to the page they need. Let's say I am helping a customer add a custom layout and statuses to their ideas and idea...
0
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
© 2025 Aha! Labs Inc.•All rights reserved