All ideas
Sort by:
Trending
Status:
Future consideration
Showing 5902
21
VOTE
To be able to easily move the features upwards in the User Story Map
When I work with the User Story Map (great tool by the way), I sometimes make mistakes. When that happens all my features ger scattered out in map height wise. Then it is a REALLY tedious work to collect them at the top level.
There should be a w...
2
Future consideration
6
VOTE
Allow detailed estimates to affect capacity plans without needing to assign a team member to the Aha record
We do all of our assigning in Jira, and in fact only sync epics between Aha and Jira, so adding an assignee in Aha doesn't make sense for us as you don't assign a dev to an epic, even in Jira. We assign to the task/sub-task. Having to add an assig...
0
Future consideration
21
VOTE
Add the ability to archive notes
Our marketing workspace has been around for a few years, and it has quite a few notes that are no longer relevant. Currently we nest notes under an "Archive" note, but that is not an elegant solution because we have to move them one at a time. It ...
0
Future consideration
36
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
1
VOTE
Automatically populate the approval group field when a workflow approval is created
What is the challenge? Previously, when a workflow approval was created, the members of an approval group were populated in the "Assigned to" field of the to-do. Recently, the "Approval group" field was added to workflow approvals. This field, how...
0
Future consideration
1
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
1
VOTE
Custom field variables in document
What is the challenge? Document metadata that needs to be part of the document content must be manually entered and updated. For example, a document's last modified date or a document's custom field reflecting a feature's lifecycle state (e.g., be...
0
Future consideration
2
VOTE
When creating reports and roadmaps, the ability to share the filters between reports
What is the challenge? Maintaining the same filters across multiple views which use need to show the same data but in different ways What is the impact? Time saving when maintaining reports and roadmaps, consistency of presentation and accuracy of...
0
Future consideration
3
VOTE
Reduce real estate consumption in the header section
Who would benefit? All users of Aha What impact would it make? It would show more of what matters on the screen, increasing legibility and user productivity. It would also bring the relevant content higher up on the screen. How should it work? The...
0
Future consideration
10
VOTE
Allow nesting of rollup releases
Rollup releases are very useful in organizations with complex and nested product lines and products. A top level product may have a V2.0 which is a rollup of three subsystems, a perfect use case of a rollup release. If each of the subsystems, in t...
3
Future consideration