Same for me, sometimes I don't see updating correctly, or even the job timestam looks odd. I must always refresh twice the page for MultiJobs.

Same issue exists for me since the refresh was deactivated. Always I must refresh twice the page in order to get last status correctly.

This is not a bug. The feature will not be restored. Please leave this issue closed.

As I wrote above, individual changes elsewhere to update status information in the background is what should be done.

Bonus: If your Jenkins instance is configured to not submit anonymous usage statistics to the Jenkins project, you only have yourself (or your admin) to blame.

Cool response.  You guys really know how to treat paying customers.  We all know what should be done, but that doesn't change the fact that you aren't doing it (or haven't yet anyway).  You seemed to hint that there was a technical reason for removing the old refresh feature without replacement, so perhaps it would make sense to us 5 percenters if you just explained that.

You guys really know how to treat paying customers.

I don't understand this comment. Jenkins is free software distributed under the MIT license.

If you're referring to my employer's products or services, I recommend you go through CloudBees support and feedback systems for customers. That could help prioritize support for dynamic refresh of components that are important to you.

But this site is the Jenkins project's issue tracker, not CloudBees's.

there was a technical reason for removing the old refresh feature

JENKINS-19828 and linked issues should give you an idea of various problems with auto refresh. While many of these individual problems may have been addressed since, it's not become a better designed solution since JENKINS-484 was filed in 2007.