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. 

  • Guest
  • Feb 20 2019
  • Future consideration
Release time frame
  • Attach files
  • Kalyndra Craven commented
    15 Oct, 2019 03:50pm

    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.