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

Error experience in create alert flow #58181

Closed
alexfrancoeur opened this issue Feb 20, 2020 · 3 comments · Fixed by #59444
Closed

Error experience in create alert flow #58181

alexfrancoeur opened this issue Feb 20, 2020 · 3 comments · Fixed by #59444
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

Comments

@alexfrancoeur
Copy link

Feb-20-2020 15-47-45

Screen Shot 2020-02-20 at 3 48 20 PM

This feels like an area where we might be able to improve the UX. I didn't realize it was erroring out, I just thought it wasn't saving. Maybe a toast or a callout at the bottom would help if the creation errors out.

Separate question, is this a known error?

cc: @mdefazio @YulNaumenko

@alexfrancoeur alexfrancoeur added bug Fixes for quality problems that affect the customer experience Feature:Alerting labels Feb 20, 2020
@mikecote mikecote added the Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) label Feb 24, 2020
@elasticmachine
Copy link
Contributor

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

@mikecote mikecote self-assigned this Feb 24, 2020
@mikecote
Copy link
Contributor

@mdefazio any UX suggestions for this? I was seeing if I could move the error box into the flyout header but can't due to it being part of EuiForm within the flyout body.

I was thinking either scrolling up to the error box or display something within a toast message.

@mdefazio
Copy link
Contributor

I will work on mocking up something. I think if we show a toast at the bottom, or a callout perhaps, that might alleviate this.

@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
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants