Features
Sort by:
Trending
Filter by:
Status
Showing 1180 of 9712
36
VOTE
Aha should delete the integration link when receiving a delete trigger from a webhook
We have Aha linked to JIRA. When we delete an issue in JIRA, this triggers our Webhook to send a message to Aha. I understand and agree that this should not cause Aha to delete the Feature connected to it for security reasons. But I would expect A...
8
Future consideration
24
VOTE
Default view of Feature / Idea list for team members
You can currently customize your Feature / Idea list and save it. But there's no ability to set this customized view as the default for all team members. This would ensure everyone is looking at the same data with appropriate filters configured an...
0
Future consideration
29
VOTE
Ability to tie color feature color to other fields
Status doesn't help to organize we would rather color code based on priority. We created a custom field for this and are eventually planning to use scorecards. We would like the ability to tie the color of the feature card to other fields beyond s...
15
Future consideration
9
VOTE
Roll up feature delivery risks to parent epics
It would be helpful to have an option to configure roll up for delivery risks. For example, if a feature is at risk, we can reasonably assume the parent epic is also at risk, so we should display the flag there as well- with a link to the relevant...
0
Future consideration
37
VOTE
Allow custom labels for scorecard metrics
It would be great if, instead of just showing the underlying value, the scorecard metrics could use abstract labels... for example, for an 'effort' metric we might use t-shirt sizes such as "Small", "Medium", "Large" and "X-Large" behind the scene...
6
Future consideration
13
VOTE
30
VOTE
Inherit Field Values from Feature to Requirement
We have a field that exists on both our Features and Requirements, and that custom field is being used in our JIRA integration. When creating a new requirement, it would be great to have the field auto-populate from what is specified in that field...
7
Future consideration
32
VOTE
1
VOTE
"Type" field for Features shuold be optional
What is the challenge?
The “Type” field is mandatory for Features but we don't have a use case for the field.
What is the impact?
The "Type" field is creating unnecessary noise on the screen every time a Feature request is submitted.
D...
0
Future consideration
27
VOTE
Allow setting the Rank of an Initiative from the Initiative detail view
We rely a lot on the rank of Initiatives in order to determine the priority of Initiatives/Epics across the business. Unfortunately, the only way to re-rank Initiatives is by dragging and dropping in the Initiatives list.
it would be helpful to ha...
3
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved