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

[Alerting] Missing CTA in error mode in Index Theshold #61431

Closed
gmmorris opened this issue Mar 26, 2020 · 4 comments · Fixed by #61615
Closed

[Alerting] Missing CTA in error mode in Index Theshold #61431

gmmorris opened this issue Mar 26, 2020 · 4 comments · Fixed by #61615
Assignees
Labels
bug Fixes for quality problems that affect the customer experience Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) v7.7.0 v8.0.0

Comments

@gmmorris
Copy link
Contributor

When Index Threshold goes into an error state it no longer shows the user which field is missing (the Index field).

It should still say "Select a field" or something to that effect, I think.

29Nkfae6el

@gmmorris gmmorris added bug Fixes for quality problems that affect the customer experience Feature:Alerting v8.0.0 v7.7.0 Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels Mar 26, 2020
@elasticmachine
Copy link
Contributor

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

@gmmorris
Copy link
Contributor Author

After discussing with @mdefazio seems this is in line with how the Expression components behave in other places in Kibana- so he'll discuss with the team to see if this is correct.

One thing I still think we might want to address is that we message "Expression contains errors" but it's very unclear now what is actually invalid.
My thinking is that we should either make the message clear that the Index field is invalid, or perhaps we should mark the word "Index" in red.

@mdefazio
Copy link
Contributor

My thinking is that we should either make the message clear that the Index field is invalid, or perhaps we should mark the word "Index" in red.

Can we do both (and for most/all errors)? Will help if the error is further down the form.

@mdefazio
Copy link
Contributor

@gmmorris From discussions with the design team, the way to solve this would be to provide something when it's empty. It's just rendering whatever is passed to it, so we have flexibility on how we make this work for us. Perhaps we have a message where the index would be (and the expression group shows red for error)?

But it's not something that makes sense to build into the component itself as we lose some of the flexibility.

@mikecote mikecote self-assigned this Mar 27, 2020
@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
Labels
bug Fixes for quality problems that affect the customer experience Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) v7.7.0 v8.0.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants