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

Rename code and files to use new rule terminology #90384

Open
mikecote opened this issue Feb 5, 2021 · 3 comments
Open

Rename code and files to use new rule terminology #90384

mikecote opened this issue Feb 5, 2021 · 3 comments
Labels
estimate:medium Medium Estimated Level of Effort 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) technical debt Improvement of the software architecture and operational architecture

Comments

@mikecote
Copy link
Contributor

mikecote commented Feb 5, 2021

This issue covers the last part of #90375 for the new rule terminology. We should go through our codebase and change it to reflect the new terminology of rule.
@mikecote mikecote added 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
Copy link
Contributor Author

mikecote commented Feb 5, 2021

I'm moving this issue directly into 8.x - Candidates (Backlog) with its sibling #70082 issue for connectors. This is based on the latest 7.x planning session.

@mikecote mikecote changed the title Rename code to reference new rule terminology Rename code to use new rule terminology Feb 5, 2021
@mikecote mikecote changed the title Rename code to use new rule terminology Rename code and files to use new rule terminology Feb 5, 2021
@gmmorris gmmorris added the technical debt Improvement of the software architecture and operational architecture label Jul 1, 2021
@gmmorris gmmorris added the loe:large Large Level of Effort label Jul 14, 2021
@gmmorris gmmorris added the estimate:medium Medium Estimated Level of Effort label Aug 18, 2021
@gmmorris gmmorris removed the loe:large Large Level of Effort label Sep 2, 2021
@gmmorris
Copy link
Contributor

gmmorris commented Nov 2, 2021

We have decided to try chipping away at this issue week by week, leaning on our triage rotation.
Whoever is on rotation that week will try and submit one PR in which they clean up some of the legacy terminology.

Please link your PRs to this issue, and if can't find any code that needs cleaning up anymore then - close this issue ❤️

@ymao1 ymao1 mentioned this issue Nov 2, 2021
Merged
@ymao1 ymao1 mentioned this issue Dec 8, 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
No one assigned
Labels
estimate:medium Medium Estimated Level of Effort 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) technical debt Improvement of the software architecture and operational architecture
Projects
No open projects
AppEx: ResponseOps - Rules & Alerts Management
Status: No status
Milestone
No milestone
Development

No branches or pull requests
4 participants
@gmmorris @kobelb @mikecote @elasticmachine