Account settings
Sort by:
Popular
Status:
Unlikely to implement
Showing 678
12
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
12
VOTE
12
VOTE
12
VOTE
Auto assign default permissions for all new users
Appreciate this can be achieved via SSO but it would be a great admin feature to have on the AHA side of the interface. As an admin i would like to be able to set a default permission for product & role rather than have to dialogue with our IT...
4
Future consideration
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
11
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
11
VOTE
Ability to Further Control Notifications
I currently get notifications from Jira when issues/features I have created or am watching get updated. I then get the exact same updates from Aha! for these same issues, causing a frustrating duplication. The issue is, there is no way to change t...
2
Future consideration
11
VOTE
Automation Rule - Add "Release" as an Action
In my scenario, there are times that a feature is in a given status, and as a result, I would want that feature to move to a different release. For example, If I abandon a feature, I want it removed from a release and put into a parking lot where ...
2
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
Advanced product permissions for users
I like that Aha! allows me to share my product data with my organization, but I need more granular controls over who can create, read, update, and delete data. It would be great if I could create custom roles and assign them to users. Additionally...
1
Unlikely to implement
© 2025 Aha! Labs Inc.•All rights reserved