Customize hours in a day for capacity estimates

It would be nice if I could customize what a day means in actual hours so that when our work integrates with JIRA it doesn't blow up the hours the wrong way.

For example - a day for us means 10 hours of work. However, I can't customize that so when a day is sent across from Aha to JIRA it immediately logs 24 hours, therefore causing my engineers to see bizarre estimates on their side. I'd love to be able to control this. It's causing a lot of angst among the team.

  • Mandy Long
  • Mar 16 2015
  • Likely to implement
Release time frame
  • Attach files
  • Sandro Boçon commented
    August 05, 2015 14:57

    Even better if could be able to estimate hours per day capacity for each project!

  • Nick Kewney commented
    September 27, 2016 09:40

    Setting the number of productive hours in an engineer's day would be a huge benefit

  • Nicola Hills commented
    October 17, 2016 16:34

    Agreed, we also find we are needing this because Aha! automatically converts from days to hours and vice versa in certain circumstances and realistically with meetings, and various other general things that go on in a day not every team gets 8 productive hours.

  • Jerrold Emery commented
    April 12, 2017 21:50

    Couldn't agree more. Much our capacity planning is done in hours and would like the ability to view the hours on a given feature rather than viewing the days. Providing an option for the resolution would be extremely helpful.

  • David Pidsley commented
    October 09, 2017 11:19

    Important for accurate reporting on effort and work done.

  • Guest commented
    06 Aug 16:35

    The configuration for productive hours in a day should equal the flexibility shared in applications that Aha integrates with.  When your estimations are done in Jira, and in Jira working days are considered to have 6 hours of true productivity allowing for meetings/breaks - there is conflict when you then run a Jira integration through to Aha! as an 8 day task in Jira is synced as a 6 day task in Aha.  This in turn leads to over-optimistic planning and forecasting in Aha, (perceiving days to be productively longer and features to be delivered sooner), which in turn leads to disappointment and perceived 'delays' in feature delivery.