Skip to content

[8.19] [Security Solution] Fix toggle column not working from anywhere but the alerts page (#234278)#234379

Merged
kibanamachine merged 1 commit intoelastic:8.19from
kibanamachine:backport/8.19/pr-234278
Sep 9, 2025
Merged

[8.19] [Security Solution] Fix toggle column not working from anywhere but the alerts page (#234278)#234379
kibanamachine merged 1 commit intoelastic:8.19from
kibanamachine:backport/8.19/pr-234278

Conversation

@kibanamachine
Copy link
Copy Markdown
Contributor

Backport

This will backport the following commits from main to 8.19:

Questions ?

Please refer to the Backport tool documentation

…he alerts page (elastic#234278)

## Summary

This PR fixes an issue related to the alert flyout toggle column
functionality not working anywhere but from the alerts page.

We noticed in the code that we when toggling on/off columns, were
filtering out all the usages of the alerts table that were not the
alerts page. This means that the rule details, case details, attack
discovery and entity analytics pages had a bug where the toggle column
cell actions was not working.

<details>
<summary>Alerts page remains unchanged</summary>

Before fix

https://github.com/user-attachments/assets/f713e70a-8a13-452c-8b9c-c468448b967a

After fix

https://github.com/user-attachments/assets/7383783e-69a8-452c-9d83-ad8d6e2a1565

</details>

<details>
<summary>Timeline remains unchanged</summary>

Before fix
| Before fix  | After fix |
| ------------- | ------------- |
|
https://github.com/user-attachments/assets/6088856d-f884-4a2e-819e-a6df12b31fbc
|
https://github.com/user-attachments/assets/4916b382-54fc-4210-9576-11cc8ebc2f2e
|

</details>

<details>
<summary>Explore pages remain unchanged</summary>

Before fix

https://github.com/user-attachments/assets/8c42e3f2-ab26-4632-9bba-e1c7f8957b6e

After fix

https://github.com/user-attachments/assets/69561c31-f69c-4ef9-9d8e-a7862e634e0b

</details>

<details>
<summary>Case details page is fixed</summary>

Before fix

https://github.com/user-attachments/assets/9a73f413-606e-4245-b827-023677130d2b

After fix

https://github.com/user-attachments/assets/b7c0827a-4abc-4824-9b9e-8b86f545de17

</details>

<details>
<summary>Rule details page is fixed</summary>

Before fix

https://github.com/user-attachments/assets/560ddf58-7047-4258-aa21-6fd5bdb5e285

After fix

https://github.com/user-attachments/assets/1d41244a-5482-4833-8887-d883a9f537be

</details>

<details>
<summary>Attack discovery page is fixed</summary>

Before fix

https://github.com/user-attachments/assets/692e9af4-4cd8-4cb5-ac86-ce99706f6d37

After fix

https://github.com/user-attachments/assets/5984c404-9d6b-4c1e-9af3-0877bd660024

</details>

### Checklist

- [x] [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
- [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#234223
(cherry picked from commit 890f7e9)
@kibanamachine kibanamachine added the backport This PR is a backport of another PR label Sep 9, 2025
@kibanamachine kibanamachine enabled auto-merge (squash) September 9, 2025 00:56
@kibanamachine kibanamachine merged commit 1d3f117 into elastic:8.19 Sep 9, 2025
11 checks passed
@elasticmachine
Copy link
Copy Markdown
Contributor

💚 Build Succeeded

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id before after diff
securitySolution 9.4MB 9.4MB -41.0B

Saved Objects .kibana field count

Every field in each saved object type adds overhead to Elasticsearch. Kibana needs to keep the total field count below Elasticsearch's default limit of 1000 fields. Only specify field mappings for the fields you wish to search on or query. See https://www.elastic.co/guide/en/kibana/master/saved-objects-service.html#_mappings

id before after diff
_data_stream_timestamp 1 - -1
_doc_count 1 - -1
_ignored_source 1 - -1
_index_mode 1 - -1
_inference_fields 1 - -1
_tier 1 - -1
apm-custom-dashboards 5 - -5
apm-server-schema 2 - -2
apm-service-group 5 - -5
application_usage_daily 2 - -2
config 2 - -2
config-global 2 - -2
coreMigrationVersion 1 - -1
created_at 1 - -1
created_by 1 - -1
entity-definition 9 - -9
entity-discovery-api-key 2 - -2
event_loop_delays_daily 2 - -2
favorites 4 - -4
file 11 - -11
file-upload-usage-collection-telemetry 3 - -3
fileShare 5 - -5
guided-onboarding-guide-state 3 - -3
infra-custom-dashboards 4 - -4
infrastructure-monitoring-log-view 2 - -2
intercept_trigger_record 5 - -5
legacy-url-alias 7 - -7
managed 1 - -1
ml-job 6 - -6
ml-module 13 - -13
ml-trained-model 7 - -7
monitoring-telemetry 2 - -2
namespace 1 - -1
namespaces 1 - -1
observability-onboarding-state 2 - -2
originId 1 - -1
product-doc-install-status 7 - -7
references 4 - -4
sample-data-telemetry 3 - -3
security-ai-prompt 8 - -8
slo 11 - -11
space 5 - -5
synthetics-monitor 34 - -34
synthetics-monitor-multi-space 34 - -34
tag 4 - -4
type 1 - -1
typeMigrationVersion 1 - -1
ui-metric 2 - -2
updated_at 1 - -1
updated_by 1 - -1
upgrade-assistant-ml-upgrade-operation 3 - -3
upgrade-assistant-reindex-operation 3 - -3
uptime-synthetics-api-key 2 - -2
url 5 - -5
usage-counters 2 - -2
total -249

cc @PhilippeOberti

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport This PR is a backport of another PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants