Account settings
Sort by:
Trending
Status:
Future consideration
Showing 638
2
VOTE
Develop team owners should be able to manage team members
Who would benefit? Team owners that do not have the customization admin role What impact would it make? Currently Develop team owners do not have a place in the team settings to manage the users in their team, but this is a permission owners have ...
0
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
4
VOTE
Allow team leads to manage workspace releases
Engineering managers & team leads sit "in between" Aha! Roadmaps and Aha! Develop. They more than just team owner permissions, but not full workspace contributor permissions. Key use cases Team leads can provide initial estimates on features b...
0
Future consideration
9
VOTE
Required fields to be excluded from features in the parking lot
Required fields cannot be excluded from features in the parking lot currently. However, it would make sense that if you have a feature under your parking lot is because you still have to define certain things and you may not count at that time wit...
0
Future consideration
13
VOTE
Preserve history when converting from one object type to another
Currently when an object is converted to another object type from within Aha! the history is cleared on the new object (Initiative to Master Feature, for example)
From an audit and logging perspective it would be preferable if the history was pres...
1
Already exists
6
VOTE
Make toggling between create/view layouts more obvious within the custom layout editor
The custom layout editor allows you to define the layouts for both the view screen and the create screen for a given record type. The admin needs to toggle between these 2 view types using a drop-down at the top of the screen. This drop-down was n...
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
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
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