Account settings
Sort by:
Trending
Status:
Showing 645
3
VOTE
When updating our Aha! account domain we need embedded links to records in Aha! that reference our old domain to continue to work
We are considering updating our Aha! account domain and would like for links embedded in our Aha! records that reference our old domain to continue to work to provide continuity for our team. Manually updating these links is very time consuming.
2
Likely to implement
2
VOTE
Dynamically adjust whitespace on "Workspaces" page in Settings
Who would benefit? Customers with a lot of workspaces and workspace lines What impact would it make? This would make it easier to see more content on this page at once and more easily adjust the hierarchy and edit workspaces. How should it work? T...
0
Future consideration
1
VOTE
Auto disable Users when their Okta account is disabled
What is the challenge? When users leave the company and their Okta accounts are disable, their Aha user accounts remain active What is the impact? This impacts our available user license count in Aha Describe your idea Improve the Okta integration...
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
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
2
VOTE
Add more specificity/granularity around automation logic.
Who would benefit? Both Aha! administrators and the product team members they support through administration of the tool. What impact would it make? It would allow Aha! administrators to automate actions and notifications that advancement can be m...
0
Future consideration
2
VOTE
Have workspace templates be default for new workspaces
Who would benefit? anyone who administers an aha account What impact would it make? streamlines work, reduces chance of manual error, reduces need to manually verify items How should it work? allow account admins to set what the default workspace ...
0
Future consideration
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
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
© 2024 Aha! Labs Inc.•All rights reserved