-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Alerts table will reset fields to a different table config that the default #126765
Comments
Pinging @elastic/response-ops (Team:ResponseOps) |
I think this is an issue in Observability, rather than ResponseOps, but I won't remove our label until o11y can confirm. |
@formgeist As @fkanout mentioned there is no such option at the moment. You can reset to the default configuration, if you clear your localStorage from the console. Do you know if this option is part of the EuiDataGrid? Otherwise just give us some design where you would like us to place this option and we will clear the localStorage to do the reset. Another question I have. Does security offer an option to reset to the default configuration? |
@fkanout @mgiota Thanks for the response! I didn't realize that the config is saved in localStorage, that's really helpful. I think I found a really weird bug where the reset fields option works in the same app, but when switching from e.g. overview -> alerts view, the reset fields suddenly returns a completely different config. I think this is probably the problem I've encountered, since the reset fields option does work if you do it while in the same app. I'll update the issue description and title to reflect this. CleanShot.2022-03-09.at.09.10.41.mp4 |
Also described in #125561 |
Kibana version:
8.2.0-snapshot
Description of the problem including expected versus actual behavior:
I somehow managed to resize the column in the alerts table and now I'm stuck with a narrower table size than the default configuration. The table doesn't offer an option to reset the configuration of the table to the default.
Steps to reproduce:
CleanShot.2022-03-09.at.09.10.41.mp4
The text was updated successfully, but these errors were encountered: