Skip to Main Content

Share your product feedback

Status Shipped
Categories Capacity planning
Created by Ashley Powell
Created on May 18, 2020

Ability to use days and weeks in advanced estimates

We are using the Enterprise + version with team capacity, scenario planning, and advanced estimates. We need the advanced estimates to allow for days and weeks estimates instead of only hours. Meaning, I can enter 2 days and the system can translate that into hours if needed. This would make the scenario planning feature much easier to use and consume.

Release time frame 1 month
  • ADMIN RESPONSE
    Oct 5, 2022

    Individual and team capacity planning just got even better. Visualize the most recent estimate for both individuals and teams to manage workloads efficiently — all in one report.

    This includes the ability to set how time is displayed in advanced estimates. You can edit your time format by going to Settings > Account > Capacity planning > Scenarios > Selecting your scenario and adjusting the "Show time in" setting.

  • Attach files
  • Jay Jeyaindran
    Reply
    |
    Aug 15, 2022

    While tackling the aforementioned gap with estimates, please consider displaying capacity reports as a weekly plan not just in months.

  • Gene Lewin
    Reply
    |
    May 16, 2022

    I strongly support this request ... and in fact, i don't think you should only support the data entry of days and/or weeks, but it should also be supported in the UI and in the capacity report as an optional scale at which to see time values. Especially for initiatives that represent large pieces of work that could take a team of 10-20 engineers 3-6 months to complete, seeing estimates and capacities in the thousands of hours lacks any real intuitive context.

  • Cyril Bousquet
    Reply
    |
    Jul 16, 2020

    Our teams are all confused that this portion of the product do not use the same input logic than the rest of the estimates field in Aha!

    Also, if they enter 5d, the system will silently consider it is 5 hours and ignore the "d", creating even more issues as users are expecting the behavior to be consistent everywhere.

  • +5