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.

Sign up for GitHub

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

Jump to bottom

Editing an alert is two clicks away #80313

Closed
arisonl opened this issue Oct 13, 2020 · 7 comments
Closed

Editing an alert is two clicks away #80313

arisonl opened this issue Oct 13, 2020 · 7 comments
Assignees
@YulNaumenko
Labels
estimate:small Small Estimated Level of Effort 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

@arisonl
Copy link
Contributor

arisonl commented Oct 13, 2020

Editing an alert is two (disconnected) clicks away (customer feedback)

edit
@arisonl arisonl added Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels Oct 13, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-alerting-services (Team:Alerting Services)

@mikecote mikecote added the UX label Oct 20, 2020
@mikecote
Copy link
Contributor

cc @mdefazio

@mdefazio
Copy link
Contributor

One quick solution is to have the Edit action available in the table row overflow menu. (This would still be 2 clicks, but an easier task). But I think going to the detail view is still correct when clicking the name.

@JDPC
Copy link

JDPC commented Jan 19, 2021

Hi All, I am unable to edit my alerts even though I am a superuser. Any ideas as to why?
image

@mikecote
Copy link
Contributor

mikecote commented Jan 30, 2021 •
edited
Loading

Hi @JDPC, I believe those are Stack Monitoring alerts? If so, they need to be edited in the Stack Monitoring application at this time. If you open "Setup Mode" there, you will be able to see the alerts and edit them from there at this time.

We are planning a fix for that with #89162.

@mikecote
Copy link
Contributor

mikecote commented Feb 5, 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
@arisonl arisonl mentioned this issue Jul 8, 2021
Closed
@YulNaumenko YulNaumenko self-assigned this Jul 8, 2021
@YulNaumenko YulNaumenko mentioned this issue Jul 8, 2021
Merged
@gmmorris gmmorris added the loe:medium Medium Level of Effort label Jul 14, 2021
@YulNaumenko
Copy link
Contributor

Resolved by PR #104190

@gmmorris gmmorris added estimate:small Small Estimated Level of Effort and removed loe:medium Medium Level of Effort labels 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@YulNaumenko YulNaumenko

Labels
estimate:small Small Estimated Level of Effort 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
None yet
Milestone
No milestone
Development

No branches or pull requests
8 participants
@gmmorris @kobelb @mikecote @mdefazio @arisonl @elasticmachine @JDPC @YulNaumenko