Skip to Main Content
Status Shipped
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. 

  • ADMIN RESPONSE
    Feb 23, 2024

    It's now possible to configure how estimates are sent to the native "Effort" field in Azure DevOps.

  • Attach files
  • Michael F
    Reply
    |
    Feb 26, 2024

    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!

  • Ruth Gardiner
    Reply
    |
    Feb 26, 2024

    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

  • Ruth Gardiner
    Reply
    |
    Aug 4, 2023

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

  • Guest
    Reply
    |
    Jun 15, 2023

    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.

  • Fabio Zavagnini
    Reply
    |
    Feb 2, 2023

    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.

  • Michael Scholze
    Reply
    |
    Jan 18, 2023

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

  • Gillian Hoyle
    Reply
    |
    Sep 2, 2022

    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.

  • Armen S
    Reply
    |
    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
    Reply
    |
    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
    Reply
    |
    Mar 4, 2021

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

  • Dave Ball
    Reply
    |
    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
    Reply
    |
    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
    Reply
    |
    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
    Reply
    |
    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.

  • +2
1 MERGED

Integration with ADO - Estimates & Effort logged

Merged
With integration to ADO, the estimates used in Aha! convert to minutes in ADO. If effort is logged in ADO it needs to be logged in minutes in order to translate across to hours/ days in Aha - this is not intuitive to the user. Time should be mappe...
Ruth Gardiner 10 months ago in Integrations 0 Shipped
1 MERGED

Provide ability to track hours that aren't converted into days

Merged
We track our estimates and log time in hour/quarter hour increments - 8 hour work days aren't meaningful to our team. It would be cool if you could give flexibility here so that if I track 24 hours, I have a choice in the workspace as to whether t...
Guest over 1 year ago in Capacity planning 0 Shipped