Tempo Timesheets update Time Remaining wrongly

[Pavel Kovařík]

Hello, 

does anyone have a problem with Tempo Timesheets overwriting the Remaining estimate wrongly?

For example: 

Where Original Estimate was 4h, but after logging 1h 30m of work, Tempo changed remaining estimate to 6h 30m. 

[Marta Perez]

Hello @Pavel Kovařík , 

Were you able to get help from Tempo by creating an issue in their portal?

@Morgan DUBUISSON I had the same issue and I fixed it by adding the Log work field in the edit screen. 

It should work correctly when you have both time tracking and log work added in the screens: 

Regards

[Susanne Götz _Tempo_]

Hi @Pavel Kovařík

Tempo retrives the data for the original and remaining estimates (Estimate and Remaining) from JIRA, as these are native JIRA fields and all calculation is done by JIRA.

When a worklog is created, Tempo updates the Logged information and sends information about the worklog to JIRA. The calculation for the remaining estimate is then done in JIRA, and Tempo retrieves this information from there. 
You might need to refresh the page to show the updated information. 

Best regards,
Susanne Götz
Tempo team 

[Pavel Kovařík]

Hi @Susanne Götz _Tempo_ , 

thanks, but unfortunately the refresh didn't help either. I don't want to manually change the remaining estimate field in Jira to maintain continuity. This problem doesn't happen very often, yet I have already noticed it for several issues (1 out of 60).

So is it possible that somewhere there is a unique synchronization problem where first based on worklog 1.5h is added, Remaining is increased and then written as time spent?

[Susanne Götz _Tempo_]

Hi @Pavel Kovařík

Can you please create a ticket for this in our Tempo Support portal, https://tempo-io.atlassian.net/servicedesk/customer/portal/6, so we can better investigate this?

As the remaining estimate calculation is done by JIRA, you might also want to reach out to Atlassian.

Best regards,
Susanne

[Pavel Kovařík]

Sure, thanks! 

[Morgan DUBUISSON]

Good morning,

We are experiencing the same error, can you share the support response with us?