Features
Sort by:
Trending
Status:
Showing 1236
1
VOTE
Status color legend on the features board
Feature cards on the features board are colored based on their status. When stakeholders, such as leadership, are browsing the features board, they may not know how the statuses correspond to the color of the feature cards. It would be helpful to ...
0
Future consideration
1
VOTE
Feature dependencies based on Requirement dependencies
Our engineers have a good view into Jira issue dependencies. Our business process enforces that all Jira issues will belong to a Jira Epic. We then map those Jira Epics into Aha Features. We would like the Jira Story/Task/Bug dependencies to be ro...
0
Future consideration
2
VOTE
Assume one predefined tag is needed
In tag fields, trigger the list view of tags only after clicking within the field. If I need another tag, let me click the field again. Currently, the behavior assumes that if I choose one tag, I'll probably want more. I don't, but I have to click...
0
Unlikely to implement
1
VOTE
Ability to NOT include the Description Field for the Create Template
I am using the new Template capability to provide guidance for populating Initiatives / Capabilities (Features) via a standard format. Unfortunately, to use this feature I am required to include the Description field in the Create Layout. This res...
0
Future consideration
1
VOTE
Remove Epic as mandatory field while a feature is created.
To create a feature I must link it to an Epic before I can save it, but then I can go back and unlink the Epic. If I can go back and unlink the Epic, then why not allow the user to create a feature without linking it to a specific Epic from the be...
0
Already exists
2
VOTE
Change the size of the created/assigned to user image on feature cards
The ability to add a user image onto feature cards is excellent but, for large organisations with many users, it can be difficult to differentiate between users when the image is small and multiple people may look similar.
It would be great if the...
0
Unlikely to implement
2
VOTE
1
VOTE
Automatically sort features in a release
As we plan our releases, we order features in those releases by their Aha! score. The "Rerank features by" option makes it simple enough to ensure records are in the correct order during planning. As a release plan evolves though, it becomes chall...
0
Future consideration
2
VOTE
Ability to add specific field from elements like feature (currently only defaults to feature name for example)
When adding other entities like scenarios to a feature, it is useful if we can associate a feature number rather than the feature name which is the default field when you use the many to many table
1
Already exists
1
VOTE
© 2025 Aha! Labs Inc.•All rights reserved