Features
Sort by:
Trending
Status:
Showing 1228
11
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
32
VOTE
Priority limit line on subsequent pages of Prioritization view
Love the new prioritization lines introduced last week. However, they can only be placed on the first page. We have a need to also place them on the subsequent pages, as we have that many features to keep track of. We're hoping to use these to als...
5
Future consideration
11
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...
1
Future consideration
14
VOTE
Add standard Key Results field on the create record view
What is the challenge? The standard Key Results field is available for use in the feature record view but is not available on the create pop-up. What is the impact? Users need to be able to identify the associated Key Results at the create step so...
0
Likely to implement
4
VOTE
Improve Epic (Feature) Prioritization page to allow key results to appear as a column
What is the challenge? Teams today associate key results to Epics (you may call them features) and objectives to Programs (you may call them Programs) but are unable to view their key results as a contextual column in the epic prioritization view....
0
Future consideration
117
VOTE
Updating a feature's dates should automatically adjust dates of features with downstream dependencies
What is the challenge? Managing sequential tasks with fixed date offsets can be cumbersome when date changes aren’t automatically applied to downstream dependencies. Currently, only changes made via drag-and-drop on the Releases Overview/Roadmap p...
11
Planning to implement
13
VOTE
Add Automation Trigger "Is Blank"
What is the challenge? For data quality, we want to notify an Epic/Feature creator when then have forgotten to tie the record to an Initiative, Objective, or Key Result What is the impact? Work that should be tied to these is not visible, monitore...
0
Future consideration
3
VOTE
96
VOTE
Don't remove lane in feature board view once shipped
Currently when you ship a release the lane disappears from the feature board view. It would be great if instead of disappearing all together the lane was simply greyed out or marked as shipped. The feature board view is where we look to see what w...
27
Unlikely to implement
3
VOTE
Update sort logic on Features board when sorting by Start Date or Due Date
What is the challenge? Currently, on the Features board, if you sort features or epics within a release on the Start Date or Due Date, it is sorting the records with the earliest dates at the bottom. What is the impact? The records that will be st...
0
Likely to implement
© 2025 Aha! Labs Inc.•All rights reserved