Features
Sort by:
Trending
Status:
Future consideration
Showing 592
178
VOTE
8
VOTE
Prioritization report should support displaying strategy fields with multiple records (goals, objectives, key results)
What is the challenge? The prioritization report cannot display strategy fields tied to multiple records (like goals, objectives, and key results). What is the impact? Goals, objectives and key results are vital reference points when determining a...
0
Future consideration
10
VOTE
Support "same as" automations for choice lists
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 choice lists across records. What is the impact? We often plan our work by compon...
0
Future consideration
7
VOTE
Specify which fields will and will not be copied when copying a Feature
What is the challenge? When a Feature is copied, any field that is filled in will automatically be copied over to the newly created Feature What is the impact? Although most of time this is ok, some fields are Read-Only and therefore cannot be cle...
1
Future consideration
1
VOTE
216
VOTE
Custom swimlanes for features and workflow boards
Currently swimlanes are by owner which is helpful when micro-managing resources however we group resources into teams and focus features on given teams. It would be nice to support custom fields/groupings on the swimlanes so I could choose how i w...
25
Future consideration
2
VOTE
Search all release and record data on the features > board view
What is the challenge? Today, when searching on the features > board view Aha! only applies search to what is on the screen. When parking lots are being used and they have not all loaded yet they are not included in the original search results....
0
Future consideration
1
VOTE
Automatic dates calculation for Features based on requirements
Currently requirements don't have a native date range, so the date range of features can't be calculated from their requirements. For teams that use requirements with dates, this misses the opportunity to streamline the planning process.
0
Future consideration
177
VOTE
5
VOTE
Option to not copy Requirements when Copying a Feature
What is the challenge? We have begun tracking high-level Requirement information in Aha! and have seen that when we copy a feature the stories are also copied. This may be appropriate in some cases, but not all. What is the impact? This may create...
1
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved