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

Alert flyout icons within "Select a trigger type" are not vertically aligned #67139

Closed
mikecote opened this issue May 20, 2020 · 2 comments · Fixed by #73665
Closed

Alert flyout icons within "Select a trigger type" are not vertically aligned #67139

mikecote opened this issue May 20, 2020 · 2 comments · Fixed by #73665
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) UX

Comments

@mikecote
Copy link
Contributor

This happens between single and multi line names.

image

@mikecote mikecote added 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) labels May 20, 2020
@elasticmachine
Copy link
Contributor

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

@mdefazio
Copy link
Contributor

I think instead of trying to fix the alignment of these, we should work towards something along the lines of the below mockup. Finding icons for each alert type will be difficult to maintain and we should consider having short descriptions for each type.
I'm not suggesting search is needed at this time, but also something that will likely be needed in the future as this list grows.

cc/ @andreadelrio

image

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

Successfully merging a pull request may close this issue.

4 participants