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

[Response Ops] Different Settings Button in Rules and Cases #191928

Closed
jcger opened this issue Sep 2, 2024 · 3 comments
Closed

[Response Ops] Different Settings Button in Rules and Cases #191928

jcger opened this issue Sep 2, 2024 · 3 comments
Labels
Feature:Alerting/RulesManagement Issues related to the Rules Management UX Feature:Cases Cases feature Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@jcger
Copy link
Contributor

jcger commented Sep 2, 2024

"Settings" Button is different for both pages, cases list and rules list. We need to use the same. This issue is about checking which one we should use and update it

Rules list:

Image

Cases list:

Image

@jcger jcger added the Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) label Sep 2, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/response-ops (Team:ResponseOps)

@cnasikas cnasikas added the Feature:Cases Cases feature label Sep 3, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/response-ops-cases (Feature:Cases)

@cnasikas cnasikas added the Feature:Alerting/RulesManagement Issues related to the Rules Management UX label Sep 3, 2024
@jcger
Copy link
Contributor Author

jcger commented Sep 10, 2024

Duplicated #188187

@jcger jcger closed this as completed Sep 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Alerting/RulesManagement Issues related to the Rules Management UX Feature:Cases Cases feature Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
None yet
Development

No branches or pull requests

3 participants