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 be 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.

  • Guest
  • Jan 14 2016
  • Likely to implement
Release time frame
  • Attach files
  • Daniel Rice commented
    October 29, 2018 09:16

    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.

  • Guest commented
    November 08, 2018 16:56

    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. 

  • Guest commented
    November 08, 2018 17:01

    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.   

  • Guest commented
    November 08, 2018 17:24

    Please note additional issue related to this topic; - Round report sums to days, weeks, etc.