Skip to content
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

[Discuss] Kibana grouped navigation feedback #55609

Closed
ryankeairns opened this issue Jan 22, 2020 · 12 comments
Closed

[Discuss] Kibana grouped navigation feedback #55609

ryankeairns opened this issue Jan 22, 2020 · 12 comments
Labels
design-only Can be handled solely by a design team member discuss loe:medium Medium Level of Effort

Comments

@ryankeairns
Copy link
Contributor

ryankeairns commented Jan 22, 2020

Why is the navigation changing?

In an effort to better align with marketing efforts and manage the growing number of applications displayed in the Kibana navigation, we have merged a new solutions-based grouping concept into kibana master.

Specifically, you will now see Analyze, Observability, Security, and Management in the left-hand navigation. Note: the letters will be replaced by icons soon.

Screenshot 2020-01-24 10 32 09

What is happening next?

The 7.7 timeframe will be used to collect feedback and refine the grouped navigation design. Any amount of change can feel disruptive, so we ask that you give it some time and see how things feel after using it for a while.

In parallel, the design team is also working on a larger navigation redesign effort for 8.0 that expands upon the grouping concept and further addresses the ever-growing number of plugins. The 8.0 design will explore the use of an off-screen style menu including additional features such as pinning, global search, and Cloud integration.

Where can I provide feedback?

Right here! Please submit your feedback as comments on this issue.

In particular, we would like feedback regarding:

  • Order and grouping
  • Naming
  • Interaction
  • Accessibility

FAQs

What happens if there are no submenu items?
Clicking a top level item with no submenu items will take you directly to that plugin.

What happens if features (plugins) are turned off?
If, for example, a plugin is disabled for a particular Space, then it will no longer appear in the menu/submenu. Further, if only one submenu item is active for the group, then the top level nav item will go directly to that plugin.

In order to save a click, how about opening the submenu on hover?
We originally used a hover interaction when the navigation design was updated for Kibana 7. The feedback was predominantly negative as the submenu covered the UI and could be accidentally triggered with an errant hover.

What about the OSS version of Kibana?
For the OSS version, grouping is disabled unless you have seven or more total plugins enabled. Additionally, if there is only one top-level group (not including Management), then grouping will not be applied.

Can I turn this off?
Yes. Find the Side nav style setting under Stack Management > Advanced settings

What about pinning and search?
Pinning and search are being considered in the 8.0 design.


Original issue: #53313
Grouped nav PR: #53545

@aravindputrevu
Copy link

Is there a demo of Kibana with this change we can try?

@ryankeairns
Copy link
Contributor Author

Is there a demo of Kibana with this change we can try?

Currently, the only way to preview this change is by running the Kibana master branch locally. For those unfamiliar with this process, please refer to the CONTRIBUTING docs.

@afharo
Copy link
Member

afharo commented Jan 24, 2020

A couple of suggestion here:

  1. Recent apps shortcuts:
    Now that we made so much space on the sidebar (I love it! Well done!) and taking into account the human is a creature of routine... Have we considered adding shortcuts to the last few opened apps?

    Like, imagine I usually jump between Canvas and the Dev Console because I like playing with aggregations first and, then, going back to my Canvas to add the actual metric to my visualisation. Going through sub-menus is a bit annoying when you are repeatedly doing so.
    Since the user will likely jump constantly through a few of them, maybe it's a good idea to provide them with a shortcut to that app.

  2. App Launcher
    If you know what you are looking for (ie: "Canvas") but you don't really know where it's sitting, an app launcher where you can type and the menu highlights where you can find it?

@shahzad31
Copy link
Contributor

I like the simplicity, i only have one suggestion, is it possible to add an expandable sublist to each icon, for example if you click on Observability, a list of icon gets expanded and it remains expanded unless user clicks on the other Parent Icon like Analyze. I really don't like two clicks to reach an app.

@kcm
Copy link

kcm commented Jan 27, 2020

I work with our customers in the field and sit with them for 32 hours of every week, typically. Recent/Frequent Apps and a open-on-flyover nav menu are the two most important improvements I can identify, from observing their usage patterns and their frustrations.

While I like the solution-based grouping, most users use only a few apps, and won't care that SIEM is now in another place, if they don't already use it. It's not worse, but it's not better either, in this regard.

Far and away, the need to click to open the nav menu is the biggest complaint. Even I, as someone that works with our stack every day, have trouble remembering which icon is which, and dislike finding each one amongst many per my first point. Most users want the old behavior of open and close on flyover/flyout, even if it briefly covers some work area.

My ideal for most heavy Kibana users would be a drag-to-add area at the top for your favorite apps, in your order. It would solve both points.

@pheyos
Copy link
Member

pheyos commented Jan 27, 2020

This has already been mentioned in #53545 (review):
I would suggest to either let all top nav icons open a menu (even though they may contain only one icon) or to make it clear which one will open a menu and which one will take you straight to an app (e.g. by adding a small arrow to the icons that will open a menu).

@ryankeairns
Copy link
Contributor Author

I like the simplicity, i only have one suggestion, is it possible to add an expandable sublist to each icon, for example if you click on Observability, a list of icon gets expanded and it remains expanded unless user clicks on the other Parent Icon like Analyze. I really don't like two clicks to reach an app.

Thanks for the feedback @shahzad31 . So that I am following, are you suggesting that the sub menu would stay open until the user decides to close it? In other words, a submenu is always visible? (essentially locked open)

@ryankeairns
Copy link
Contributor Author

My ideal for most heavy Kibana users would be a drag-to-add area at the top for your favorite apps, in your order. It would solve both points.

@kcm thanks for the detailed feedback. Regarding your last point, we're hoping to add pinning to the Kibana 8.0 navigation. This would allow customers to basically customize the navigation to their liking by moving (pinning) their most used applications to the top of the navigation.

@mbarretta
Copy link

Two questions:

  1. Is there any means to select which apps land under which solutions? I could see Maps being an app that could be used in all solutions
  2. Will existing feature controls still work if the grouping is disabled? In other words, could I still have a nav with just Dashboard, Maps, and (since I can't hide it) Management?

@shahzad31
Copy link
Contributor

I like the simplicity, i only have one suggestion, is it possible to add an expandable sublist to each icon, for example if you click on Observability, a list of icon gets expanded and it remains expanded unless user clicks on the other Parent Icon like Analyze. I really don't like two clicks to reach an app.

Thanks for the feedback @shahzad31 . So that I am following, are you suggesting that the sub menu would stay open until the user decides to close it? In other words, a submenu is always visible? (essentially locked open)

@ryankeairns
Yes it will remain open, unless user clicks on any other category submenu.

For example if user Clicks on Analyze icon, a submenu containing three icons, Discover, Canvas and Maps, will open, and it will remain open, unless user clicks on observability Icon. And upon clicking observability icon, we can close Analyze submenu.

In Icon View Submenu will be just icons.

@ryankeairns ryankeairns added loe:medium Medium Level of Effort design-only Can be handled solely by a design team member labels Jan 29, 2020
@ryankeairns
Copy link
Contributor Author

ryankeairns commented Jan 29, 2020

@mbarretta

  • Is there any means to select which apps land under which solutions? I could see Maps being an app that could be used in all solutions

We don't currently intend to display an application under multiple groups. That said, we're clearly in the feedback stage and your suggestion has been noted :)

  • Will existing feature controls still work if the grouping is disabled? In other words, could I still have a nav with just Dashboard, Maps, and (since I can't hide it) Management?

As I understand it, the nav will work just as it did prior to this change if you switch from the 'Grouped' to 'Individual' style under Advanced Settings.

@ryankeairns
Copy link
Contributor Author

Closed in favor of new grouped design: #64018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
design-only Can be handled solely by a design team member discuss loe:medium Medium Level of Effort
Projects
None yet
Development

No branches or pull requests

7 participants