[ResponseOps][Alerts] Fix Security alerts table not switching view mode columns correctly#245253
Merged
PhilippeOberti merged 2 commits intoelastic:mainfrom Dec 4, 2025
Conversation
umbopepato
added
release_note:fix
Team:ResponseOps
Contributor
|
Pinging @elastic/response-ops (Team:ResponseOps) |
PhilippeOberti
approved these changes
Dec 4, 2025
Contributor
PhilippeOberti
left a comment
PhilippeOberti
left a comment
There was a problem hiding this comment.
Desk tested and code LGTM, thanks for fixing this for us!!!! 🙏
Contributor
💛 Build succeeded, but was flaky
Failed CI StepsMetrics [docs]Async chunks
History
|
Contributor
|
Starting backport for target branches: 8.19, 9.1, 9.2 |
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Dec 4, 2025
…de columns correctly (elastic#245253) ## 📄 Summary Forces the Security AlertsTable to rerender entirely when switching view mode (`Grid view/Event rendered view` dropdown in the table toolbar) to make sure the columns are updated correctly. <details> <summary> ## 🧪 Verification steps </summary> 1. Create Security rules that fire alerts 2. Navigate to Security Solution > Alerts 3. Try switching view mode `Grid view` <> `Event rendered view` one or more times, with page reloads in between too 4. After switching mode, try adding/removing columns to the table from the `Fields` toolbar menu 5. After editing the columns, try to reset to the default ones (`Fields` > `Reset fields`) </details> ## ⏪ Backport rationale Backporting to all branches where the issue occurs ## 🔗 References Fixes elastic#245257 ## Release Notes Fixes an issue that caused the Security alerts table to not update columns correctly when switching view mode ## ☑️ Checklist - [ ] ~~Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)~~ - [ ] ~~[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials~~ - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] ~~If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)~~ - [ ] ~~This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations.~~ - [ ] ~~[Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed~~ - [x] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [x] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. (cherry picked from commit 3a3d46c)
Contributor
💔 Some backports could not be created
Note: Successful backport PRs will be merged automatically after passing CI. Manual backportTo create the backport manually run: Questions ?Please refer to the Backport tool documentation |
Contributor
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
PhilippeOberti
pushed a commit
to PhilippeOberti/kibana
that referenced
this pull request
Dec 4, 2025
…de columns correctly (elastic#245253) ## 📄 Summary Forces the Security AlertsTable to rerender entirely when switching view mode (`Grid view/Event rendered view` dropdown in the table toolbar) to make sure the columns are updated correctly. <details> <summary> ## 🧪 Verification steps </summary> 1. Create Security rules that fire alerts 2. Navigate to Security Solution > Alerts 3. Try switching view mode `Grid view` <> `Event rendered view` one or more times, with page reloads in between too 4. After switching mode, try adding/removing columns to the table from the `Fields` toolbar menu 5. After editing the columns, try to reset to the default ones (`Fields` > `Reset fields`) </details> ## ⏪ Backport rationale Backporting to all branches where the issue occurs ## 🔗 References Fixes elastic#245257 ## Release Notes Fixes an issue that caused the Security alerts table to not update columns correctly when switching view mode ## ☑️ Checklist - [ ] ~~Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)~~ - [ ] ~~[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials~~ - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] ~~If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)~~ - [ ] ~~This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations.~~ - [ ] ~~[Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed~~ - [x] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [x] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. (cherry picked from commit 3a3d46c) # Conflicts: # x-pack/solutions/security/plugins/security_solution/public/detections/components/alerts_table/index.tsx
kibanamachine
added a commit
that referenced
this pull request
Dec 4, 2025
…iew mode columns correctly (#245253) (#245295) # Backport This will backport the following commits from `main` to `9.2`: - [[ResponseOps][Alerts] Fix Security alerts table not switching view mode columns correctly (#245253)](#245253) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Umberto Pepato","email":"umbopepato@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-12-04T17:51:08Z","message":"[ResponseOps][Alerts] Fix Security alerts table not switching view mode columns correctly (#245253)\n\n## 📄 Summary\n\nForces the Security AlertsTable to rerender entirely when switching view\nmode (`Grid view/Event rendered view` dropdown in the table toolbar) to\nmake sure the columns are updated correctly.\n\n<details>\n<summary>\n\n## 🧪 Verification steps\n\n</summary>\n\n1. Create Security rules that fire alerts\n2. Navigate to Security Solution > Alerts\n3. Try switching view mode `Grid view` <> `Event rendered view` one or\nmore times, with page reloads in between too\n4. After switching mode, try adding/removing columns to the table from\nthe `Fields` toolbar menu\n5. After editing the columns, try to reset to the default ones (`Fields`\n> `Reset fields`)\n\n</details>\n\n## ⏪ Backport rationale\n\nBackporting to all branches where the issue occurs\n\n## 🔗 References\n\nFixes #245257\n\n## Release Notes\n\nFixes an issue that caused the Security alerts table to not update\ncolumns correctly when switching view mode\n\n## ☑️ Checklist\n\n- [ ] ~~Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)~~\n- [ ]\n~~[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials~~\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] ~~If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)~~\n- [ ] ~~This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.~~\n- [ ] ~~[Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed~~\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [x] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.","sha":"3a3d46c1be1dbac5c7a647ffaabf37604fe455af","branchLabelMapping":{"^v9.3.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:ResponseOps","backport:version","v9.3.0","v9.2.3","v9.1.9","v8.19.9"],"title":"[ResponseOps][Alerts] Fix Security alerts table not switching view mode columns correctly","number":245253,"url":"https://github.com/elastic/kibana/pull/245253","mergeCommit":{"message":"[ResponseOps][Alerts] Fix Security alerts table not switching view mode columns correctly (#245253)\n\n## 📄 Summary\n\nForces the Security AlertsTable to rerender entirely when switching view\nmode (`Grid view/Event rendered view` dropdown in the table toolbar) to\nmake sure the columns are updated correctly.\n\n<details>\n<summary>\n\n## 🧪 Verification steps\n\n</summary>\n\n1. Create Security rules that fire alerts\n2. Navigate to Security Solution > Alerts\n3. Try switching view mode `Grid view` <> `Event rendered view` one or\nmore times, with page reloads in between too\n4. After switching mode, try adding/removing columns to the table from\nthe `Fields` toolbar menu\n5. After editing the columns, try to reset to the default ones (`Fields`\n> `Reset fields`)\n\n</details>\n\n## ⏪ Backport rationale\n\nBackporting to all branches where the issue occurs\n\n## 🔗 References\n\nFixes #245257\n\n## Release Notes\n\nFixes an issue that caused the Security alerts table to not update\ncolumns correctly when switching view mode\n\n## ☑️ Checklist\n\n- [ ] ~~Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)~~\n- [ ]\n~~[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials~~\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] ~~If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)~~\n- [ ] ~~This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.~~\n- [ ] ~~[Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed~~\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [x] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.","sha":"3a3d46c1be1dbac5c7a647ffaabf37604fe455af"}},"sourceBranch":"main","suggestedTargetBranches":["9.2","9.1","8.19"],"targetPullRequestStates":[{"branch":"main","label":"v9.3.0","branchLabelMappingKey":"^v9.3.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/245253","number":245253,"mergeCommit":{"message":"[ResponseOps][Alerts] Fix Security alerts table not switching view mode columns correctly (#245253)\n\n## 📄 Summary\n\nForces the Security AlertsTable to rerender entirely when switching view\nmode (`Grid view/Event rendered view` dropdown in the table toolbar) to\nmake sure the columns are updated correctly.\n\n<details>\n<summary>\n\n## 🧪 Verification steps\n\n</summary>\n\n1. Create Security rules that fire alerts\n2. Navigate to Security Solution > Alerts\n3. Try switching view mode `Grid view` <> `Event rendered view` one or\nmore times, with page reloads in between too\n4. After switching mode, try adding/removing columns to the table from\nthe `Fields` toolbar menu\n5. After editing the columns, try to reset to the default ones (`Fields`\n> `Reset fields`)\n\n</details>\n\n## ⏪ Backport rationale\n\nBackporting to all branches where the issue occurs\n\n## 🔗 References\n\nFixes #245257\n\n## Release Notes\n\nFixes an issue that caused the Security alerts table to not update\ncolumns correctly when switching view mode\n\n## ☑️ Checklist\n\n- [ ] ~~Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)~~\n- [ ]\n~~[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials~~\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] ~~If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)~~\n- [ ] ~~This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.~~\n- [ ] ~~[Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed~~\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [x] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.","sha":"3a3d46c1be1dbac5c7a647ffaabf37604fe455af"}},{"branch":"9.2","label":"v9.2.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.1","label":"v9.1.9","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.19","label":"v8.19.9","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Umberto Pepato <umbopepato@users.noreply.github.com>
PhilippeOberti
added a commit
that referenced
this pull request
Dec 4, 2025
…view mode columns correctly (#245253) (#245302) # Backport This will backport the following commits from `main` to `8.19`: - [[ResponseOps][Alerts] Fix Security alerts table not switching view mode columns correctly (#245253)](#245253) <!--- Backport version: 10.2.0 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Umberto Pepato","email":"umbopepato@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-12-04T17:51:08Z","message":"[ResponseOps][Alerts] Fix Security alerts table not switching view mode columns correctly (#245253)\n\n## 📄 Summary\n\nForces the Security AlertsTable to rerender entirely when switching view\nmode (`Grid view/Event rendered view` dropdown in the table toolbar) to\nmake sure the columns are updated correctly.\n\n<details>\n<summary>\n\n## 🧪 Verification steps\n\n</summary>\n\n1. Create Security rules that fire alerts\n2. Navigate to Security Solution > Alerts\n3. Try switching view mode `Grid view` <> `Event rendered view` one or\nmore times, with page reloads in between too\n4. After switching mode, try adding/removing columns to the table from\nthe `Fields` toolbar menu\n5. After editing the columns, try to reset to the default ones (`Fields`\n> `Reset fields`)\n\n</details>\n\n## ⏪ Backport rationale\n\nBackporting to all branches where the issue occurs\n\n## 🔗 References\n\nFixes #245257\n\n## Release Notes\n\nFixes an issue that caused the Security alerts table to not update\ncolumns correctly when switching view mode\n\n## ☑️ Checklist\n\n- [ ] ~~Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)~~\n- [ ]\n~~[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials~~\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] ~~If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)~~\n- [ ] ~~This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.~~\n- [ ] ~~[Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed~~\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [x] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.","sha":"3a3d46c1be1dbac5c7a647ffaabf37604fe455af","branchLabelMapping":{"^v9.3.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:ResponseOps","backport:version","v9.3.0","v9.2.3","v9.1.9","v8.19.9"],"title":"[ResponseOps][Alerts] Fix Security alerts table not switching view mode columns correctly","number":245253,"url":"https://github.com/elastic/kibana/pull/245253","mergeCommit":{"message":"[ResponseOps][Alerts] Fix Security alerts table not switching view mode columns correctly (#245253)\n\n## 📄 Summary\n\nForces the Security AlertsTable to rerender entirely when switching view\nmode (`Grid view/Event rendered view` dropdown in the table toolbar) to\nmake sure the columns are updated correctly.\n\n<details>\n<summary>\n\n## 🧪 Verification steps\n\n</summary>\n\n1. Create Security rules that fire alerts\n2. Navigate to Security Solution > Alerts\n3. Try switching view mode `Grid view` <> `Event rendered view` one or\nmore times, with page reloads in between too\n4. After switching mode, try adding/removing columns to the table from\nthe `Fields` toolbar menu\n5. After editing the columns, try to reset to the default ones (`Fields`\n> `Reset fields`)\n\n</details>\n\n## ⏪ Backport rationale\n\nBackporting to all branches where the issue occurs\n\n## 🔗 References\n\nFixes #245257\n\n## Release Notes\n\nFixes an issue that caused the Security alerts table to not update\ncolumns correctly when switching view mode\n\n## ☑️ Checklist\n\n- [ ] ~~Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)~~\n- [ ]\n~~[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials~~\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] ~~If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)~~\n- [ ] ~~This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.~~\n- [ ] ~~[Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed~~\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [x] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.","sha":"3a3d46c1be1dbac5c7a647ffaabf37604fe455af"}},"sourceBranch":"main","suggestedTargetBranches":["9.1","8.19"],"targetPullRequestStates":[{"branch":"main","label":"v9.3.0","branchLabelMappingKey":"^v9.3.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/245253","number":245253,"mergeCommit":{"message":"[ResponseOps][Alerts] Fix Security alerts table not switching view mode columns correctly (#245253)\n\n## 📄 Summary\n\nForces the Security AlertsTable to rerender entirely when switching view\nmode (`Grid view/Event rendered view` dropdown in the table toolbar) to\nmake sure the columns are updated correctly.\n\n<details>\n<summary>\n\n## 🧪 Verification steps\n\n</summary>\n\n1. Create Security rules that fire alerts\n2. Navigate to Security Solution > Alerts\n3. Try switching view mode `Grid view` <> `Event rendered view` one or\nmore times, with page reloads in between too\n4. After switching mode, try adding/removing columns to the table from\nthe `Fields` toolbar menu\n5. After editing the columns, try to reset to the default ones (`Fields`\n> `Reset fields`)\n\n</details>\n\n## ⏪ Backport rationale\n\nBackporting to all branches where the issue occurs\n\n## 🔗 References\n\nFixes #245257\n\n## Release Notes\n\nFixes an issue that caused the Security alerts table to not update\ncolumns correctly when switching view mode\n\n## ☑️ Checklist\n\n- [ ] ~~Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)~~\n- [ ]\n~~[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials~~\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] ~~If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)~~\n- [ ] ~~This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.~~\n- [ ] ~~[Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed~~\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [x] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.","sha":"3a3d46c1be1dbac5c7a647ffaabf37604fe455af"}},{"branch":"9.2","label":"v9.2.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/245295","number":245295,"state":"OPEN"},{"branch":"9.1","label":"v9.1.9","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.19","label":"v8.19.9","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Umberto Pepato <umbopepato@users.noreply.github.com>
PhilippeOberti
added a commit
that referenced
this pull request
Dec 4, 2025
…iew mode columns correctly (#245253) (#245301) # Backport This will backport the following commits from `main` to `9.1`: - [[ResponseOps][Alerts] Fix Security alerts table not switching view mode columns correctly (#245253)](#245253) <!--- Backport version: 10.2.0 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Umberto Pepato","email":"umbopepato@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-12-04T17:51:08Z","message":"[ResponseOps][Alerts] Fix Security alerts table not switching view mode columns correctly (#245253)\n\n## 📄 Summary\n\nForces the Security AlertsTable to rerender entirely when switching view\nmode (`Grid view/Event rendered view` dropdown in the table toolbar) to\nmake sure the columns are updated correctly.\n\n<details>\n<summary>\n\n## 🧪 Verification steps\n\n</summary>\n\n1. Create Security rules that fire alerts\n2. Navigate to Security Solution > Alerts\n3. Try switching view mode `Grid view` <> `Event rendered view` one or\nmore times, with page reloads in between too\n4. After switching mode, try adding/removing columns to the table from\nthe `Fields` toolbar menu\n5. After editing the columns, try to reset to the default ones (`Fields`\n> `Reset fields`)\n\n</details>\n\n## ⏪ Backport rationale\n\nBackporting to all branches where the issue occurs\n\n## 🔗 References\n\nFixes #245257\n\n## Release Notes\n\nFixes an issue that caused the Security alerts table to not update\ncolumns correctly when switching view mode\n\n## ☑️ Checklist\n\n- [ ] ~~Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)~~\n- [ ]\n~~[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials~~\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] ~~If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)~~\n- [ ] ~~This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.~~\n- [ ] ~~[Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed~~\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [x] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.","sha":"3a3d46c1be1dbac5c7a647ffaabf37604fe455af","branchLabelMapping":{"^v9.3.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:ResponseOps","backport:version","v9.3.0","v9.2.3","v9.1.9","v8.19.9"],"title":"[ResponseOps][Alerts] Fix Security alerts table not switching view mode columns correctly","number":245253,"url":"https://github.com/elastic/kibana/pull/245253","mergeCommit":{"message":"[ResponseOps][Alerts] Fix Security alerts table not switching view mode columns correctly (#245253)\n\n## 📄 Summary\n\nForces the Security AlertsTable to rerender entirely when switching view\nmode (`Grid view/Event rendered view` dropdown in the table toolbar) to\nmake sure the columns are updated correctly.\n\n<details>\n<summary>\n\n## 🧪 Verification steps\n\n</summary>\n\n1. Create Security rules that fire alerts\n2. Navigate to Security Solution > Alerts\n3. Try switching view mode `Grid view` <> `Event rendered view` one or\nmore times, with page reloads in between too\n4. After switching mode, try adding/removing columns to the table from\nthe `Fields` toolbar menu\n5. After editing the columns, try to reset to the default ones (`Fields`\n> `Reset fields`)\n\n</details>\n\n## ⏪ Backport rationale\n\nBackporting to all branches where the issue occurs\n\n## 🔗 References\n\nFixes #245257\n\n## Release Notes\n\nFixes an issue that caused the Security alerts table to not update\ncolumns correctly when switching view mode\n\n## ☑️ Checklist\n\n- [ ] ~~Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)~~\n- [ ]\n~~[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials~~\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] ~~If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)~~\n- [ ] ~~This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.~~\n- [ ] ~~[Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed~~\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [x] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.","sha":"3a3d46c1be1dbac5c7a647ffaabf37604fe455af"}},"sourceBranch":"main","suggestedTargetBranches":["9.1","8.19"],"targetPullRequestStates":[{"branch":"main","label":"v9.3.0","branchLabelMappingKey":"^v9.3.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/245253","number":245253,"mergeCommit":{"message":"[ResponseOps][Alerts] Fix Security alerts table not switching view mode columns correctly (#245253)\n\n## 📄 Summary\n\nForces the Security AlertsTable to rerender entirely when switching view\nmode (`Grid view/Event rendered view` dropdown in the table toolbar) to\nmake sure the columns are updated correctly.\n\n<details>\n<summary>\n\n## 🧪 Verification steps\n\n</summary>\n\n1. Create Security rules that fire alerts\n2. Navigate to Security Solution > Alerts\n3. Try switching view mode `Grid view` <> `Event rendered view` one or\nmore times, with page reloads in between too\n4. After switching mode, try adding/removing columns to the table from\nthe `Fields` toolbar menu\n5. After editing the columns, try to reset to the default ones (`Fields`\n> `Reset fields`)\n\n</details>\n\n## ⏪ Backport rationale\n\nBackporting to all branches where the issue occurs\n\n## 🔗 References\n\nFixes #245257\n\n## Release Notes\n\nFixes an issue that caused the Security alerts table to not update\ncolumns correctly when switching view mode\n\n## ☑️ Checklist\n\n- [ ] ~~Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)~~\n- [ ]\n~~[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials~~\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] ~~If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)~~\n- [ ] ~~This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.~~\n- [ ] ~~[Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed~~\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [x] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.","sha":"3a3d46c1be1dbac5c7a647ffaabf37604fe455af"}},{"branch":"9.2","label":"v9.2.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/245295","number":245295,"state":"OPEN"},{"branch":"9.1","label":"v9.1.9","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.19","label":"v8.19.9","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Umberto Pepato <umbopepato@users.noreply.github.com>
3 tasks
PhilippeOberti
added a commit
that referenced
this pull request
Dec 5, 2025
## Summary A [recent PR](#245253) fixed an issue with the alerts table that was not properly switching between grid view and event rendered view. This PR unskips the Cypress tests related to testing the event rendered view in our alerts page alerts table. <img width="639" height="273" alt="Screenshot 2025-12-04 at 4 42 06 PM" src="https://github.com/user-attachments/assets/510a6de3-ccbc-4268-96fd-2ced9c6cb45d" /> Flaky test runner: https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/10002 ### Checklist - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [x] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [x] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. #236608
JordanSh
pushed a commit
to JordanSh/kibana
that referenced
this pull request
Dec 9, 2025
…de columns correctly (elastic#245253) ## 📄 Summary Forces the Security AlertsTable to rerender entirely when switching view mode (`Grid view/Event rendered view` dropdown in the table toolbar) to make sure the columns are updated correctly. <details> <summary> ## 🧪 Verification steps </summary> 1. Create Security rules that fire alerts 2. Navigate to Security Solution > Alerts 3. Try switching view mode `Grid view` <> `Event rendered view` one or more times, with page reloads in between too 4. After switching mode, try adding/removing columns to the table from the `Fields` toolbar menu 5. After editing the columns, try to reset to the default ones (`Fields` > `Reset fields`) </details> ## ⏪ Backport rationale Backporting to all branches where the issue occurs ## 🔗 References Fixes elastic#245257 ## Release Notes Fixes an issue that caused the Security alerts table to not update columns correctly when switching view mode ## ☑️ Checklist - [ ] ~~Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)~~ - [ ] ~~[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials~~ - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] ~~If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)~~ - [ ] ~~This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations.~~ - [ ] ~~[Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed~~ - [x] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [x] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels.
JordanSh
pushed a commit
to JordanSh/kibana
that referenced
this pull request
Dec 9, 2025
…#245312) ## Summary A [recent PR](elastic#245253) fixed an issue with the alerts table that was not properly switching between grid view and event rendered view. This PR unskips the Cypress tests related to testing the event rendered view in our alerts page alerts table. <img width="639" height="273" alt="Screenshot 2025-12-04 at 4 42 06 PM" src="https://github.com/user-attachments/assets/510a6de3-ccbc-4268-96fd-2ced9c6cb45d" /> Flaky test runner: https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/10002 ### Checklist - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [x] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [x] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. elastic#236608
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
📄 Summary
Forces the Security AlertsTable to rerender entirely when switching view mode (
Grid view/Event rendered viewdropdown in the table toolbar) to make sure the columns are updated correctly.🧪 Verification steps
Grid view<>Event rendered viewone or more times, with page reloads in between tooFieldstoolbar menuFields>Reset fields)⏪ Backport rationale
Backporting to all branches where the issue occurs
🔗 References
Fixes #245257
Release Notes
Fixes an issue that caused the Security alerts table to not update columns correctly when switching view mode
☑️ Checklist
Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n supportDocumentation was added for features that require explanation or tutorialsIf a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker listThis was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. Therelease_note:breakinglabel should be applied in these situations.Flaky Test Runner was used on any tests changedrelease_note:*label is applied per the guidelinesbackport:*labels.