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

[UI] Notifications bell menu #51547

Closed
mikecote opened this issue Nov 23, 2019 · 5 comments
Closed

[UI] Notifications bell menu #51547

mikecote opened this issue Nov 23, 2019 · 5 comments
Labels
estimate:needs-research Estimated as too large and requires research to break down into workable issues Feature:Alerting/RulesManagement Issues related to the Rules Management UX Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) UX

Comments

@mikecote
Copy link
Contributor

No description provided.

@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-stack-services (Team:Stack Services)

@bmcconaghy bmcconaghy added Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) and removed Team:Stack Services labels Dec 12, 2019
@shaunmcgough
Copy link

Chatting with @peterschretlen earlier today, I wondered if we were considering tonal alerts. I believe an Elastic auditory alert would be in order. This would be a logical extension to visual alerts, and assist with accessibility. Two obvious preparations of the desired behavior would be to enable sounds or not generally, and to enable sounds or not on each alert. i am dropping a comment here, and if needed will log a new issue please just let me know.

@pmuellr
Copy link
Member

pmuellr commented Apr 1, 2020

I love the idea of "tonal" alerts - 20 years ago or so I had a cli program which took a long time to run, and so added a "--beep-on-error" option, which would beep when it wrote an error message. Started out as kind of a joke, but ended up being pretty useful.

@pmuellr
Copy link
Member

pmuellr commented Apr 1, 2020

An interesting possibility as well, would be to make use of "desktop notifications" via the web browser, using a service worker to poll for them in the background, even if the Kibana app isn't running in a tab. I'm pretty sure that's possible today - at least in Chrome - but easy to imagine they'd remove that functionality, or make it hard to enable, in the future.

@mikecote
Copy link
Contributor Author

mikecote commented Feb 4, 2021

Moving from 7.x - Candidates to 8.x - Candidates (Backlog) after the latest 7.x planning session.

@gmmorris gmmorris added the Feature:Alerting/RulesManagement Issues related to the Rules Management UX label Jul 1, 2021
@gmmorris gmmorris added the loe:needs-research This issue requires some research before it can be worked on or estimated label Jul 14, 2021
@gmmorris gmmorris added UX estimate:needs-research Estimated as too large and requires research to break down into workable issues labels Aug 13, 2021
@gmmorris gmmorris removed the loe:needs-research This issue requires some research before it can be worked on or estimated label Sep 2, 2021
@kobelb kobelb added the needs-team Issues missing a team label label Jan 31, 2022
@botelastic botelastic bot removed the needs-team Issues missing a team label label Jan 31, 2022
@XavierM XavierM closed this as completed Apr 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
estimate:needs-research Estimated as too large and requires research to break down into workable issues Feature:Alerting/RulesManagement Issues related to the Rules Management UX Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) UX
Projects
No open projects
Development

No branches or pull requests

8 participants