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

The Actions terminology in the code has diverged from the terminology we use verbally and in the UI #70082

Open
gmmorris opened this issue Jun 26, 2020 · 3 comments
Open

The Actions terminology in the code has diverged from the terminology we use verbally and in the UI #70082

gmmorris opened this issue Jun 26, 2020 · 3 comments
Labels
estimate:medium Medium Estimated Level of Effort Feature:Actions 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

@gmmorris
Copy link
Contributor

gmmorris commented Jun 26, 2020 •
edited by mikecote
Loading

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 connector.

This is also a step towards addressing #69442

Align the terminology in the code with the terminology we use externally and in the UI by changing "Actions" to "Connectors". This isn't a whole sale find-and-replace, as we'll still have an Actions feature, client etc. But we'll separate between the Connector entity and the Action entity as they are treated differently in the UI.
@gmmorris gmmorris mentioned this issue Jun 26, 2020
Open
4 tasks
@azasypkin azasypkin added Feature:Actions Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels Jun 29, 2020
@elasticmachine
Copy link
Contributor

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

@mikecote
Copy link
Contributor

Moving from 7.12 - Candidates to 7.x - Candidates.

@mikecote
Copy link
Contributor

mikecote commented Feb 5, 2021

Moving from 7.x - Candidates to 8.x - Candidates (Backlog) after the latest 7.x planning session.

@mikecote mikecote added the Project:UnifiedAlertingArchitectureAndExperience Alerting team project for developing a unified alerting experience. label Feb 5, 2021
This was referenced Feb 5, 2021
Open
Open
@gmmorris gmmorris added the loe:large Large Level of Effort label Jul 14, 2021
@gmmorris gmmorris added technical debt Improvement of the software architecture and operational architecture estimate:medium Medium Estimated Level of Effort labels Aug 13, 2021
@gmmorris gmmorris removed the loe:large Large Level of Effort label Sep 2, 2021
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:Actions 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 - Execution & Connectors
Status: Todo
Milestone
No milestone
Development

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