-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Navigation ordering in the Kibana section for 7.8 #66279
Comments
Pinging @elastic/kibana-core-ui (Team:Core UI) |
I conducted a bit of informal user research with experienced Kibana users to see if moving Visualize to the bottom is a problem. In summary: the new navigation is a large disruption of the user's flow, resulting in them having to re-learn the location of the apps. In addition, the new nav has 2 levels, so the list they have to scan through it short. On the background of that, users have no trouble finding Visualize at the bottom. Given these findings, I propose sticking with the original plan to move Visualize to the bottom now. If we leave this change for later, we will introduce a second event where users need to learn the new location of the apps which would be more disruptive in the end. |
To follow on Raya's comment here. |
@skearns64 @VijayDoshi @AlonaNadler can we make a final decision on this? |
I'm +1 on the proposed ordering. Thank you for getting user input, that makes a big difference in evaluating the change. In addition, Discover really jumps out in the telemetry data as the most common usage, so it makes sense to make it the first in the list. |
In the new Navigation we are introducing the ordering of the new navigation should remain as:
Discover
Visualize
Dashboard
Canvas
Maps
Machine Learning
Graph
In the future, once we are further along in our work on Time to Dashboard and Visualization Library, we can consider changing the order up. This will create a more consistent UX till we are able to change the overall authoring flow.
#63429
@AlonaNadler
The text was updated successfully, but these errors were encountered: