JIRA: Detect default unit of time tracking

Aha! relies on time tracking in JIRA being set to the default value of minutes. If the value in JIRA has been altered to anything else, it throws time tracking estimates off.

As of the 6.4.x version of the JIRA REST API a GET is available that returns information on optional JIRA features including the full configuration details of time tracking.

Aha! should utilize this to detect the default value and adjust estimates according to what the JIRA instance has configured as the time tracking value.

  • Danny Archer
  • Sep 9 2015
  • Future consideration
Release time frame
  • Attach files
  • Debbie Andrews commented
    September 09, 2015 17:11

    I need it.

  • Josh Glasser commented
    September 10, 2015 22:32

    If users aren't running 6.4.x, even having a setting in the JIRA integration to allow the Aha Admin to specify the unit in AHA is a workaround.

  • Marcin Mikołajczak commented
    September 21, 2015 06:09

    Or maybe it is technically possible to pass a unit (hours, minutes) in the API call, so that JIRA will not try guessing baesd on the setting?

  • Michal Anderson commented
    October 23, 2015 15:38

    That might explain why when I set a JIRA issue to have a 5h estimate I get 300h back from JIRA sometimes because they're not speaking the same language for estimates.  

  • Aurélie Valery commented
    June 02, 2016 14:08

    This would be very useful for my organisation. Because of this limitation, we had to change the default unit for time tracking to minutes in JIRA whereas it was hours from the beginning and teams were used to that. That's very annoying when everything you log is hours. And it's difficult to explain that it is necessary for Aha integration, we would expect Aha to be able to adapt to this configuration.

  • Daniel Rice commented
    November 15, 2018 17:11

    Cannot put effort estimates into JIRA without it.