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

[Alerting] Alert with broken connector should allow user to select existing connector of same type #87533

Closed
ymao1 opened this issue Jan 6, 2021 · 1 comment · Fixed by #89062
Closed

[Alerting] Alert with broken connector should allow user to select existing connector of same type #87533

ymao1 opened this issue Jan 6, 2021 · 1 comment · Fixed by #89062
Assignees
@ymao1
Labels
Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
Kibana Alerting

Comments

@ymao1
Copy link
Contributor

ymao1 commented Jan 6, 2021

From this PR comment.

When a user edits an alert that is using a connector that has been deleted, she is only given the option to create a new connector of the same type. If there is an existing connector of the same type as the deleted connector, she should be able to select that without creating a new connector.

To reproduce:

  1. Create 2 connectors of the same type (I like server log)
  2. Create an alert using 1 of the connectors created in (1)
  3. Delete the connector you just attached to the alert
  4. Edit the alert. Notice that you are given a warning that you are "Unable to load connector" but the only action available is to "Create a new connector"

Screen Shot 2021-01-06 at 12 40 42 PM
@ymao1 ymao1 added Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels Jan 6, 2021
@elasticmachine
Copy link
Contributor

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

@mikecote mikecote added this to To-Do (Ordered by priority) in Make it Action Jan 12, 2021
@ymao1 ymao1 moved this from To-Do (Ordered by priority) to In Progress in Make it Action Jan 20, 2021
@ymao1 ymao1 self-assigned this Jan 20, 2021
@ymao1 ymao1 mentioned this issue Jan 22, 2021
Merged
3 tasks
@ymao1 ymao1 moved this from In Progress to In Review in Make it Action Jan 26, 2021
@mikecote mikecote removed this from In Review in Make it Action Jan 27, 2021
@mikecote mikecote added this to In Review in Kibana Alerting Jan 27, 2021
Kibana Alerting automation moved this from In Review to Done (Ordered by most recent) Feb 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

@ymao1 ymao1

Labels
Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
No open projects
Kibana Alerting
Done (Ordered by most recent)
Milestone
No milestone
3 participants
@kobelb @ymao1 @elasticmachine