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

"Save" Button is enabled for Alerts containing Actions with broken Connector #79672

Closed
ymao1 opened this issue Oct 6, 2020 · 1 comment · Fixed by #80579
Closed

"Save" Button is enabled for Alerts containing Actions with broken Connector #79672

ymao1 opened this issue Oct 6, 2020 · 1 comment · Fixed by #80579
Assignees
Labels
Feature:Actions Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@ymao1
Copy link
Contributor

ymao1 commented Oct 6, 2020

To reproduce:

  1. Create an Index Threshold alert with an associated action (I used Slack)
  2. Delete the connector for the associated action.
  3. Create a test user with role that has "All" access to "Built-In Alerts" and "Read" access to "Actions"
  4. Log in as the test user and navigate to "Alerts and Actions"
  5. Select the alert created in Step 1 and click "Edit"
  6. Notice that the action associated with the alert has a message "No Slack connectors" but your user doesn't have the privileges to configure a connector.
  7. Notice that the "Save" button is enabled but when you try to Save without removing the broken action, you will receive a 400 error message.
@ymao1 ymao1 added Feature:Alerting Feature:Actions Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels Oct 6, 2020
@elasticmachine
Copy link
Contributor

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

@ymao1 ymao1 changed the title "Save" Button should be disabled if Alert has Action with broken Connector "Save" Button is enabled for Alerts containing Actions with broken Connector Oct 6, 2020
@mikecote mikecote mentioned this issue Oct 13, 2020
36 tasks
@ymao1 ymao1 self-assigned this Oct 14, 2020
@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
Labels
Feature:Actions Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants