[Security Solution] Fix toggle column not working from anywhere but the alerts page

[PhilippeOberti]

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.

Alerts page remains unchanged

Before fix

alerts-before.mov

After fix

alerts-after.mov

Timeline remains unchanged

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

Explore pages remain unchanged

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

After fix

explore-after.mov

Case details page is fixed

Before fix

case-before.mov

After fix

case-after.mov

Rule details page is fixed

Before fix

rule-before.mov

After fix

rule-after.mov

Attack discovery page is fixed

Before fix

attack.discovery-before.mov

After fix

attack.discovery-after.mov

Checklist

• Unit or functional tests were updated or added to match the most common scenarios
• The PR description includes the appropriate Release Notes section, and the correct release_note:* label is applied per the guidelines
• Review the backport guidelines and apply applicable backport:* labels.

#234223

[elasticmachine]

Pinging @elastic/security-threat-hunting-investigations (Team:Threat Hunting:Investigations)

[NicholasPeretti]

Great stuff! Thanks for taking care of this 😄

I've left one minor comment, let me know what you think! ☺️

[kibanamachine]

Starting backport for target branches: 8.18, 8.19, 9.0, 9.1

https://github.com/elastic/kibana/actions/runs/17568280355

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 2fcd21b

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	10.3MB	10.3MB	-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
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			-246

History

• 💔 Build #336734 failed 9625f5b

[kibanamachine]

💔 Some backports could not be created

Status	Branch	Result
❌	8.18	Backport failed because of merge conflicts
✅	8.19
❌	9.0	Backport failed because of merge conflicts
✅	9.1

Note: Successful backport PRs will be merged automatically after passing CI.

Manual backport

To create the backport manually run:

node scripts/backport --pr 234278

Questions ?

Please refer to the Backport tool documentation

[PhilippeOberti]

I'm removing the 8.18 and 9.0 labels as the issue does not happen there. The bug was most likely introduced by this PR which was merged to 9.1 and successfully backported to 8.19.
While the PR also says that it was backported to 9.0, looking a bit closer shows that the backport to 9.0 was rejected.