Forums

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

Incorrect Remaining Calculation

Cast_Informatica_S_A_ March 8, 2019

When adding multiple worklogs, the remaining generates a value above the estimated, even leaving the remaining blankprint work.jpg

1 answer

0 votes
Petter Gonçalves
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
March 11, 2019

Hello,

Thank you for raising this question.

By default, if you don't set any values to the Remaining Estimate field it will automatically receive the exact same value configured for the Original time estimate (Estimated) field.

As you can see in the screenshot below, I was able to reproduce this behavior in my tests, using the same values you used:

Screen Shot 2019-03-11 at 16.18.58.png

That been said, the incoherent values that you are seen in your issue could only be caused by one of the following actions:

1 - A higher value was added to the Remaining Estimate field during its creation

2 - A higher value was added to the Remaining Estimate field posteriorly, using the edit option or a transition screen (This change is logged under the History tab) 

3 - In the worklog screen, one of the users marked a different option than Adjust automatically and added some extra time to the field Remaining Estimate (This action does not get logged anywhere)

Screen Shot 2019-03-11 at 16.16.55.png

To work around it, we suggest you to manually set the Remaining Estimate with the correct value or set it to 0 if it is already finished.

For more information, you can check the documentation below:

Configuring Time Tracking

Let us know if this information helps! :)

Suggest an answer

Log in or Sign up to answer