RELATED IDEAS
Choose unit to display effort values (such as estimates) in the pivot table
If a feature or requirement has an estimate of 5 days, then the corresponding estimate will count as 40 hours in the pivot table (for example when the requirement's estimated effort is summed as the cell value). This can result in figures that are less practical to work with, especially when aggregating figures up to the initiative or release level.
It would be better if it was possible to choose the unit, such as days or months.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +4
4
MERGED
Display estimations as days in pivot table
Field Feature Original Estimate is populated with number of days value. When presenting features in a pivot table and summing up the values in Feature Original Estimate the result is presented in hours.
My immediate request would be to display th...
0
Future consideration
6
MERGED
Ability to change value format in reports
I'm often wanting to track how much work is being logged, especially compared to how much work was originally estimated. In the reports, the work defaults to showing in hours. It's not as convenient to compare. See screenshots. It would be great i...
1
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved
Would be great to have the initial estimate visualised in all analytics tables so. In my opinion the effort should be either:
An option to choose/configure the visualised effort time (converted from the estimate that is)
Take the same unit as used in the release (e.g. story points, or mandays)
I just made this idea to be merged with this https://big.ideas.aha.io/ideas/A-I-13290
I really don't understand, as a software developer, why is this here since 2016! This is a huge shock for me.
We're hoping to replace an excel process for Product Increment planning with a process in Aha, but since we're currently budgeting and estimating in days rather than complexity, having to use hours makes this much harder to work with (especially since we don't plan using an 8 hour work day - we assume more like 5 hours in a working day to compensate for various meetings etc). It would be much more useful if we could choose the unit to display the totals in (in our case days).
Having days displayed in hours in meaningless to many viewers of dashboards and shared reports. It's a shame that we are forced to ignore the great Aha! functionality because of this and revert to annoying spreadsheets. Please consider prioritizing this
Our capacity planning is in days so we would like to see the estimates in days in the pivot table.
I would love to see weeks as an option for capacity planning. We are currently using a custom field to accomplish this.
Please note additional issue related to this topic; https://big.ideas.aha.io/ideas/APP-I-6688 - Round report sums to days, weeks, etc.
One point of clarification is that our Estimates are established in the system as 'Story Points' - not days & certainly not hours. So, we would be looking for the Aha! Pivot Report to sum these estimates and present them back as 'Story Points', not days or hours.
Aha! Reports should have standards that present data as data was entered into the system. We enter estimates in Aha! as story points and in the following scenario Aha! total's them as hours - this is not acceptable!
Background as explained by Aha! Support; When time estimates are summed in Pivot reports (like we did in your attached screenshot) they are always summed as hours as a common denominator.
We would use the pivot to compare Release Capacity vs Estimated Effort, split out by initiative - today the Capacity appears in days and the Estimated Effort cells and totals in hours. The pivot feature seems ostensibly a really useful feature but not usable until you can compare all the numbers directly. I would need them all in days, for instance.