elastic / kibana

Your window into the Elastic Stack
https://www.elastic.co/products/kibana
Other
19.6k stars 8.21k forks source link

[Dashboard] Improve context menu options organization #177254

Closed markov00 closed 7 months ago

markov00 commented 8 months ago

I believe the current context menu, in particular when clicking into More is pretty confusing (see the screenshot)

Screenshot 2024-02-20 at 09 36 54

There isn't a logic order of elements (or at least I can't find one) and they seems to be mixed up a bit.

I'm wondering if there is a way to sort and better organize these items (even if they are dynamic menu items). Something like adding a group name or just a line separator (as in OS context menu) will be already enough

Screenshot 2024-02-20 at 09 44 05 Screenshot 2024-02-20 at 09 44 39

I can see at least 3 groups: Panel related operations, Data related actions, and Security related where items can be grouped.

Screenshot 2024-02-20 at 09 36 54
elasticmachine commented 8 months ago

Pinging @elastic/kibana-presentation (Team:Presentation)

ThomThomson commented 8 months ago

Great idea @markov00. We're currently aiming to move some of the most common actions out of this context menu into hover actions to make them easier to click.

With the remainder, we should look into fixing this issue by using an action grouping.

nreese commented 8 months ago

@markov00 Thanks for opening this issue and laying out solution options. I really like the idea of having a line indicating groupings.

@ThomThomson This seems like pretty low hanging fruit. What do you think about @markov00's grouping and implementing a visual distinction between groups in the very short term? Lets not fall into the trap of letting small quality of life improvements getting overshadowed by longer term initiatives.

teresaalvarezsoler commented 7 months ago

Thanks @markov00 for starting this discussion. I did some analysis in the past using telemetry and after discussing it with the team we agreed in the following:

The final menu will look like this:

image image

Please @andreadelrio, can you review this? Thanks!

markov00 commented 7 months ago

Just to me clear, when I was saying grouping I didn't mean group them in sub-menus, but just reorder the items and put an horizontal line between groups (like in the actual browser context menu) These items are already within the sub-menu More... and deeper sub-menu hierarchies are actually not a great UX IMHO.

< Options
-------------
Maximize panel
Replace Panel
Save to Library
Copy to Dashboard
Delete from Dashboard
-------------
Inspect
Explore in Discover
Download CSV
-------------
Add to Existing Case
Add to New Case
andreadelrio commented 7 months ago

@teresaalvarezsoler After reading through this discussion and checking out some references I've come up with three proposals trying to incorporate everything. I think the Delete from dashboard should be a quick access (i.e. top-level) action. It should ideally appear at the bottom (i.e. footer) as mentioned above. Currently, we have the "Create drilldown" action in that location so we'd need to decide whether we keep it on the top level or send it to the second level. I checked the relative usage (last 90 days) of paying customers in FullStory and found that Delete from dashboard is used more often than Create drilldown which should come as no surprise.

Frame 454

Here are the three proposals:

Option A: Create drilldown is sent to the second level. Option B: Create drilldown is kept on the top-level with a dedicated section. Option C: Create drilldown is kept on the top-level but no longer gets a dedicated section.

Frame 444b
teresaalvarezsoler commented 7 months ago

Thank you @andreadelrio . I think Option A makes more sense. Just for the records, when there are Drilldowns created, there will be another option under "Create drilldown" called "Manage drilldowns".

ThomThomson commented 7 months ago

++ to Option A, These look great!