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

[ResponseOps][Rules] Improve query selection in ES rule #209002

Open
joana-cps opened this issue Jan 30, 2025 · 1 comment
Open

[ResponseOps][Rules] Improve query selection in ES rule #209002

joana-cps opened this issue Jan 30, 2025 · 1 comment
Labels
enhancement New value added to drive a business result Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@joana-cps
Copy link

During the new Rule form tasks came to the attention the way we ask users to select the query type in ES Rule creation.
There are some issues with the current component:

  • It takes too much space in a flyout
  • It takes too many clicks to change the language
  • We clean the form each time we change the query type, making the user lose any query that one has writen
  • ES|QL as the last option
Image

In order to improve the UX and push for an ES|QL first approach I'm proposing to change this to a simple select field.
Changing the Query type to a select field will improve the user experience and make the:

  • ES|QL selected by default
  • No need for user input when starting the form to select query type
  • Fewer clicks to change query type
  • In the first iteration, we can mimic current behavior when choosing a new one. But it would be nice to keep the query parameters when we switch query type (TBD with the engineer)
Image

This change will also make it easier for this form to be pre-populated when creating rules from Visualizations:#197489


Resource
🎨 Design: Figma File Handoff

@cnasikas Might be a good one to included as a sub-issue in: #196235

@joana-cps joana-cps added enhancement New value added to drive a business result Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels Jan 30, 2025
@elasticmachine
Copy link
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New value added to drive a business result Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
None yet
Development

No branches or pull requests

2 participants