Features
Sort by:
Recent
Status:
Showing 1209
2
VOTE
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
2
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
1
VOTE
Support types on requirements like we do on features
What is the challenge? We have many types of requirements and today it is hard to quickly see the difference between them or report on the number by type. What is the impact? Less efficiency and consistency. We use a workaround of placing emojis i...
0
Future consideration
1
VOTE
Use AI to reference my personas and let me know what their opinions are on the features I am working on
What is the challenge? Creating personas is a really great way to help me think about my customers and their needs. Over time however it's hard to keep all that information in my head as I am writing new features or prioritising them. We also do a...
0
Future consideration
0
VOTE
1
VOTE
2
VOTE
Allow me to control what fields display in the Subfeature/requirement/story and To-Dos tabs
What is the challenge? When running calls or providing status updates, I appreciate having a condensed view of Subfeatures or To-Dos and being able to update the status through a drop-down in the same view. Sometimes, there are two or three additi...
0
Future consideration
9
VOTE
Do not automatically create record links when records are mentioned
What is the challenge? Users capture important details about an epic or feature in the description of the record, which is a note-type field. In some cases, the user needs to mention another record and does so using the "#" mention. Today, the men...
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