All ideas
Sort by:
Trending
Status:
Future consideration
Showing 5650
16
VOTE
Allow bulk moving of reports
Reports often get created at the root level when first starting use of Aha but over time multiple users require different report folders. Then you need to move reports into those new folders. There is no bulk move feature so it is a lot of effort ...
0
Future consideration
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
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
1
VOTE
Work Requests should ignore/remove archived workspaces
What is the challenge? Work requests that were assigned to a workspace, that has later been archived before a workspace owner could respond, cannot currently be closed. These work requests will show a "[Hidden project]" in the Pending response. Wh...
0
Future consideration
1
VOTE
Use a Single Meta/Data Worksheet to Generate Multiple Report Types and Add Directly to Panels Without Pre-Saving
What is the challenge? The current process of creating and managing multiple reports can lead to overcrowded workflows and inefficiencies when building a unified dashboard. Users face difficulties in seamlessly generating multiple reports and orga...
0
Future consideration
1
VOTE
Include integration mapping details in integration reporting
We want to automate the documentation of all of our integration points (integration to Jira). We would like to see not only the integration name, rather we would like to see the specifics field mapping information , direction of integration etc...
0
Future consideration
3
VOTE
Allow customization of field name per-workspace
What is the challenge? Reusing custom fields across workspaces is helpful for governance and consistent reporting. But sometimes teams would like to call that field something else on their layouts. What is the impact? Teams have to modify their fi...
0
Future consideration
5
VOTE
Add delivery risk check for connecting work to strategy
We need to ensure that all of the work we deliver is driving our overall product strategy. Create a new delivery risk indicator that is triggered when a record does not roll up to a larger part of the plan (e.g. feature doesn't have an epic set, e...
0
Future consideration
19
VOTE
Trigger automation from a custom worksheet update
My use case: I've created a worksheet on master features that looks at all features in a master feature and presents the min and max dates. I want the master feature's "Start on" and "Due on" dates to be driven by this worksheet's calculated dates.
1
Future consideration
9
VOTE
Scorecard automated metric should allow you to select other scorecard fields
We have implemented two separate scorecards for feature cost and feature impact. This gives us more flexibility in reporting/filtering based on what-ifs. We would like to combine those two scores in an an overall feature score to use for prioritiz...
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved