In the meantime, please revert back to a usable experience. Half the product being in UIv4 and having to do an extra movement before clicking just leads to frustration. You can still have the little pop up menu, but make the button itself still link to what it always linked to.
I want RBAC because my NOC guys spook easily and they’re already going to have a tough time adjusting to UIv4, not to mention my customers. It’s really a question of why I’d want any level of RBAC that is beyond simple RO vs. RW. Why do we have RBAC for support tickets? Why do we have RBAC for training? Why do we have RBAC for viewing your own profile info? Why do we have RBAC for OpsNotes? We want it because there are parts of the product that we don’t want certain users to have access to. The real question is why isn’t LM making a platform on which I can build the thing I want, the way that matches my business? Why didn’t LM give me an RBAC option to hide the explorer? Is it because some product manager is so thrilled with this new idea that they came up with to solve one problem that they think everyone should be using it. They’re so convinced of their own wonderous achievement that they didn’t even think about the fact that the use cases don’t apply to 100% of LM’s customers. For those that the use cases don’t apply to, those customers just have to deal with the extra, needless, wasted space in the UI.
While we’re at it, I need a way of preventing my customers from being able to access the new UI preview. I’ve had several customers with really frustrating experiences trying to use it, only to get on a call with me where the first thing I do is disable UIv4 preview. Then everything’s great for the customer. Can we please have the ability to choose who can view the new UI preview so i don’t have to spend an hour a day showing people how to turn it back off so they can get back to work?
It’s respecting my choice of UIv3 now. Nice job with that quick code merge.
