Account settings
Sort by:
Trending
Status:
Future consideration
Showing 648
3
VOTE
Allow custom links within help (?) menu
What is the challenge? For large scale implementations it requires a blend of general Aha! documentation and internally created documentation to provide users with a complete picture. In app we are limited to only Aha! resources What is the impact...
0
Future consideration
2
VOTE
Automation that pulls parent information when child field created
What is the challenge? Currently passing fields from parents to children (epic to feature or initiative to epic) can only be done when the parent is updated. This means when you create an epic under an initiative the fields are not automatically u...
0
Future consideration
4
VOTE
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...
0
Planning to implement
20
VOTE
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...
0
Future consideration
56
VOTE
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...
3
Future consideration
13
VOTE
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...
0
Future consideration
11
VOTE
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...
2
Future consideration
92
VOTE
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...
6
Future consideration
60
VOTE
10
VOTE
Quick navigation to settings pages by name
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...
0
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved