RELATED IDEAS
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.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +3
13
MERGED
Allow Aha! Time Tracking support more than minutes for the JIRA integration
Our JIRA instance is configured to use hours to track time. This is not something our DEV team is willing to move away from. Is it possible to configure Aha to respect this configuration and send hours and not minutes so time tracking isn't screwe...
0
Likely to implement
This will help us to reduce the effort towards integration.
We integrate with 2 different instances of Jira which both have admins not willing to change the default units. I have to run a separate process which updates Aha! based on Jira estimates alongside the integration. Very clunky! Please let us configure default units in the integration itself.
We bring the estimates in from Jira, which we track in hours. We can't change the Jira setup without impacting the rest of the business. Can we customize our estimate field to be a formula so we can calculate and display hours by converting those minutes on the Aha side?
Hi, we have the same problem. Our JIRA team is not willing to change the default time unit since this has other implications. It would be great if Aha could be made more flexible (i.e. configure the time units while setting up the JIRA integration). Otherwise it will be very difficult for us to use the capacity planning feature.
Cannot put effort estimates into JIRA without it.
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.
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.
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?
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.
I need it.