Account settings
Sort by:
Trending
Status:
Showing 640
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
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
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
9
VOTE
2
VOTE
Consider inherited values when copying workspace settings for workspace templates
Who would benefit? Any users creating a workspace template from an existing workspace. What impact would it make? Today if a workspace template is created from an existing workspace, Aha! does not look at inherited settings. For example, at the wo...
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
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
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
© 2024 Aha! Labs Inc.•All rights reserved