# Backport
This will backport the following commits from `main` to `8.x`:
- [[ML] Add Spaces column to Anomaly Detection, Data Frame Analytics and
Trained Models management pages
(#206696)](https://github.com/elastic/kibana/pull/206696)
<!--- Backport version: 9.4.3 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT [{"author":{"name":"Quynh Nguyen
(Quinn)","email":"43350163+qn895@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-01-28T23:12:17Z","message":"[ML]
Add Spaces column to Anomaly Detection, Data Frame Analytics and Trained
Models management pages (#206696)\n\n## Summary\r\n\r\nThis PR adds a
new `Spaces` column to Anomaly detection, Data Frame\r\nAnalytics, and
Trained Models tables for management of
spaces.\r\n\r\n\r\n\r\n85f9be3a-a56e-4ba8-9bcf-06f2b8e01cf7\r\n\r\nIf
user does not have permission to share to other spaces, the
spaces\r\nbutton will be disabled
completely.\r\n\r\n\r\n\r\nhttps://github.com/user-attachments/assets/8c188240-9adf-439b-a6ea-5ad2b4c3ad0a\r\n\r\n**Reviewer's
note:**\r\n\r\n- For kibana-security: A small change in the hook was
updated to fix an\r\nerror with component set state after
unmounting\r\n\r\n\r\n\r\n\r\n### Checklist\r\n\r\n\r\n\r\nCheck the PR
satisfies following conditions. \r\n\r\nReviewers should verify this PR
satisfies this list as well.\r\n\r\n- [ ] Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\r\n-
[
]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas
added for features that require explanation or tutorials\r\n- [ ] [Unit
or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n- [ ] If a plugin
configuration key changed, check if it needs to be\r\nallowlisted in the
cloud and added to the
[docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n-
[ ] This was checked for breaking HTTP API changes, and any
breaking\r\nchanges have been approved by the breaking-change committee.
The\r\n`release_note:breaking` label should be applied in these
situations.\r\n- [ ] [Flaky
Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\r\nused on any tests changed\r\n- [ ] The PR description includes
the appropriate Release Notes section,\r\nand the correct
`release_note:*` label is applied per
the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n###
Identify risks\r\n\r\nDoes this PR introduce any risks? For example,
consider risks like hard\r\nto test bugs, performance regression,
potential of data loss.\r\n\r\nDescribe the risk, its severity, and
mitigation for each identified\r\nrisk. Invite stakeholders and evaluate
how to proceed before merging.\r\n\r\n- [ ] [See some
risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\r\n-
[ ] ...\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"b5de0a7fc4a240c3d73c747b77768bbc401a5a14","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement",":ml","Feature:Anomaly
Detection","Feature:Data Frame
Analytics","v9.0.0","backport:version","v8.18.0"],"title":"[ML] Add
Spaces column to Anomaly Detection, Data Frame Analytics and Trained
Models management
pages","number":206696,"url":"https://github.com/elastic/kibana/pull/206696","mergeCommit":{"message":"[ML]
Add Spaces column to Anomaly Detection, Data Frame Analytics and Trained
Models management pages (#206696)\n\n## Summary\r\n\r\nThis PR adds a
new `Spaces` column to Anomaly detection, Data Frame\r\nAnalytics, and
Trained Models tables for management of
spaces.\r\n\r\n\r\n\r\n85f9be3a-a56e-4ba8-9bcf-06f2b8e01cf7\r\n\r\nIf
user does not have permission to share to other spaces, the
spaces\r\nbutton will be disabled
completely.\r\n\r\n\r\n\r\nhttps://github.com/user-attachments/assets/8c188240-9adf-439b-a6ea-5ad2b4c3ad0a\r\n\r\n**Reviewer's
note:**\r\n\r\n- For kibana-security: A small change in the hook was
updated to fix an\r\nerror with component set state after
unmounting\r\n\r\n\r\n\r\n\r\n### Checklist\r\n\r\n\r\n\r\nCheck the PR
satisfies following conditions. \r\n\r\nReviewers should verify this PR
satisfies this list as well.\r\n\r\n- [ ] Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\r\n-
[
]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas
added for features that require explanation or tutorials\r\n- [ ] [Unit
or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n- [ ] If a plugin
configuration key changed, check if it needs to be\r\nallowlisted in the
cloud and added to the
[docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n-
[ ] This was checked for breaking HTTP API changes, and any
breaking\r\nchanges have been approved by the breaking-change committee.
The\r\n`release_note:breaking` label should be applied in these
situations.\r\n- [ ] [Flaky
Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\r\nused on any tests changed\r\n- [ ] The PR description includes
the appropriate Release Notes section,\r\nand the correct
`release_note:*` label is applied per
the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n###
Identify risks\r\n\r\nDoes this PR introduce any risks? For example,
consider risks like hard\r\nto test bugs, performance regression,
potential of data loss.\r\n\r\nDescribe the risk, its severity, and
mitigation for each identified\r\nrisk. Invite stakeholders and evaluate
how to proceed before merging.\r\n\r\n- [ ] [See some
risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\r\n-
[ ] ...\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"b5de0a7fc4a240c3d73c747b77768bbc401a5a14"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/206696","number":206696,"mergeCommit":{"message":"[ML]
Add Spaces column to Anomaly Detection, Data Frame Analytics and Trained
Models management pages (#206696)\n\n## Summary\r\n\r\nThis PR adds a
new `Spaces` column to Anomaly detection, Data Frame\r\nAnalytics, and
Trained Models tables for management of
spaces.\r\n\r\n\r\n\r\n85f9be3a-a56e-4ba8-9bcf-06f2b8e01cf7\r\n\r\nIf
user does not have permission to share to other spaces, the
spaces\r\nbutton will be disabled
completely.\r\n\r\n\r\n\r\nhttps://github.com/user-attachments/assets/8c188240-9adf-439b-a6ea-5ad2b4c3ad0a\r\n\r\n**Reviewer's
note:**\r\n\r\n- For kibana-security: A small change in the hook was
updated to fix an\r\nerror with component set state after
unmounting\r\n\r\n\r\n\r\n\r\n### Checklist\r\n\r\n\r\n\r\nCheck the PR
satisfies following conditions. \r\n\r\nReviewers should verify this PR
satisfies this list as well.\r\n\r\n- [ ] Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\r\n-
[
]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas
added for features that require explanation or tutorials\r\n- [ ] [Unit
or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n- [ ] If a plugin
configuration key changed, check if it needs to be\r\nallowlisted in the
cloud and added to the
[docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n-
[ ] This was checked for breaking HTTP API changes, and any
breaking\r\nchanges have been approved by the breaking-change committee.
The\r\n`release_note:breaking` label should be applied in these
situations.\r\n- [ ] [Flaky
Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\r\nused on any tests changed\r\n- [ ] The PR description includes
the appropriate Release Notes section,\r\nand the correct
`release_note:*` label is applied per
the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n###
Identify risks\r\n\r\nDoes this PR introduce any risks? For example,
consider risks like hard\r\nto test bugs, performance regression,
potential of data loss.\r\n\r\nDescribe the risk, its severity, and
mitigation for each identified\r\nrisk. Invite stakeholders and evaluate
how to proceed before merging.\r\n\r\n- [ ] [See some
risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\r\n-
[ ] ...\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"b5de0a7fc4a240c3d73c747b77768bbc401a5a14"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
Co-authored-by: Quynh Nguyen (Quinn) <43350163+qn895@users.noreply.github.com>
These tests take a while so they have been broken up into groups with their own config.ts and index.ts file, causing each of these groups to be independent bundles of tests which can be run on some worker in CI without taking an incredible amount of time.
Want to change the groups to something more logical? Have fun! Just make sure that each group executes on CI in less than 10 minutes or so. We don't currently have any mechanism for validating this right now, you just need to look at the times in the log output on CI, but we'll be working on tooling for making this information more accessible soon.
b65acc7c66