[Obs alerts list] UX improvements to Alerts table

[katrin-freihofner]

Kibana version:
8.1 build locally with edge data

Browser version:
Version 98.0.4758.80

Browser OS version:
Mac OS

Describe the bug:

Steps to reproduce:

1. Visit the alerts view (with some rules enabled)

Expected behavior:

• the alerts table should use the full width
• the event.action column is not one of the default columns we'd like to show, it should be removed
• the reason message should be shown as a column
• "view in app" icon button (the eye icon) should navigate to the respective app
• I'm not sure why I can't add an alert to a case (both actions are disabled). I'm signed in with the admin user.

• the inspect button needs to be removed (in the last 30 days, 0.23% of Kibana users clicked it)
• the updated X seconds ago and fullscreen are overlapping

• [RAM] [META] Dynamic field selection in Alerts Table #137988 and ...
• [Security Solution]Incorrect sorting type for timestamp,Risk Score under Cases new alert tab #135101 - clicking the "recovered" or "active" buttons should not add this as a filter in the search bar
• Alerts table will reset fields to a different table config that the default #126765
• [Actionable Observability] Alerts table looks broken #125191

[emma-raffenne]

This needs to be backport to 8.1 as well

[emma-raffenne]

It looks like those fields appear when the columns are reset to the default fields, using the "reset" button in the field selector. To be confirmed (TBC).

[simianhacker]

Please tackle #125191 when working on this issue.

[elasticmachine]

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

[emma-raffenne]

@liciavale Please have a look at the following requirement:

• clicking the "recovered" or "active" buttons should not add this as a filter in the search bar
  Do you agree with this?

[jcger]

I reviewed all points with the new Alerts table and everything is working as expected so we should be ready to go once we do the migration.

cc @XavierM

[emma-raffenne]

@jcger I have checked the checkboxes for what I could test but there are a few that I couldn't check. Can you confirm that everything listed in the description of this epic either has been addressed and will be released in 8.4 or is obsolete as not applicable to the new shareable component?
Thanks!

[jcger]

Hi @emma-raffenne,

Every time the user updates the table settings (like visible columns, order, etc...) we save it locally in order to load it with this same configuration the next time the user visits the same table. Here is a screenshot of what a user sees when entering for the first time. You can easily test it just opening kibana opening your browser in private mode. Another way would be deleting the corresponding localStorage entry in your browser.

What I mean is that it should be working already, but I can't tell if it was fixed or if the screenshot was done after playing around with the columns.

Regarding clicking the "recovered" or "active" buttons should not add this as a filter in the search bar. It can't see any difference in the UI when clicking there so it looks like fixed to me but please consider opening kibana in private mode to try yourself as I'm not 100% sure how it was before.

Feel free to reach out to me if there is something else you need to know or if I haven't explained it good enough. Also, yesterday @maryam-saeidi and I met to talk about the internals and setup of this shareable component so she might be able to help you too

[maryam-saeidi]

Since I'm working on the integration of shared Alert Table on this page, I can verify the items after my implementation and close this ticket if everything is done already :)