New views half baked

[cmr]

The new views all seem a bit half baked, most take some time to draw, refresh between sub menus and you often see the old one flash up when switching.  On top of that the layouts are messed up, in particular the switch view where hovering over a port brings up some details, but the port number and description is often cut off like below.  Only ports 8 and 9 on this switch show the port number and description 🙄

It is the same on other switch models, with maybe 20% of ports displaying properly.  I am happy to be a QA team for the developers as it is frankly getting embarrassing now where I have to tell customers to avoid the new views as they don't work 😞

[BlakeRichardson]

I agree, the load times of the new layouts is frustrating slow. The new UI should be an early access setting allowing them to be completely disabled until they are ready for full release. 

In IT we are told taught to never use Beta software in production and thats exactly whats happening. 

[GiacomoS]

Hey @cmr , @BlakeRichardson ,

Thank you so much for flagging this up and I'm sorry for the pain points here. 

We are still working hard on documenting and ironing the cosmetic and non-cosmetic issues that some of these pages introduced.

I would recommend to anyway have a case with our Support team raised to ensure some tracking and correct reporting of these problems, but in the meantime I've also gone ahead and shared the feedback internally with our product managers to review.

Thanks a lot for bearing with us as we work through this!

Giac

[GIdenJoe]

I also want to report that the updating of the new GUI switchports is way slower than the old version.
In the old version you could see a switchport coming up or going down within 2 seconds.  Now it takes 30 seconds or doesn't work at all and requires a refresh of the page.

Usually the refresh then always shows the current state and than goes back to the old state for a while before finally showing the correct state.

[OL_Nate]

THANK YOU 
I was wondering about reality when working with someone at another location.

Correct display of these states is IMPORTANT especially when trying to diagnose / support remote unknowns. Delays of correct information in those cases are always roadblocks to issue resolution. And when there's an issue with infrastructure, usually people depending on it are somewhere on their way to frustration, if not already fully arrived there. 

[OL_Nate]

As well, it's important to know if there's an upgrade available. 

Who should I trust?

In the old view, everything's current.

     

In the new view, an update is available, and no further information is reachable.

   

[GiacomoS]

Hey @OL_Nate ,

In a sense, both are accurate. In this example it seems you are in 17.2.1, which is still a stable release, so there's no need to upgrade unless you want to or need to because of specific issues; however as per the second view, an update is available, as we are currently on 17.2.2. 

Ultimately, my recommendation would be to manage the upgrades through the Firmware upgrade page, and make decisions on which firmware to go to based on the release change log and the current status of the firmware in the Organization > Firmware upgrades > Schedule upgrades page. 

Hope this helps!

Giac