Configurable unit of time for Estimation field

This made my year. Team has not liked estimating and tracking in minutes, so I was very excited to inform them we can use hours. However, the excitement was short lived after I realized work complete (actuals) is non-configurable... I would really like to understand why, unless this was purely an oversight. Estimates, remaining in days, hours, minutes, but actuals minutes only? For context, we enter initial estimates in Aha! during requirements, which don't make their way into ADO. In design, the team works in ADO and enters their detailed estimates, which one-way back into ADO for visibility. They then enter their actuals as they work dev in ADO, which also flows one-way to Aha!

thanks, this is great to see shipped. Is there a reason that there isn't an option to configure the a actual effort also? This is still pulling through as minutes. thanks

adding another vote for this. Is there any timeframe on when we can expect this to be implemented?

Adding another vote that cant believe 3 years later this hasnt been implemented. No one estimates in minutes, why would the system default to this unit? And expecting users to implement their own workarounds is a terrible user experience. Either have it configurable or at least update the default to something useful like hours or days.

Adding one more vote to this. I'm surprised this is not yet implemented. It is causing great hindrance to our planning process and basically defeats in part the purpose for us using this tool if the integration is not properly done. The whole point was for us to be able to plan AND Monitor the operations through this tool and now we can't. We would really appreciate this to be taken with a higher priority.

Adding our vote here. Use Case (Problem) is exactly as described above - we are not planning in minutes.

Hiya, A bit surprised that this isn't something that can be done. Over the years of running agile teams i have never estimated in minutes - it is just too granular. With an integration from ADO to Aha where ADO works in hours it is coming into Aha in Min meaning that all the capacity planning is out.

Either need the ability to put a conversion into the estimate box to convert from Min to the required hours/days etc OR define that filed in the capacity admin controls and during the integration to state what the supplied numbers will be input/exported as.

Surprised this hasn't been implemented yet after over 2 years. I've never heard of any scrum team or framework ever recommend estimating effort in minutes... please don't be lazy and fix this so we can actually do proper capacity planning.

Configuration would surely help, we have development teams estimating in hours and teams using Story Points (it is agile and scrum isn't it). both using Effort, Original Estimate for this purpose ...

Why minutes? Unit conversion should have been accommodated. Useless as it...

Surely sending the Original Estimate which is days or hours and then converting to minutes in ADO should be treated as a bug as its just not useable as minutes.

I would like to change the default time tracking unit of days to hours in Aha. This is for Capex monthly time tracking. Days require an extra conversion step and no other department works in days.

Same issue here. A number value in TFS/DevOps comes over as minutes, but is also converted to days when the minutes value is a factor of I'd argue that there should be a setting in the field mapping to allow for conversion for any mapped field. In this case take the value coming inbound from TFS/DevOps and enable the site to do whatever conversion they want. This will allow sites to also get around the fact that minutes to days conversion are also hard-coded in Aha to an 8 hour day. In this case, a value of 480 coming across form DevOps is calculated to 1 day in Aha (60 X 8). When the number is 540 from DevOps, Aha calculates to 1 Day, 1 Hour. If our site works with 9 hour days, I would want the 540 value calculated to 1 day.

We need the ability to set this on completed work as well.  We have certain tasks that we track in Aha! but that need to be accounted for in ADO, so we read the completed work into ADO.  Reading in minutes requires an extra step to convert to hours in ADO to match the rest of the team capacity.