"x minutes ago" not updating on the activity feed

Question

Post timestamps and their corresponding "x minutes ago" label are no longer updating on the activity feed automatically. I have to manually refresh the page to get accurate times for how long ago everything was posted. If not, I can see "just now" (or an incorrect amount for "x minutes ago" depending on the last time I manually refreshed the page) next to a post that has been sitting for hours. Is there a setting I need to change on the board or is this a known internal issue? This has been a problem for at least two weeks.

As you can see in the picture I'm including, when I hover over the time stamp that says I posted 2 minutes ago, it shows that I actually posted 10 minutes ago (posted at 1:11pm and time in bottom right is 1:21pm).

DiMaggio Tucci · Answer

@Michael Munday

Hmm...I actually noticed that the timestamps did seem to update even when I purposefully killed my connection, so that may not be the cause of the issue!

Still, contacting them directly is probably best at this point.

Let me know how it goes!

Michael Munday · Answer

I see. I tried it as well and nothing changed after opening the network activity screen, so it looks like you're correct about this being a connection issue. Switching browsers didn't change anything either as the problem persisted on Chrome, Firefox, and Microsoft Edge. I'll take your advice and contact Atlassian directly. Thanks for your help!

DiMaggio Tucci · Answer

I'm using Chrome on Windows 11, ensuring Chrome is fully updated (not necessarily Windows 11; I hadn't checked the version run at that time).

For context, I tested this by making a change and then watching that screen. It updated minute by minute for a few minutes, and I considered that as the evidence that my browser was not reproducing the error.

I used the instructions I provided (In Chrome for Windows, the shortcut is Ctrl+Shift+I) to check the networking activity.

Interesting, I would think using multiple networks would eliminate a connection issue on your end. That being said, there's so many points where there could be a problem that it's hard to say.

You might consider contacting Atlassian directly. That could eliminate the possibility of an issue with the server running your instance on their end.