RELATED IDEAS
Ability to filter and sort on estimates field
Estimations is an important factor in our prioritization and decision process and a weak point right now in Aha!
Right now Aha! surprisingly does not allow to build a simple list report that could show all initiatives/epics/features with no estimates entered which basically keeps us from using this information properly.
It seems like estimates are stored in minutes by Aha!, so even by just giving the ability to consider this information as a regular number value, that would be a good start.
Exporting to Excel to accomplish this very simple task is time consuming and remove the flexibility of working with other filters on our reports (workspace, theme, etc.)
We were also hoping to find through reports any epic that has or has no estimates while some features underneath may or may not, to ensure our product managers had been consistent when entering their estimates at one level or the other of our hierarchy.
-
ADMIN RESPONSESep 30, 2024
In November 2022, we added filtering and sorting support for detailed and actual estimates. We recently expanded this to initial estimates as well, which should cover all use cases.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +7
1
MERGED
Make Original Estimate a Sortable Field
Currently, I am unable to produce a report in Aha in which Features are sorted in descending order based on the Original Estimate. This is frustrating as leadership would like to be able to quickly see the Features that are the biggest in a release.
0
Shipped
© 2024 Aha! Labs Inc.•All rights reserved
We have now expanded this functionality to initial estimates.
This a huge gap for us. As we're laying out our future releases and budget planning not being able to filter on this field limits our functionality and use of Aha. Seems like a simple fix to add this in as another filter.
Honestly shocked it's not there currently, why wouldn't you have all data points as filters?
You can now filter, sort, and run calculations on the detailed estimate and logged effort fields.
This is a big gap for us as well ... in addition to being able to filter on records that are missing esimates (and I definitely agree this is very important for us), it would be great to be able to export actual estimates in a list or pivot report to do additional math / analysis on. I certainly understand that there is complexity in multiple teams, time slices, and estimation scenarios being represented in the estimates field, but even having it as a comma-separated string, JSON string, etc. that in some way would allow me to get at the data would be hugely useful.
Sorting and filtering by estimates as a data column in a list report is extremely valuable during routine house-keeping to ensure features/stories/requirements have the required estimates entered.
Our use case would be mostly to be able to determine which Features haven't been estimated. Also, sorting by Estimate would be useful.
The use case on our side would be to analyze the features done (or planned) in a release (or multiple releases) but excluding the really small features. Those really small features (the ones that are only 1 or 2 story points) only add "noise" to the report and make it harder to analyze...
I'll add that I need further filtering for stories like:
As a product manager, I need to be able to visualize my top 10 highest effort stories plotted against their Score in a scatter chart, so that I can identify any estimate/impact misalignments and decide if adjustments are worth exploring.
This would be great for our organization as well. Not only do we need to determine if estimates were entered at the initiative level, I believe there's valuable information that can be pulled if we had the ability to filter and sort. For instance, we can see which initiatives are taking up a lot of resources. Being able to perform calculations on these fields would be great if we wanted to create a dashboard comparing/contrasting these very estimates - what % of resources does this initiative take up versus another?
This would be so helpful in enabling me to prioritize work which has already been estimated! It's how we know how many features the dev team can work on in a sprint, and enables us to see how far ahead we are in our documentation.