Account settings
Sort by:
Trending
Status:
Showing 512
10
VOTE
Enable Conversion of Product Workspace to Product Line
In the creation / setup phase of workspaces and product lines, we cannot change the workspace designation to a product line. Instead we have to move the data objects from the existing workspace to other workspaces, then delete the workspace that c...
1
Future consideration
6
VOTE
Restrict workspace type for new workspace set up
We have come across the issue of team members setting up different workspace types in our Business Line. This makes reporting complicated as the status do not line up. There should be a way to restrict workspace types for new workspaces with admin...
0
Future consideration
11
VOTE
Limit Workspace Permissions for User with Product Line Owner Permission
We need an ability to Limit Workspace Permissions for User with Product Line Owner Permission.
Currently "Users with access to product lines also have access to their underlying products."
Use Case:
We have a number of Product Operations Worksp...
1
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
3
VOTE
Improve error messages for background job failures
When background jobs fail we are not able to see what caused the failure. It would be helpful to see which records(s) caused the issue so that the errors can be resolved quickly. Recently saw this with a bulk update job error - the message indicat...
0
Future consideration
4
VOTE
Allow for Create SSO access when sharing notes and whiteboards
As a large organization, SSO is required to access authorized tools. When sharing documents (notes/whiteboards) today with a non-Aha! user in my organization, that user would need to start a free Aha! Create account with a UN/PW or Google SSO. We'...
0
Future consideration
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
5
VOTE
Follow custom workspace line terminology when viewing Roll up to workspace goals
When a workspace line references its parent, the naming of that parent should match the parent level, not the workspace level. By not reflecting the customized terminology we are introducing layers of confusion for the team members who don’t spend...
1
Future consideration
14
VOTE
Active Directory group integration for user authentication
We would like to give visibility (at least read only access) to Aha to a large amount of users (> 1K) in our organization however this is currently not practical as each user needs to be added manually one by one. Even when using SSO you still ...
1
Future consideration
9
VOTE
Guided setup for Capacity Planning for Teams
It would be great if Aha! provided a step-by-step wizard to setup the Capacity Planning for Teams feature, very similar to how the current integration setup wizard functions. As an admin, I am not quite sure the sequence that I need to set up the ...
0
Future consideration