Account settings
Sort by:
Trending
Status:
Future consideration
Showing 640
8
VOTE
Ability to vary a team's cost by calendar year
A team will have a defined cost that is applicable for the calendar year. When putting together a multi-year plan, there needs to be a way to account for factors that will cause the team's cost to increase (e.g. inflation). There needs to be an ab...
0
Future consideration
7
VOTE
Be able to select a default scenario for all users (Capacity Planning)
Right now, when you add a new scenario (even if it is just a test scenario), all users will be defaulted to that new scenario. We will have dozens of people using the tool, so the inability to get them to all set their own defaults to our standard...
0
Future consideration
2
VOTE
Ability to set a specific date in automation rules
Who would benefit? everyone What impact would it make? high priority for our key product team In the area in setting an Automation Rule you can set dates for things like 1 day or 1 week from today. Our team wants to enter a specific date to be set.
2
Unlikely to implement
9
VOTE
Ability to select only one user from the "User Field" custom field
Currently the "User Field" (custom field) in Aha! allows you to select one or more Aha! users.
It would be useful to have a "User Field" whereby a user can only select one user. This is important for us, as one of our User Fields sycnhronises wi...
1
Future consideration
4
VOTE
3
VOTE
Configure terminology of Notebook navigation menue and Documents sub-menu
Currently terminology can be configured for workspace, goal, initiative etc. Would like the ability to also use our own terminology for Notebook and Documents as the recent out of the box changes to terminology don't mense sense to our users.
0
Future consideration
2
VOTE
Allow Reviewers to update existing rows in custom tables
We would like to implement Custom Tables in Releases to collect cross-functional status information from different functional/project teams involved in each release. These teams are not part of product management and would only use Aha! to update ...
0
Future consideration
4
VOTE
Show layouts used in workflows in "Used in" column
In Settings > Account > Custom Layouts, there is a "used in" column that displays which workspace(s) use the custom layout. However layouts can be overwritten by a layout used at the workflow status level. Therefore, some custom layouts will...
0
Future consideration
1
VOTE
Ability to list users who are using API Keys
What is the challenge? Users have generated API Keys to update Aha and the Account Admins would like to know which users are using API Keys. What is the impact? How can we know who is updating using an API and understanding where the API is used t...
0
Future consideration
2
VOTE
Ability for a user to see what permissions they have
Our Aha! admin team frequently gets asked "Do I have a paid seat and which workspaces do I have edit permissions for". And so every time, someone from the admin team has to go take a look in the user admin area and report back. This causes an unne...
0
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved