Kibana: A number of alerting UX observations of lower prio

[arisonl]

Recording here a number of UX-related observations of lower priority. Those that the team considers worth to address (if any), will be converted to individual issues and will be added to the project:

1. Confirm delete?

2. Can only see the entire field when hovering

3. Hide the popover after selection?

Gets in the middle of the rest of the experience

[elasticmachine]

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

[arisonl]

4. Popover disappears when clearing the field selector

It should remain open and user should be able to type in order to search for new field.

[mdefazio]

Apologies for only just seeing this list.

1. Yep. My fault on not getting this prototyped initially

2. This is tricky because some of the entries will be very long, right? Extending the width of the popover is certainly an option, but not sure that really solves it.

3. Yes, and perhaps we need an x opposite the title of the popover?

4. Agreed

We had discussed moving the popovers open above the field instead of below. Was that finalized?

[pmuellr]

This is tricky because some of the entries will be very long, right? Extending the width of the popover is certainly an option, but not sure that really solves it.

Index patterns and fields names can be very long, so I think we'll need a better option than making forms wider. I've seen this most recently when picking an index pattern that is very long, then trying to pick the time field for it.

Seems survivable for 7.7 tho.