Features
Sort by:
Trending
Status:
Likely to implement
Showing 1191
43
VOTE
Customize Default Fields on Records - Renaming and Adding Descriptions
This applies to all records with required default fields, not just Features: I would like to be able to customize fields that are default/'out of the box' fields on records. Specifically, I would like to be able to rename and add descriptions (hov...
11
Future consideration
1
VOTE
Suggested Development timeframe
What is the challenge? Getting estimates from people is a slow process, they are rarely correct and are often influenced by politics or hidden agendas. What is the impact? Plans are rarely accurate, estimates are padded to make people feel safe. O...
0
Likely to implement
2
VOTE
Support "same as" automations for tags
What is the challenge? Automations currently make it possible to pass values from one record to another, such as users and dates. We need the ability to set the same tags across records. What is the impact? We often capture a key customer's name o...
0
Future consideration
86
VOTE
Allow the creation of to-dos in a custom "create new feature" template
You just launched a feature whereby you can create a list of to-dos in a feature, and then when you copy that feature the to-dos are copied over with them. However this is a very clumsy way to have to create new features every single time. I need ...
17
Future consideration
2
VOTE
Enhance the advanced functions in Aha! to list unique values from a string field
What is the challenge? The primary challenge we are facing is the presence of duplicate values in the lists generated by our custom field formula. We have a custom field in our feature layout that pulls values from a specific column in a related c...
0
Future consideration
39
VOTE
Inherit field values from Epics to Features
By default, have the Epic based data values copied over to the Feature data fields when the user creates a new feature from an epic card. This eliminates the need for re-entering and possibly inconsistent values for the same fields. If inherited f...
7
Future consideration
75
VOTE
Unique field layout based on feature type
As we continue to expand our use of Aha, one issue that has come up is that within a given product, there are different types of work/requirements that require different types of information. We're adding more and more custom fields, and it's star...
8
Future consideration
1
VOTE
ICE scoring is a cross-functional team exercise
What is the challenge? Write access for just ICE scoring opens up to much access, but using a spreadsheet and then transferring the data is duplicative work What is the impact? Duplicating work Describe your idea Provide a role access that is Read...
0
Future consideration
2
VOTE
Allow Product value scorecard and custom scorecards to be read-only on Prioritization view
What is the challenge? Currently, it is not possible to make the Product value scorecard or a custom scorecards read-only on the Prioritization view. What is the impact? This prevents you from being able to lock-in a scorecard because even if you ...
0
Future consideration
23
VOTE
© 2024 Aha! Labs Inc.•All rights reserved