Skip to Main Content
Status Likely to implement
Created by Guest
Created on Feb 20, 2019

Configurable unit of time for Estimation field

We're using Aha with Azure DevOps integration. We’ve mapped the Estimate field in Aha with an estimate field in Azure DevOps.

Our estimation process is basically as follows:

* Product Manager creates Feature in Aha

* Product Manager send RFC into Azure DevOps – state = “Estimation needed”

* Development team reviews the Feature and provide an estimate by updating estimate field and set the state to “Estimation Completed”

The problem we are having is that development team provide their estimate in days but this manifests in minutes in Aha.

We'd like the ability to configure the base time units in Aha (so we are able to set it to days) – entering our estimates in minutes in VSTS is not really a workable solution.

At this point, I am planning to add a custom field in Azure Devops (i.e. Estimation (mins)) and configure it to auto populate when the Estimation field is set. I'll then map the Estimation (mins) field to the estimation field in Aha. I'll post an update with how I get on with this hack. 

  • Attach files
  • Armen S
    Jul 26, 2021

    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.

  • Guest
    Jul 9, 2021

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

  • Guest
    Mar 4, 2021

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

  • Dave Ball
    Aug 10, 2020

    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.

  • CJ Jacobs
    Jul 27, 2020

    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.

  • Rick Gouse
    Jun 16, 2020

    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.

  • Kalyndra Craven
    Oct 15, 2019

    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.