Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some timestamps stop updating #1627

Closed
compulim opened this issue Jan 23, 2019 · 3 comments · Fixed by #2090
Closed

Some timestamps stop updating #1627

compulim opened this issue Jan 23, 2019 · 3 comments · Fixed by #2090
Assignees
Labels
bug Indicates an unexpected problem or an unintended behavior. front-burner p1 Painful if we don't fix, won't block releasing

Comments

@compulim
Copy link
Contributor

compulim commented Jan 23, 2019

activity.timestamp is correct. Looks like some UI stopped from updating itself (thru setInterval or setTimeout). And there are no JavaScript errors.

image

image

And after awhile, the timestamp still looks the same.

image

@compulim compulim added the bug Indicates an unexpected problem or an unintended behavior. label Jan 23, 2019
@corinagum corinagum added front-burner Pending backlog Out of scope for the current iteration but it will be evaluated in a future release. and removed Triage-E labels Jan 23, 2019
@galenguilbert
Copy link

I'm wondering if there's a time frame for this fix?

@corinagum
Copy link
Contributor

Hi @galenguilbert, currently there is no time frame. Thank you for commenting, however! Customers adding their desire for these kinds of fixes puts them on our radar as something customers are looking for. I will add this to our discussion list for now. :)

@cwhitten cwhitten added the p1 Painful if we don't fix, won't block releasing label May 13, 2019
@corinagum corinagum added 4.5 and removed backlog Out of scope for the current iteration but it will be evaluated in a future release. labels May 13, 2019
@compulim
Copy link
Contributor Author

compulim commented Jun 18, 2019

Still seeing the bug as of today, easily reproducible but kind of random. Need to fix it in 4.5.

Probably related to TimeAgo.js or Timer.js.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Indicates an unexpected problem or an unintended behavior. front-burner p1 Painful if we don't fix, won't block releasing
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants