Feedback UI

[cburgmer]

• Make aggregation of machines of an environment easier to understand (green vs. error states)
• Trying to click a link to the status page is annoying when the patch expands on long entries
• Hover roll out is lost every 5 secs on refresh

[rakhra]

Addressed - Hover roll out is lost every 5 secs on refresh
Addressed - Trying to click a link to the status page is annoying when the patch expands on long entries

The current hovered system is now stored in the browsers session storage. The relevant CSS hover style is applied to a system on window load based on the session storage. Additionally, we store the scroll position within the hovered system element and restore this on page load to further improve the UX. This change functions on the latest versions of Firefox, Chrome and Safari. However, remains untested for IE.

[cburgmer]

Here is an idea to visualise the aggregation step.

If all machines of a certain service are green, aggregate behind the first host (currently starting from the 2nd they are hidden):

If a machine is non-green, pop out a little, but still stack them behind the first machine:

On hover expand:

I am not sure whether hiding red/yellow machines behind the first is a good idea, as you wont see what's wrong at a first glance, but we could trial that. Feedback?

[rakhra]

We should move away from the idea of stacking the patches/cards in this fashion because:-

1. Users cannot quickly determine what package has been deployed to a particular host.
2. Users cannot quickly determine the host URLs for a particular service.
3. Hosts with issues should be visible without the additional need to click/hover.

Issues 1+2 are currently experienced by services with aggregated hosts that are all 'green'. However, a recent commit corrects these issues by displaying the hostname and package on the face of the patch. Additionally, a 'COLLAPSED' indicator is displayed to further highlight that the patch is displaying such aggregated information.