Admin UI systems filters should be accessible by the corresponding roles

[wsmirnow]

A non privileged admin UI user should may access jobs, services and servers filters by having the corresponding view roles.

Your pull request should…

• have a concise title
• close an accompanying issue if one exists
• be against the correct branch (features can only go into develop)
• include migration scripts and documentation, if appropriate
• pass automated testing
• have a clean commit history
• have proper commit messages (title and body) for all commits
• have appropriate tags applied

[gregorydlogan]

This is kinda gimmicky, but what would be the expected set of minimum roles to view just these options? ROLE_ADMIN_UI plus the changes here? Because that leads to a broken UI. The test user is trapped on the events tab with the loading spinner, and no hamburger on the left to get to the other tabs...

[wsmirnow]

You need the ROLE_UI_JOBS_VIEW to see especially the jobs tab. But if the user is not an global admin, the filters endpoint will be empty or hidden. Same for servers and services.
The minimum role set is:

• ROLE_ADMIN_UI to generally see the admin UI parts
• ROLE_UI_NAV to generally see the navigation menu
• ROLE_UI_NAV_SYSTEMS_VIEW to see the systems icon/option in the navigation menu
• ROLE_UI_JOBS_VIEW to see the jobs tab
• ROLE_UI_SERVERS_VIEW to see the servers tab
• ROLE_UI_SERVICES_VIEW to see the services tab

I've created an sample user on develop.opencast.org (username and password: systems-viewer) to test this scenario. There you can verify, that the filter pane isn't shown.