Delivery Risks - Ability to Inherent to Child Workspace
What is the challenge? If one product line (parent workspace) wants to implement Delivery Risks, we would need to individually go through the settings on each child workspace to configure. What is the impact? It is very time consuming for large pr...
Manny Pannu
over 1 year ago
in Account settings
2
Future consideration
What is the challenge?
When you have multiple approvers depending on different conditions everyone received the same message
What is the impact?
Multiple users receive approval requests that might not apply to them. It causes confusion and...
Edgar Holguin
7 months ago
in Account settings
0
Future consideration
When working with Aha! customers, one part that slows down users as they set up their account is figuring out how to navigate through to the page they need. Let's say I am helping a customer add a custom layout and statuses to their ideas and idea...
Max Robbins
over 1 year ago
in Account settings
0
Future consideration
Sort the list of release templates to appear in alphabetical order or set manually
What is the challenge? Large lists of release templates can be difficult to manage and sort. Not having a set list and being able to sort the order alphabetically or manually increases the time it takes to find a release template. This is also the...
Terence Osmeña
over 1 year ago
in Account settings
0
Future consideration
Only Allow Users to Create Workspaces under the Workspace Lines They Own
What is the challenge?
Users who have owner licenses can create workspaces or workspace lines not only under the workspace lines they own, but also other workspace lines they do not own. As admins of the Aha! account, we want to limit user's abi...
Allow to define the scope of tags/choice list custom field values (account vs. workspace)
It should be possible to define whether the values of choice list and tags custom fields (predefined or editable) are shared at account level (current behavior) or limited to workspace level such that workspaces can share a configuration but have ...
Thierry Loones
almost 3 years ago
in Account settings
2
Future consideration
It would be very useful to be able to set read-only permissions for some fields (either standard or custom fields) based on permissions, or - even better - permission groups. In fact we have some fields on Features and Ideas that should be maintai...
Nicola Rolando
over 2 years ago
in Account settings
0
Likely to implement
Amount of changes made by a user when Account Level permissions
What is the challenge? Business Problem to Solve: Utilization report: We would like to know who is utilizing the Aha Account Level? How can we manage the amount of changes made by a user when Account Level permissions have been granted? License co...
Mike Jacobson
almost 2 years ago
in Account settings
1
Future consideration
Allow admins without a paid license to manage workspace hierarchy
What is the challenge? Some teams have central admins who do not manage work in Aha!, just help configure it for end users. These users have full admin permissions and help administrate the account. This is fine for most settings, but if a customi...
Max Robbins
10 months ago
in Account settings
0
Future consideration
Delete in Aha restricted to Admins expand to Custom roles
What is the challenge? Recently Aha! implemented a feature for restricting delete but once enabled only Admins can delete records. What is the impact? We have some power users who required delete permissions but do not need other admin priviliges ...
Shiv Shankar Vedharajan
12 months ago
in Account settings
0
Future consideration