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

Hide index threshold from alerting UIs if alert type not in 7.7 #56780

Closed
mikecote opened this issue Feb 4, 2020 · 2 comments
Closed

Hide index threshold from alerting UIs if alert type not in 7.7 #56780

mikecote opened this issue Feb 4, 2020 · 2 comments
Labels
Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) v7.7.0

Comments

@mikecote
Copy link
Contributor

mikecote commented Feb 4, 2020 •
edited
Loading

In the scenario we can't ship #53041 in 7.7, let's remove it from the UIs (ex: create alert flyout). This could be done via feature flag so we can still demo the work in progress.

This issue should close if index threshold is merged before 7.7.
@mikecote mikecote added Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels Feb 4, 2020
@elasticmachine
Copy link
Contributor

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

@mikecote
Copy link
Contributor Author

mikecote commented Mar 3, 2020

Will not have to hide UI as #59064 made the index threshold UI work 👍 Closing.

@mikecote mikecote closed this as completed Mar 3, 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
Assignees
No one assigned
Labels
Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) v7.7.0
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@kobelb @mikecote @elasticmachine