@Dale, this was a top feedback with several other things from several of us that beta tested 15.2 (yes 15.2) I know this may sound a bit harsh ,but what is the point of getting your customers' involved in a beta process, getting their feedback prioritized and then just ignoring it?
I saw that with several things and not just the documents . The new idea process should be for new enhancements, since it is a lengthy process. It really is about being transparent----customers should not have to ask CA to include existing functionality.. bigger things I get,,it takes time to code, but there are so many smaller features that would be a win win. What is the purpose of having a new look if users can't adopt it? And yes, this is for EXISTING customers, .. new customers won't really know the difference. CA should already have the immediate missing pieces (Again "smaller" wins ) planned and share that with the customers, especially since we are no longer getting patches but mini and major releases.
I desperately want our users to adopt the ux, but being a client for over 14 yrs,, my users are saying "what's the point?" -- the navigation /interaction with classic was also another TOP urgent priority feedback that has still not been addressed. and is the #1 push back from our users.. Users will be more willing to adopt it IF you give them more dynamic and easier ways to navigate between the two.(which I agree)