The problems view can only be refreshed to show the latest state by switching subapps to the definitions subapp and back. It should be easy, clear, and one click away to reload the contents. (Note, a browser refresh also does not show the latest problems state.)

The common usecase is that a developer is working to remove the problems in thier project. They have this view open and they fix code or config elsewhere - then they want to check again if the problem is fixed. 

The configured view should stay the same when the contents are reloaded so that a developer does not loose their place - ie same filters and same scroll-location.