Time tracking bars not updating immediately after new logged work

[Stine Søndergaard]

I have a problem with logged work in Jira and the time tracking bars in BigGantt. 

Logging work in Jira will update the task correctly in Jira. When going to BigGantt the task will however stay the same as before the new work was logged. 

I have tried to refresh the page, hard refresh the page, re-sync manually, but nothing seems to help at that specific time. Strange thing is, that after some time, the bars have updated just fine. 

So the link is there, I just don't know how to force them to update. 

Anyone with a similar problem - and a solution? 

/Stine

[Marcin Geb _SoftwarePlant_]

Hello Stine,

I did some testing and the time tracking bars get updated immediately in BigGantt on my instance, but obviously it's July now. Since you included the jira-cloud tag, I assume you are on the Cloud hosting and I'd attribute the issue to the fact that the server on which your BigGantt resides is usually not the same server on which your Jira Cloud sits.

If those servers have problems communicating then there could be delays. Are these delays normally expected? No. And I did my testing on Jira Cloud.

It would be helpful to know how long the delay is. Would you estimate it to seconds, minutes, or perhaps hours? Is the issue happening consistently over time? Or is it of intermittent nature?

On a related note, SoftwarePlant apps' users will soon be able to choose the geographic location of a server where their instance physically is, more on that here:

https://softwareplant.com/data-location-jira-cloud/

Sure, it's about BigPicture and not BigGantt, but still, you will have the option to change the server.

[Andy Putra]

Hi Marcin,

This case also happened in my team. i think this happened when my teammates update the log, it won't updated in the BigGantt directly

BigGantt owner --> me

Update log --> another user

i did some testing with edit the my teammate log without any changes, after that i did re-sync, after that time tracking finally updated. this case always happened right now.