What is the challenge? We have standard automations needed across a majority of the account with a few exceptions. We would like to disable those that we do not want to be used in certain workspaces. What is the impact? 99% of the time we want wor...
Michael Bruner
7 days ago
in Account settings
0
Future consideration
Prevent users from updating fields through bulk edit when set to "read only"
What is the challenge? A set of fields on various records (initiatives, epics and others) are used for financial reporting and should only be editable for a specific set of users. The fields are set as read only in their custom layouts, but can st...
Dale Potter
27 days ago
in Account settings
0
Planning to implement
Ability to configure scope of selection for custom "users field"
What is the challenge? Based on our use case, we need the ability to configure the scope of selection for the custom "users field" What is the impact? Not able to configure the scope of selection. Describe your idea Need ability to configure the s...
Hank Liu
6 months 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
5 months ago
in Account settings
0
Future consideration
User permissions: prevent users from deleting records
We occasionally have situations where data is deleted and then we realize it needs to be recovered. If we notice this within 7 days we can restore the records from the recycle bin, but we would prefer to disable the ability to delete records for s...
Dale Potter
almost 2 years ago
in Account settings
3
Future consideration
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
5 months ago
in Account settings
2
Future consideration
What is the challenge? To comply with company policy, user accounts created more than 90 days ago, and never used, need to be disabled. What is the impact? Non-compliance with company policy Describe your idea Add a filter to the Settings > Acc...
Dale Potter
27 days ago
in Account settings
0
Future consideration
Associate the same custom field to more than one Aha record type
I've seen this mentioned a few places, but the Aha! staff seems to keep deferring to custom tables as being the answer, which isn't the need. When I create a custom field - let's say the customer's name or the segment impacted - I want to add it t...
Karie Kelly
over 3 years ago
in Account settings
6
Future consideration
Support integration actions within workspace template automations
What is the challenge? Currently, integration actions from automation rules can only be created for workspace-level automations. These automations can only be copied but cannot be applied to a workspace template. Currently, workspace templates are...
Terence Osmeña
about 2 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
5 months ago
in Account settings
0
Future consideration