Features
Sort by:
Trending
Status:
Likely to implement
Showing 1209
1
VOTE
3
VOTE
Bulk load a list of requirements or To Do assignments
What is the challenge? Have long lists of requirements or To Dos to add to a feature card or project; including the assigned person, requirement name, description, and the due date. What is the impact? Save data entry time for project management D...
0
Future consideration
40
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
27
VOTE
7
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
4
VOTE
Trigger automations from an automated delivery risk flag
What is the challenge? When an automated delivery risk is flagged, I want to then enact an automation to trigger notifications and todos to key team members to address the risk. Today, automations only support the manual delivery risk flag. What i...
0
Future consideration
76
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
7
VOTE
Features workflow board - do not default group by assignee
What is the challenge? My account has hundreds of users. Every time I go to the workflow board, it is grouped by assignee and this is not helpful since I am never looking at this work across all my users (if I ever do, it's just a subset of users ...
2
Future consideration
2
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
1
VOTE
When converting a requirement to a feature, if the original feature is in a shipped release, place the converted requirement in an unshipped release.
What is the challenge? I needed to break out a requirement in a feature that was already shipped (as was its release). However, when I converted the feature, it placed it in the shipped release. What is the impact? This new feature could have been...
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved