Coming soon: We are introducing a fresh new look for record drawer and details pages on September 30, 2020. This article describes the current experience. Preview the upcoming improvements in your account now so you can get familiar with the new way of working in Aha!
If you are seeing estimates from Aha! sent to Jira with inflated values, this is because your Jira time tracking unit is set to a value other than minutes. Aha! sends all estimates to Jira in minutes. This is regardless of how the estimate is specified in the Aha! user interface where the time can be displayed as m (minutes), h (hours), d (days), w (weeks), or m (months). As a result, the default unit for time tracking in Jira must also be set to minute. If it is not, the estimate reflected in Jira will represent the wrong unit of time and be heavily inflated as a result.
You can check the Jira time tracking settings by logging in as a user with Jira Administrator global permissions. Go to the Jira Administration settings and look for Issue Features which can be found under either the System or Issues sub-menus. Once you have found Issue Features, open the Time Tracking page to view the settings.
Example when default unit of time tracking is something other than minute
The following example illustrates how an Aha! time estimate is converted to Jira when the default unit for time tracking is changed from minute to day. This is the Aha! feature showing a time estimate of 1d.
Upon initiating the update to Jira, the time estimated is converted to the following:
The number Aha! passed to Jira was 480 minutes (1 day = 8 hours * 60 minutes/hour =480 minutes). With the Jira default unit for time tracking set to day, the Jira estimate was converted to 480 days instead of minutes. The 480 days was then divided by 5 days/week which resulted in 96 weeks.
Be sure to set the Jira default unit for time tracking to minute to avoid this type of conversion issue.