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

Make alerting UIs use new rule APIs #90381

Closed
mikecote opened this issue Feb 5, 2021 · 3 comments · Fixed by #96018
Closed

Make alerting UIs use new rule APIs #90381

mikecote opened this issue Feb 5, 2021 · 3 comments · Fixed by #96018
Assignees
@YulNaumenko
Labels
Feature:Alerting Project:UnifiedAlertingArchitectureAndExperience Alerting team project for developing a unified alerting experience. Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@mikecote
Copy link
Contributor

mikecote commented Feb 5, 2021 •
edited by gmmorris
Loading

Blocked by #90377.

This is the third part of #90375. We should make our alerting UIs use the new rule APIs as we deprecate the APIs using the old terminology.

For details on the introduction of the terminology see notes under #90375 (comment)
@mikecote mikecote added blocked Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) Project:UnifiedAlertingArchitectureAndExperience Alerting team project for developing a unified alerting experience. labels Feb 5, 2021
@elasticmachine
Copy link
Contributor

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

@mikecote mikecote mentioned this issue Feb 5, 2021
Open
17 tasks
@mikecote mikecote mentioned this issue Mar 8, 2021
Closed
@dhurley14 dhurley14 mentioned this issue Mar 22, 2021
Open
@gmmorris
Copy link
Contributor

This can be done in parallel with this by creating a feature branch out of Mike's feature branch (which should be merged soon, it's just blocked on documentation and test updates).

With that with mind - Unblocking

@gmmorris gmmorris removed the blocked label Mar 23, 2021
@YulNaumenko YulNaumenko self-assigned this Mar 26, 2021
@mikecote
Copy link
Contributor Author

@YulNaumenko, the new APIs are merged in master now: #93977.

@YulNaumenko YulNaumenko mentioned this issue Apr 1, 2021
Merged
@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
Feature:Alerting Project:UnifiedAlertingArchitectureAndExperience Alerting team project for developing a unified alerting experience. Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[Alerting UI] Changed alerting UIs use new rule APIs. YulNaumenko/kibana
5 participants
@gmmorris @kobelb @mikecote @elasticmachine @YulNaumenko