Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

originalEstimate reporting incorrect values when originalEstimateSeconds is correct

Austin Isaacs
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 27, 2023

I'm working on a system where a customer submits a request and subtasks are generated based on the request, each with their own time estimate. I want the total estimated time reported on the main task and have been running into issues with the original estimate being days to months off. Looking through the code, time tracking is calculating the originalEstimateSeconds correctly (in the case below 16.25hr) but originalEstimate is reporting 2d 15m. I have the original estimate set to join the times from the subtasks and divide by 60 to convert to minutes.

timetracking":{"originalEstimate":"2d 15m","remainingEstimate":"0m","originalEstimateSeconds":58500,"remainingEstimateSeconds":0}

Any ideas what is going on? Does it have to do with the w/d/h/m format for original estimate not interpreting the time correctly?

1 answer

1 accepted

1 vote
Answer accepted
Tim Perrault
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 27, 2023

Hi @Austin Isaacs 

 

My guess is your Time tracking setting are setup so that there are 8 working hours per day. This means every 8hrs will be converted to 1 day.

 

Time Tracking 

Austin Isaacs
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 27, 2023

Ah! Totally missed that and makes sense. Thanks for your help!!

Like # people like this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events