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
over 5 years ago
in Account settings
6
Future consideration
When configuring scorecards, it would be useful to be able to set a default value for a metric within the given range. For example if a metric range runs from -10 to 10 (some metric may have a positive or negative impact on our product), it appear...
Guest
about 10 years ago
in Account settings
3
Unlikely to implement
Add "Parking Lot" to the terminology area and allow a user to rename this. We have always used "Backlog" as our holding area for unscheduled ideas. When exporting the data to a report, executives aren't quite sure what "Parking Lot" refers to!
Guest
almost 8 years ago
in Account settings
6
Unlikely to implement
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...
Marina Reyna
over 5 years ago
in Account settings
8
Future consideration
I would like to have the ability to set an automatic deactivation of user accounts after XX days of inactivity.
Use Case: As an admin with a large user base, I frequently have users moving between groups, changing responsibilities, etc. Sometimes...
Joe Carpenter
over 8 years ago
in Account settings
2
Future consideration
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...
Kelly Sebes
about 4 years ago
in Account settings
1
Future consideration
I need a history log to review admin changes to templates, integrations, etc.
Mistakes do happen, but having a history log helps us determine how big the impact is, and where to begin correcting the issue. It also prevents a case for Aha support.
Wen-Wen Lin
about 6 years ago
in Account settings
0
Future consideration
The ability to have a tool tip for a standard field
Aha Score is a standard field in Aha and like many others, you still can configure it based on your business requirements. This is why it would be good that the reviewers' users be able to understand the metrics under that score and have quick vis...
Guest
almost 5 years ago
in Account settings
4
Future consideration
Allow inherited custom field layouts that can be extended for specific products
We would like to have a core set of common fields used in the field layouts for all products, but there will still be a need to support custom fields needed only by a subset of products. If we could have products inherit a custom field layout and ...
Guest
about 7 years ago
in Account settings
3
Future consideration
We are a large organization with many users. We would like to share Aha! with interested individuals and that number could be hundreds or thousands. In order to alleviate that, the recommendation is to allow a self registration process that would ...
Guest
almost 9 years ago
in Account settings
8
Unlikely to implement