Kibana notifications UX pile on the screen and prevent users from taking actions

[AlonaNadler]

When there is an issue with a shard or a specific index Kibana notifications can start to pile on the screen
It's a problem because:

• To remove you need to click on each one which is annoying and sometimes constantly continuing to pile
• The notifications pile and hide important parts of the screen which prevents the user from moving on

User quotes :

I can't hit "Save and Return" on this TSVB visualization because the popups are blocking the button and they reappear as fast as I can close them (probably due to some eager autoretry logic)

Similarly I can't click the gear -> edit visualization to open visualizations after having this dashboard open for a few seconds because the popups overwhelm the right side of the screen

@alexfrancoeur

[elasticmachine]

Pinging @elastic/kibana-app-services (Team:AppServices)

[lizozom]

I really think we need a dismiss all option for them!
However I suspect this is a @elastic/kibana-core issue as they own the notifications service

[alexfrancoeur]

Thanks for filing Alona! I've personally run into this many times. There is a workaround, that I'm afraid I've probably gotten too used to at this point, and it's to click "show details" and then clear the notifications. It will remove all toasts. I agree, it would be great to have a dismiss all button.

Regarding the notification service, I'm not sure if these toasts or errors would live there. I would think that they'd still exist as they are today. Outside of a dismiss all button, it'd be great to see common errors or warnings grouped in toasts with a count and a dismiss all button. @ryankeairns do you have any thoughts around UX here?

Adding @thesmallestduck to the thread.

[ryankeairns]

This specific issue has come up in past situations, but it is not prioritized on any roadmap that I'm aware of. As you can see in the linked issue, it was on the radar of Core UI and still needs to be reassigned. With the fairly clear proposals, it strikes me that a good next step would be a technical one to prove if/how well we can do things like grouping same messages. From there, the design team can provide guidance on button placement, etc.

Given the duplicative nature, I would propose closing this specific issue.

[streamich]

I've added Team:Core label, @elastic/kibana-core does it make sense to solve it in Notification service in core?

[lizozom]

Duplicate of #67270
Closing