Can we please get back the autorefresh on the homepage in 6.x? This was such a nice feature in 5.x which is really missing in 6.x.
https://docs.bestpractical.com/rt/5.0.0/RT_Config.html#HomePageRefreshInterval
1 Like
The change is noted in the UPGRADING-6.0 file. Is there something on the page that you want to refresh that isn’t a saved search? Or maybe there is another reason the saved-search refresh doesn’t provide the refresh you need?
prior to 6.x you could leave the page open and it refreshed every x seconds automatically. This way you could have a look at new tickets without hitting f5 in the browser. I often had the homepage open in one tab and working on tickets in other tabs. When switching back to the main tab the refresh had updated the site, now I need to manually refresh. This feature is now gone completely but should be trivial to reimplement
You can still have it autorefresh. If you go to the saved search and click on Options, you can set the refresh interval, just like the old page refresh. It should work the same, but it will refresh just the saved search and not the entire page. You can set multiple saved searches to refresh also. When set, it will show the time of the last refresh at the bottom, so you can confirm it’s working.
Thanks for the hint, this worked perfectly! This was not really clear before, thanks!
1 Like
What’s the option for changing the refresh if one or more of the searches on a homepage are effectively read only for a user? Until now, an individual user can determine the refresh update period for their homepage without changing the saved searches or affecting others.
For example I’ve been playing with RT6.0.x on a test server and my non-admin account can see/run a saved search, but doesn’t have rights to change the options. Making a personal copy of that search might not be a good idea because then that user diverges from the group version, which in some cases is maintained on behalf of lots of users.
You’re correct that this changes refresh from a user-level setting to a search-owner setting. My thought is that searches with results that change frequently and benefit from automatic refreshes would generally be that way for anyone using a dashboard, like “new, unowned support tickets” for example. If there are users who don’t need the refresh for some reason, but still want the search on a dashboard, the search owner could create two versions of the search. Not ideal, but I think it should be infrequent. If we hear that this is a common problem, we can consider adding a user-level layer that could override the default search-level setting.
1 Like