[Spaces] Excluded deprecated features from solution visibility#230385
Merged
elena-shostak merged 3 commits intoelastic:mainfrom Aug 5, 2025
Merged
[Spaces] Excluded deprecated features from solution visibility#230385elena-shostak merged 3 commits intoelastic:mainfrom
elena-shostak merged 3 commits intoelastic:mainfrom
Conversation
Contributor
💛 Build succeeded, but was flaky
Failed CI StepsMetrics [docs]
History
|
Contributor
|
Pinging @elastic/kibana-security (Team:Security) |
SiddharthMantri
approved these changes
Aug 5, 2025
Contributor
|
Starting backport for target branches: 8.17, 8.18, 8.19, 9.1 |
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Aug 5, 2025
…ic#230385) ## Summary Excluded deprecated features from solution visibility. ## How to test 1. Change the solution from `classic` to `observability` for the very first time in the default space. Make sure the response of the active space `GET internal/spaces/_active_space` doesn't contain deprecated features. (`siem`, `siemV2`, `securitySolutionCases` and `securitySolutionCasesV2` were deprecated, so only `siemV3` and `securitySolutionCasesV3` should be on the list) ``` { "id": "default", "name": "Default", "description": "This is your default space!", "color": "#00bfb3", "initials": "D", "imageUrl": "", "disabledFeatures": [ "siemV3", "securitySolutionCasesV3", "securitySolutionAssistant", "securitySolutionAttackDiscovery", "securitySolutionTimeline", "securitySolutionNotes", "securitySolutionSiemMigrations" ], "_reserved": true, "solution": "oblt" } ``` 2. Change the solution back to `classic` and enable all security features. <img width="1252" height="540" alt="Screenshot 2025-08-04 at 12 35 36" src="https://github.com/user-attachments/assets/bf0db3df-362f-4814-8fc8-2be3b6c8740c" /> 3. Update the space and go back to Edit Space page. 3. Make sure the enabled features counter is correctly displayed in the UI. ### 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. __Fixes: https://github.com/elastic/kibana/issues/220743__ ## Release Note Excluded deprecated features from spaces solution visibility. (cherry picked from commit 81f252c)
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 |
elena-shostak
added a commit
to elena-shostak/kibana
that referenced
this pull request
Aug 5, 2025
…ic#230385) ## Summary Excluded deprecated features from solution visibility. ## How to test 1. Change the solution from `classic` to `observability` for the very first time in the default space. Make sure the response of the active space `GET internal/spaces/_active_space` doesn't contain deprecated features. (`siem`, `siemV2`, `securitySolutionCases` and `securitySolutionCasesV2` were deprecated, so only `siemV3` and `securitySolutionCasesV3` should be on the list) ``` { "id": "default", "name": "Default", "description": "This is your default space!", "color": "#00bfb3", "initials": "D", "imageUrl": "", "disabledFeatures": [ "siemV3", "securitySolutionCasesV3", "securitySolutionAssistant", "securitySolutionAttackDiscovery", "securitySolutionTimeline", "securitySolutionNotes", "securitySolutionSiemMigrations" ], "_reserved": true, "solution": "oblt" } ``` 2. Change the solution back to `classic` and enable all security features. <img width="1252" height="540" alt="Screenshot 2025-08-04 at 12 35 36" src="https://github.com/user-attachments/assets/bf0db3df-362f-4814-8fc8-2be3b6c8740c" /> 3. Update the space and go back to Edit Space page. 3. Make sure the enabled features counter is correctly displayed in the UI. ### 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. __Fixes: https://github.com/elastic/kibana/issues/220743__ ## Release Note Excluded deprecated features from spaces solution visibility. (cherry picked from commit 81f252c) # Conflicts: # x-pack/platform/plugins/shared/spaces/server/lib/utils/space_solution_disabled_features.test.ts # x-pack/platform/test/spaces_api_integration/common/suites/create.ts # x-pack/platform/test/spaces_api_integration/common/suites/get.ts # x-pack/platform/test/spaces_api_integration/common/suites/get_all.ts
elena-shostak
added a commit
to elena-shostak/kibana
that referenced
this pull request
Aug 5, 2025
…ic#230385) ## Summary Excluded deprecated features from solution visibility. ## How to test 1. Change the solution from `classic` to `observability` for the very first time in the default space. Make sure the response of the active space `GET internal/spaces/_active_space` doesn't contain deprecated features. (`siem`, `siemV2`, `securitySolutionCases` and `securitySolutionCasesV2` were deprecated, so only `siemV3` and `securitySolutionCasesV3` should be on the list) ``` { "id": "default", "name": "Default", "description": "This is your default space!", "color": "#00bfb3", "initials": "D", "imageUrl": "", "disabledFeatures": [ "siemV3", "securitySolutionCasesV3", "securitySolutionAssistant", "securitySolutionAttackDiscovery", "securitySolutionTimeline", "securitySolutionNotes", "securitySolutionSiemMigrations" ], "_reserved": true, "solution": "oblt" } ``` 2. Change the solution back to `classic` and enable all security features. <img width="1252" height="540" alt="Screenshot 2025-08-04 at 12 35 36" src="https://github.com/user-attachments/assets/bf0db3df-362f-4814-8fc8-2be3b6c8740c" /> 3. Update the space and go back to Edit Space page. 3. Make sure the enabled features counter is correctly displayed in the UI. ### 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. __Fixes: https://github.com/elastic/kibana/issues/220743__ ## Release Note Excluded deprecated features from spaces solution visibility. (cherry picked from commit 81f252c) # Conflicts: # x-pack/platform/plugins/shared/spaces/server/lib/utils/space_solution_disabled_features.test.ts # x-pack/test/spaces_api_integration/common/suites/create.ts # x-pack/test/spaces_api_integration/common/suites/get.ts # x-pack/test/spaces_api_integration/common/suites/get_all.ts
Contributor
Author
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
elena-shostak
added a commit
to elena-shostak/kibana
that referenced
this pull request
Aug 5, 2025
…ic#230385) ## Summary Excluded deprecated features from solution visibility. ## How to test 1. Change the solution from `classic` to `observability` for the very first time in the default space. Make sure the response of the active space `GET internal/spaces/_active_space` doesn't contain deprecated features. (`siem`, `siemV2`, `securitySolutionCases` and `securitySolutionCasesV2` were deprecated, so only `siemV3` and `securitySolutionCasesV3` should be on the list) ``` { "id": "default", "name": "Default", "description": "This is your default space!", "color": "#00bfb3", "initials": "D", "imageUrl": "", "disabledFeatures": [ "siemV3", "securitySolutionCasesV3", "securitySolutionAssistant", "securitySolutionAttackDiscovery", "securitySolutionTimeline", "securitySolutionNotes", "securitySolutionSiemMigrations" ], "_reserved": true, "solution": "oblt" } ``` 2. Change the solution back to `classic` and enable all security features. <img width="1252" height="540" alt="Screenshot 2025-08-04 at 12 35 36" src="https://github.com/user-attachments/assets/bf0db3df-362f-4814-8fc8-2be3b6c8740c" /> 3. Update the space and go back to Edit Space page. 3. Make sure the enabled features counter is correctly displayed in the UI. ### 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. __Fixes: https://github.com/elastic/kibana/issues/220743__ ## Release Note Excluded deprecated features from spaces solution visibility. (cherry picked from commit 81f252c) # Conflicts: # x-pack/plugins/spaces/server/lib/utils/space_solution_disabled_features.test.ts # x-pack/test/spaces_api_integration/common/suites/create.ts # x-pack/test/spaces_api_integration/common/suites/get.ts # x-pack/test/spaces_api_integration/common/suites/get_all.ts
elena-shostak
added a commit
to elena-shostak/kibana
that referenced
this pull request
Aug 5, 2025
…ic#230385) ## Summary Excluded deprecated features from solution visibility. ## How to test 1. Change the solution from `classic` to `observability` for the very first time in the default space. Make sure the response of the active space `GET internal/spaces/_active_space` doesn't contain deprecated features. (`siem`, `siemV2`, `securitySolutionCases` and `securitySolutionCasesV2` were deprecated, so only `siemV3` and `securitySolutionCasesV3` should be on the list) ``` { "id": "default", "name": "Default", "description": "This is your default space!", "color": "#00bfb3", "initials": "D", "imageUrl": "", "disabledFeatures": [ "siemV3", "securitySolutionCasesV3", "securitySolutionAssistant", "securitySolutionAttackDiscovery", "securitySolutionTimeline", "securitySolutionNotes", "securitySolutionSiemMigrations" ], "_reserved": true, "solution": "oblt" } ``` 2. Change the solution back to `classic` and enable all security features. <img width="1252" height="540" alt="Screenshot 2025-08-04 at 12 35 36" src="https://github.com/user-attachments/assets/bf0db3df-362f-4814-8fc8-2be3b6c8740c" /> 3. Update the space and go back to Edit Space page. 3. Make sure the enabled features counter is correctly displayed in the UI. ### 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. __Fixes: https://github.com/elastic/kibana/issues/220743__ ## Release Note Excluded deprecated features from spaces solution visibility. (cherry picked from commit 81f252c) # Conflicts: # x-pack/platform/plugins/shared/spaces/server/lib/utils/space_solution_disabled_features.test.ts # x-pack/test/spaces_api_integration/common/suites/create.agnostic.ts # x-pack/test/spaces_api_integration/common/suites/get.agnostic.ts # x-pack/test/spaces_api_integration/common/suites/get_all.agnostic.ts
Contributor
Author
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
kibanamachine
added a commit
that referenced
this pull request
Aug 5, 2025
…230385) (#230511) # Backport This will backport the following commits from `main` to `9.1`: - [[Spaces] Excluded deprecated features from solution visibility (#230385)](#230385) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Elena Shostak","email":"165678770+elena-shostak@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-08-05T08:52:39Z","message":"[Spaces] Excluded deprecated features from solution visibility (#230385)\n\n## Summary\n\nExcluded deprecated features from solution visibility.\n\n## How to test\n1. Change the solution from `classic` to `observability` for the very\nfirst time in the default space.\nMake sure the response of the active space `GET\ninternal/spaces/_active_space` doesn't contain deprecated features.\n(`siem`, `siemV2`, `securitySolutionCases` and `securitySolutionCasesV2`\nwere deprecated, so only `siemV3` and `securitySolutionCasesV3` should\nbe on the list)\n```\n{\n \"id\": \"default\",\n \"name\": \"Default\",\n \"description\": \"This is your default space!\",\n \"color\": \"#00bfb3\",\n \"initials\": \"D\",\n \"imageUrl\": \"\",\n \"disabledFeatures\": [\n \"siemV3\",\n \"securitySolutionCasesV3\",\n \"securitySolutionAssistant\",\n \"securitySolutionAttackDiscovery\",\n \"securitySolutionTimeline\",\n \"securitySolutionNotes\",\n \"securitySolutionSiemMigrations\"\n ],\n \"_reserved\": true,\n \"solution\": \"oblt\"\n} \n```\n2. Change the solution back to `classic` and enable all security\nfeatures.\n<img width=\"1252\" height=\"540\" alt=\"Screenshot 2025-08-04 at 12 35 36\"\nsrc=\"https://github.com/user-attachments/assets/bf0db3df-362f-4814-8fc8-2be3b6c8740c\"\n/>\n3. Update the space and go back to Edit Space page.\n3. Make sure the enabled features counter is correctly displayed in the\nUI.\n\n### Checklist\n\n- [x] [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- [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.\n\n\n__Fixes: https://github.com/elastic/kibana/issues/220743__\n\n\n## Release Note\nExcluded deprecated features from spaces solution visibility.","sha":"81f252c02d076b83d795ffadb9030e43ed09c0fb","branchLabelMapping":{"^v9.2.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Security","Feature:Security/Spaces","backport:prev-minor","backport:prev-major","v9.2.0"],"title":"[Spaces] Excluded deprecated features from solution visibility","number":230385,"url":"https://github.com/elastic/kibana/pull/230385","mergeCommit":{"message":"[Spaces] Excluded deprecated features from solution visibility (#230385)\n\n## Summary\n\nExcluded deprecated features from solution visibility.\n\n## How to test\n1. Change the solution from `classic` to `observability` for the very\nfirst time in the default space.\nMake sure the response of the active space `GET\ninternal/spaces/_active_space` doesn't contain deprecated features.\n(`siem`, `siemV2`, `securitySolutionCases` and `securitySolutionCasesV2`\nwere deprecated, so only `siemV3` and `securitySolutionCasesV3` should\nbe on the list)\n```\n{\n \"id\": \"default\",\n \"name\": \"Default\",\n \"description\": \"This is your default space!\",\n \"color\": \"#00bfb3\",\n \"initials\": \"D\",\n \"imageUrl\": \"\",\n \"disabledFeatures\": [\n \"siemV3\",\n \"securitySolutionCasesV3\",\n \"securitySolutionAssistant\",\n \"securitySolutionAttackDiscovery\",\n \"securitySolutionTimeline\",\n \"securitySolutionNotes\",\n \"securitySolutionSiemMigrations\"\n ],\n \"_reserved\": true,\n \"solution\": \"oblt\"\n} \n```\n2. Change the solution back to `classic` and enable all security\nfeatures.\n<img width=\"1252\" height=\"540\" alt=\"Screenshot 2025-08-04 at 12 35 36\"\nsrc=\"https://github.com/user-attachments/assets/bf0db3df-362f-4814-8fc8-2be3b6c8740c\"\n/>\n3. Update the space and go back to Edit Space page.\n3. Make sure the enabled features counter is correctly displayed in the\nUI.\n\n### Checklist\n\n- [x] [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- [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.\n\n\n__Fixes: https://github.com/elastic/kibana/issues/220743__\n\n\n## Release Note\nExcluded deprecated features from spaces solution visibility.","sha":"81f252c02d076b83d795ffadb9030e43ed09c0fb"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.2.0","branchLabelMappingKey":"^v9.2.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/230385","number":230385,"mergeCommit":{"message":"[Spaces] Excluded deprecated features from solution visibility (#230385)\n\n## Summary\n\nExcluded deprecated features from solution visibility.\n\n## How to test\n1. Change the solution from `classic` to `observability` for the very\nfirst time in the default space.\nMake sure the response of the active space `GET\ninternal/spaces/_active_space` doesn't contain deprecated features.\n(`siem`, `siemV2`, `securitySolutionCases` and `securitySolutionCasesV2`\nwere deprecated, so only `siemV3` and `securitySolutionCasesV3` should\nbe on the list)\n```\n{\n \"id\": \"default\",\n \"name\": \"Default\",\n \"description\": \"This is your default space!\",\n \"color\": \"#00bfb3\",\n \"initials\": \"D\",\n \"imageUrl\": \"\",\n \"disabledFeatures\": [\n \"siemV3\",\n \"securitySolutionCasesV3\",\n \"securitySolutionAssistant\",\n \"securitySolutionAttackDiscovery\",\n \"securitySolutionTimeline\",\n \"securitySolutionNotes\",\n \"securitySolutionSiemMigrations\"\n ],\n \"_reserved\": true,\n \"solution\": \"oblt\"\n} \n```\n2. Change the solution back to `classic` and enable all security\nfeatures.\n<img width=\"1252\" height=\"540\" alt=\"Screenshot 2025-08-04 at 12 35 36\"\nsrc=\"https://github.com/user-attachments/assets/bf0db3df-362f-4814-8fc8-2be3b6c8740c\"\n/>\n3. Update the space and go back to Edit Space page.\n3. Make sure the enabled features counter is correctly displayed in the\nUI.\n\n### Checklist\n\n- [x] [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- [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.\n\n\n__Fixes: https://github.com/elastic/kibana/issues/220743__\n\n\n## Release Note\nExcluded deprecated features from spaces solution visibility.","sha":"81f252c02d076b83d795ffadb9030e43ed09c0fb"}}]}] BACKPORT--> Co-authored-by: Elena Shostak <165678770+elena-shostak@users.noreply.github.com>
elena-shostak
added a commit
that referenced
this pull request
Aug 5, 2025
…#230385) (#230514) # Backport This will backport the following commits from `main` to `8.19`: - [[Spaces] Excluded deprecated features from solution visibility (#230385)](#230385) <!--- Backport version: 10.0.1 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Elena Shostak","email":"165678770+elena-shostak@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-08-05T08:52:39Z","message":"[Spaces] Excluded deprecated features from solution visibility (#230385)\n\n## Summary\n\nExcluded deprecated features from solution visibility.\n\n## How to test\n1. Change the solution from `classic` to `observability` for the very\nfirst time in the default space.\nMake sure the response of the active space `GET\ninternal/spaces/_active_space` doesn't contain deprecated features.\n(`siem`, `siemV2`, `securitySolutionCases` and `securitySolutionCasesV2`\nwere deprecated, so only `siemV3` and `securitySolutionCasesV3` should\nbe on the list)\n```\n{\n \"id\": \"default\",\n \"name\": \"Default\",\n \"description\": \"This is your default space!\",\n \"color\": \"#00bfb3\",\n \"initials\": \"D\",\n \"imageUrl\": \"\",\n \"disabledFeatures\": [\n \"siemV3\",\n \"securitySolutionCasesV3\",\n \"securitySolutionAssistant\",\n \"securitySolutionAttackDiscovery\",\n \"securitySolutionTimeline\",\n \"securitySolutionNotes\",\n \"securitySolutionSiemMigrations\"\n ],\n \"_reserved\": true,\n \"solution\": \"oblt\"\n} \n```\n2. Change the solution back to `classic` and enable all security\nfeatures.\n<img width=\"1252\" height=\"540\" alt=\"Screenshot 2025-08-04 at 12 35 36\"\nsrc=\"https://github.com/user-attachments/assets/bf0db3df-362f-4814-8fc8-2be3b6c8740c\"\n/>\n3. Update the space and go back to Edit Space page.\n3. Make sure the enabled features counter is correctly displayed in the\nUI.\n\n### Checklist\n\n- [x] [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- [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.\n\n\n__Fixes: https://github.com/elastic/kibana/issues/220743__\n\n\n## Release Note\nExcluded deprecated features from spaces solution visibility.","sha":"81f252c02d076b83d795ffadb9030e43ed09c0fb","branchLabelMapping":{"^v9.2.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Security","Feature:Security/Spaces","backport:prev-minor","backport:prev-major","v9.2.0"],"title":"[Spaces] Excluded deprecated features from solution visibility","number":230385,"url":"https://github.com/elastic/kibana/pull/230385","mergeCommit":{"message":"[Spaces] Excluded deprecated features from solution visibility (#230385)\n\n## Summary\n\nExcluded deprecated features from solution visibility.\n\n## How to test\n1. Change the solution from `classic` to `observability` for the very\nfirst time in the default space.\nMake sure the response of the active space `GET\ninternal/spaces/_active_space` doesn't contain deprecated features.\n(`siem`, `siemV2`, `securitySolutionCases` and `securitySolutionCasesV2`\nwere deprecated, so only `siemV3` and `securitySolutionCasesV3` should\nbe on the list)\n```\n{\n \"id\": \"default\",\n \"name\": \"Default\",\n \"description\": \"This is your default space!\",\n \"color\": \"#00bfb3\",\n \"initials\": \"D\",\n \"imageUrl\": \"\",\n \"disabledFeatures\": [\n \"siemV3\",\n \"securitySolutionCasesV3\",\n \"securitySolutionAssistant\",\n \"securitySolutionAttackDiscovery\",\n \"securitySolutionTimeline\",\n \"securitySolutionNotes\",\n \"securitySolutionSiemMigrations\"\n ],\n \"_reserved\": true,\n \"solution\": \"oblt\"\n} \n```\n2. Change the solution back to `classic` and enable all security\nfeatures.\n<img width=\"1252\" height=\"540\" alt=\"Screenshot 2025-08-04 at 12 35 36\"\nsrc=\"https://github.com/user-attachments/assets/bf0db3df-362f-4814-8fc8-2be3b6c8740c\"\n/>\n3. Update the space and go back to Edit Space page.\n3. Make sure the enabled features counter is correctly displayed in the\nUI.\n\n### Checklist\n\n- [x] [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- [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.\n\n\n__Fixes: https://github.com/elastic/kibana/issues/220743__\n\n\n## Release Note\nExcluded deprecated features from spaces solution visibility.","sha":"81f252c02d076b83d795ffadb9030e43ed09c0fb"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.2.0","branchLabelMappingKey":"^v9.2.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/230385","number":230385,"mergeCommit":{"message":"[Spaces] Excluded deprecated features from solution visibility (#230385)\n\n## Summary\n\nExcluded deprecated features from solution visibility.\n\n## How to test\n1. Change the solution from `classic` to `observability` for the very\nfirst time in the default space.\nMake sure the response of the active space `GET\ninternal/spaces/_active_space` doesn't contain deprecated features.\n(`siem`, `siemV2`, `securitySolutionCases` and `securitySolutionCasesV2`\nwere deprecated, so only `siemV3` and `securitySolutionCasesV3` should\nbe on the list)\n```\n{\n \"id\": \"default\",\n \"name\": \"Default\",\n \"description\": \"This is your default space!\",\n \"color\": \"#00bfb3\",\n \"initials\": \"D\",\n \"imageUrl\": \"\",\n \"disabledFeatures\": [\n \"siemV3\",\n \"securitySolutionCasesV3\",\n \"securitySolutionAssistant\",\n \"securitySolutionAttackDiscovery\",\n \"securitySolutionTimeline\",\n \"securitySolutionNotes\",\n \"securitySolutionSiemMigrations\"\n ],\n \"_reserved\": true,\n \"solution\": \"oblt\"\n} \n```\n2. Change the solution back to `classic` and enable all security\nfeatures.\n<img width=\"1252\" height=\"540\" alt=\"Screenshot 2025-08-04 at 12 35 36\"\nsrc=\"https://github.com/user-attachments/assets/bf0db3df-362f-4814-8fc8-2be3b6c8740c\"\n/>\n3. Update the space and go back to Edit Space page.\n3. Make sure the enabled features counter is correctly displayed in the\nUI.\n\n### Checklist\n\n- [x] [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- [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.\n\n\n__Fixes: https://github.com/elastic/kibana/issues/220743__\n\n\n## Release Note\nExcluded deprecated features from spaces solution visibility.","sha":"81f252c02d076b83d795ffadb9030e43ed09c0fb"}},{"url":"https://github.com/elastic/kibana/pull/230511","number":230511,"branch":"9.1","state":"OPEN"}]}] BACKPORT-->
elena-shostak
added a commit
that referenced
this pull request
Aug 5, 2025
…230385) (#230522) # Backport This will backport the following commits from `main` to `9.0`: - [[Spaces] Excluded deprecated features from solution visibility (#230385)](#230385) <!--- Backport version: 10.0.1 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Elena Shostak","email":"165678770+elena-shostak@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-08-05T08:52:39Z","message":"[Spaces] Excluded deprecated features from solution visibility (#230385)\n\n## Summary\n\nExcluded deprecated features from solution visibility.\n\n## How to test\n1. Change the solution from `classic` to `observability` for the very\nfirst time in the default space.\nMake sure the response of the active space `GET\ninternal/spaces/_active_space` doesn't contain deprecated features.\n(`siem`, `siemV2`, `securitySolutionCases` and `securitySolutionCasesV2`\nwere deprecated, so only `siemV3` and `securitySolutionCasesV3` should\nbe on the list)\n```\n{\n \"id\": \"default\",\n \"name\": \"Default\",\n \"description\": \"This is your default space!\",\n \"color\": \"#00bfb3\",\n \"initials\": \"D\",\n \"imageUrl\": \"\",\n \"disabledFeatures\": [\n \"siemV3\",\n \"securitySolutionCasesV3\",\n \"securitySolutionAssistant\",\n \"securitySolutionAttackDiscovery\",\n \"securitySolutionTimeline\",\n \"securitySolutionNotes\",\n \"securitySolutionSiemMigrations\"\n ],\n \"_reserved\": true,\n \"solution\": \"oblt\"\n} \n```\n2. Change the solution back to `classic` and enable all security\nfeatures.\n<img width=\"1252\" height=\"540\" alt=\"Screenshot 2025-08-04 at 12 35 36\"\nsrc=\"https://github.com/user-attachments/assets/bf0db3df-362f-4814-8fc8-2be3b6c8740c\"\n/>\n3. Update the space and go back to Edit Space page.\n3. Make sure the enabled features counter is correctly displayed in the\nUI.\n\n### Checklist\n\n- [x] [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- [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.\n\n\n__Fixes: https://github.com/elastic/kibana/issues/220743__\n\n\n## Release Note\nExcluded deprecated features from spaces solution visibility.","sha":"81f252c02d076b83d795ffadb9030e43ed09c0fb","branchLabelMapping":{"^v9.2.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Security","Feature:Security/Spaces","backport:prev-minor","backport:prev-major","v9.2.0"],"title":"[Spaces] Excluded deprecated features from solution visibility","number":230385,"url":"https://github.com/elastic/kibana/pull/230385","mergeCommit":{"message":"[Spaces] Excluded deprecated features from solution visibility (#230385)\n\n## Summary\n\nExcluded deprecated features from solution visibility.\n\n## How to test\n1. Change the solution from `classic` to `observability` for the very\nfirst time in the default space.\nMake sure the response of the active space `GET\ninternal/spaces/_active_space` doesn't contain deprecated features.\n(`siem`, `siemV2`, `securitySolutionCases` and `securitySolutionCasesV2`\nwere deprecated, so only `siemV3` and `securitySolutionCasesV3` should\nbe on the list)\n```\n{\n \"id\": \"default\",\n \"name\": \"Default\",\n \"description\": \"This is your default space!\",\n \"color\": \"#00bfb3\",\n \"initials\": \"D\",\n \"imageUrl\": \"\",\n \"disabledFeatures\": [\n \"siemV3\",\n \"securitySolutionCasesV3\",\n \"securitySolutionAssistant\",\n \"securitySolutionAttackDiscovery\",\n \"securitySolutionTimeline\",\n \"securitySolutionNotes\",\n \"securitySolutionSiemMigrations\"\n ],\n \"_reserved\": true,\n \"solution\": \"oblt\"\n} \n```\n2. Change the solution back to `classic` and enable all security\nfeatures.\n<img width=\"1252\" height=\"540\" alt=\"Screenshot 2025-08-04 at 12 35 36\"\nsrc=\"https://github.com/user-attachments/assets/bf0db3df-362f-4814-8fc8-2be3b6c8740c\"\n/>\n3. Update the space and go back to Edit Space page.\n3. Make sure the enabled features counter is correctly displayed in the\nUI.\n\n### Checklist\n\n- [x] [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- [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.\n\n\n__Fixes: https://github.com/elastic/kibana/issues/220743__\n\n\n## Release Note\nExcluded deprecated features from spaces solution visibility.","sha":"81f252c02d076b83d795ffadb9030e43ed09c0fb"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.2.0","branchLabelMappingKey":"^v9.2.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/230385","number":230385,"mergeCommit":{"message":"[Spaces] Excluded deprecated features from solution visibility (#230385)\n\n## Summary\n\nExcluded deprecated features from solution visibility.\n\n## How to test\n1. Change the solution from `classic` to `observability` for the very\nfirst time in the default space.\nMake sure the response of the active space `GET\ninternal/spaces/_active_space` doesn't contain deprecated features.\n(`siem`, `siemV2`, `securitySolutionCases` and `securitySolutionCasesV2`\nwere deprecated, so only `siemV3` and `securitySolutionCasesV3` should\nbe on the list)\n```\n{\n \"id\": \"default\",\n \"name\": \"Default\",\n \"description\": \"This is your default space!\",\n \"color\": \"#00bfb3\",\n \"initials\": \"D\",\n \"imageUrl\": \"\",\n \"disabledFeatures\": [\n \"siemV3\",\n \"securitySolutionCasesV3\",\n \"securitySolutionAssistant\",\n \"securitySolutionAttackDiscovery\",\n \"securitySolutionTimeline\",\n \"securitySolutionNotes\",\n \"securitySolutionSiemMigrations\"\n ],\n \"_reserved\": true,\n \"solution\": \"oblt\"\n} \n```\n2. Change the solution back to `classic` and enable all security\nfeatures.\n<img width=\"1252\" height=\"540\" alt=\"Screenshot 2025-08-04 at 12 35 36\"\nsrc=\"https://github.com/user-attachments/assets/bf0db3df-362f-4814-8fc8-2be3b6c8740c\"\n/>\n3. Update the space and go back to Edit Space page.\n3. Make sure the enabled features counter is correctly displayed in the\nUI.\n\n### Checklist\n\n- [x] [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- [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.\n\n\n__Fixes: https://github.com/elastic/kibana/issues/220743__\n\n\n## Release Note\nExcluded deprecated features from spaces solution visibility.","sha":"81f252c02d076b83d795ffadb9030e43ed09c0fb"}},{"url":"https://github.com/elastic/kibana/pull/230511","number":230511,"branch":"9.1","state":"OPEN"},{"url":"https://github.com/elastic/kibana/pull/230514","number":230514,"branch":"8.19","state":"OPEN"},{"url":"https://github.com/elastic/kibana/pull/230517","number":230517,"branch":"8.18","state":"OPEN"},{"url":"https://github.com/elastic/kibana/pull/230520","number":230520,"branch":"8.17","state":"OPEN"}]}] BACKPORT-->
elena-shostak
added a commit
that referenced
this pull request
Aug 5, 2025
…#230385) (#230517) # Backport This will backport the following commits from `main` to `8.18`: - [[Spaces] Excluded deprecated features from solution visibility (#230385)](#230385) <!--- Backport version: 10.0.1 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Elena Shostak","email":"165678770+elena-shostak@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-08-05T08:52:39Z","message":"[Spaces] Excluded deprecated features from solution visibility (#230385)\n\n## Summary\n\nExcluded deprecated features from solution visibility.\n\n## How to test\n1. Change the solution from `classic` to `observability` for the very\nfirst time in the default space.\nMake sure the response of the active space `GET\ninternal/spaces/_active_space` doesn't contain deprecated features.\n(`siem`, `siemV2`, `securitySolutionCases` and `securitySolutionCasesV2`\nwere deprecated, so only `siemV3` and `securitySolutionCasesV3` should\nbe on the list)\n```\n{\n \"id\": \"default\",\n \"name\": \"Default\",\n \"description\": \"This is your default space!\",\n \"color\": \"#00bfb3\",\n \"initials\": \"D\",\n \"imageUrl\": \"\",\n \"disabledFeatures\": [\n \"siemV3\",\n \"securitySolutionCasesV3\",\n \"securitySolutionAssistant\",\n \"securitySolutionAttackDiscovery\",\n \"securitySolutionTimeline\",\n \"securitySolutionNotes\",\n \"securitySolutionSiemMigrations\"\n ],\n \"_reserved\": true,\n \"solution\": \"oblt\"\n} \n```\n2. Change the solution back to `classic` and enable all security\nfeatures.\n<img width=\"1252\" height=\"540\" alt=\"Screenshot 2025-08-04 at 12 35 36\"\nsrc=\"https://github.com/user-attachments/assets/bf0db3df-362f-4814-8fc8-2be3b6c8740c\"\n/>\n3. Update the space and go back to Edit Space page.\n3. Make sure the enabled features counter is correctly displayed in the\nUI.\n\n### Checklist\n\n- [x] [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- [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.\n\n\n__Fixes: https://github.com/elastic/kibana/issues/220743__\n\n\n## Release Note\nExcluded deprecated features from spaces solution visibility.","sha":"81f252c02d076b83d795ffadb9030e43ed09c0fb","branchLabelMapping":{"^v9.2.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Security","Feature:Security/Spaces","backport:prev-minor","backport:prev-major","v9.2.0"],"title":"[Spaces] Excluded deprecated features from solution visibility","number":230385,"url":"https://github.com/elastic/kibana/pull/230385","mergeCommit":{"message":"[Spaces] Excluded deprecated features from solution visibility (#230385)\n\n## Summary\n\nExcluded deprecated features from solution visibility.\n\n## How to test\n1. Change the solution from `classic` to `observability` for the very\nfirst time in the default space.\nMake sure the response of the active space `GET\ninternal/spaces/_active_space` doesn't contain deprecated features.\n(`siem`, `siemV2`, `securitySolutionCases` and `securitySolutionCasesV2`\nwere deprecated, so only `siemV3` and `securitySolutionCasesV3` should\nbe on the list)\n```\n{\n \"id\": \"default\",\n \"name\": \"Default\",\n \"description\": \"This is your default space!\",\n \"color\": \"#00bfb3\",\n \"initials\": \"D\",\n \"imageUrl\": \"\",\n \"disabledFeatures\": [\n \"siemV3\",\n \"securitySolutionCasesV3\",\n \"securitySolutionAssistant\",\n \"securitySolutionAttackDiscovery\",\n \"securitySolutionTimeline\",\n \"securitySolutionNotes\",\n \"securitySolutionSiemMigrations\"\n ],\n \"_reserved\": true,\n \"solution\": \"oblt\"\n} \n```\n2. Change the solution back to `classic` and enable all security\nfeatures.\n<img width=\"1252\" height=\"540\" alt=\"Screenshot 2025-08-04 at 12 35 36\"\nsrc=\"https://github.com/user-attachments/assets/bf0db3df-362f-4814-8fc8-2be3b6c8740c\"\n/>\n3. Update the space and go back to Edit Space page.\n3. Make sure the enabled features counter is correctly displayed in the\nUI.\n\n### Checklist\n\n- [x] [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- [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.\n\n\n__Fixes: https://github.com/elastic/kibana/issues/220743__\n\n\n## Release Note\nExcluded deprecated features from spaces solution visibility.","sha":"81f252c02d076b83d795ffadb9030e43ed09c0fb"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.2.0","branchLabelMappingKey":"^v9.2.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/230385","number":230385,"mergeCommit":{"message":"[Spaces] Excluded deprecated features from solution visibility (#230385)\n\n## Summary\n\nExcluded deprecated features from solution visibility.\n\n## How to test\n1. Change the solution from `classic` to `observability` for the very\nfirst time in the default space.\nMake sure the response of the active space `GET\ninternal/spaces/_active_space` doesn't contain deprecated features.\n(`siem`, `siemV2`, `securitySolutionCases` and `securitySolutionCasesV2`\nwere deprecated, so only `siemV3` and `securitySolutionCasesV3` should\nbe on the list)\n```\n{\n \"id\": \"default\",\n \"name\": \"Default\",\n \"description\": \"This is your default space!\",\n \"color\": \"#00bfb3\",\n \"initials\": \"D\",\n \"imageUrl\": \"\",\n \"disabledFeatures\": [\n \"siemV3\",\n \"securitySolutionCasesV3\",\n \"securitySolutionAssistant\",\n \"securitySolutionAttackDiscovery\",\n \"securitySolutionTimeline\",\n \"securitySolutionNotes\",\n \"securitySolutionSiemMigrations\"\n ],\n \"_reserved\": true,\n \"solution\": \"oblt\"\n} \n```\n2. Change the solution back to `classic` and enable all security\nfeatures.\n<img width=\"1252\" height=\"540\" alt=\"Screenshot 2025-08-04 at 12 35 36\"\nsrc=\"https://github.com/user-attachments/assets/bf0db3df-362f-4814-8fc8-2be3b6c8740c\"\n/>\n3. Update the space and go back to Edit Space page.\n3. Make sure the enabled features counter is correctly displayed in the\nUI.\n\n### Checklist\n\n- [x] [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- [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.\n\n\n__Fixes: https://github.com/elastic/kibana/issues/220743__\n\n\n## Release Note\nExcluded deprecated features from spaces solution visibility.","sha":"81f252c02d076b83d795ffadb9030e43ed09c0fb"}},{"url":"https://github.com/elastic/kibana/pull/230511","number":230511,"branch":"9.1","state":"OPEN"}]}] BACKPORT-->
elena-shostak
added a commit
that referenced
this pull request
Aug 5, 2025
…) (#230520) # Backport This will backport the following commits from `main` to `8.17`: - [[Spaces] Excluded deprecated features from solution visibility (#230385)](#230385) <!--- Backport version: 10.0.1 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Elena Shostak","email":"165678770+elena-shostak@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-08-05T08:52:39Z","message":"[Spaces] Excluded deprecated features from solution visibility (#230385)\n\n## Summary\n\nExcluded deprecated features from solution visibility.\n\n## How to test\n1. Change the solution from `classic` to `observability` for the very\nfirst time in the default space.\nMake sure the response of the active space `GET\ninternal/spaces/_active_space` doesn't contain deprecated features.\n(`siem`, `siemV2`, `securitySolutionCases` and `securitySolutionCasesV2`\nwere deprecated, so only `siemV3` and `securitySolutionCasesV3` should\nbe on the list)\n```\n{\n \"id\": \"default\",\n \"name\": \"Default\",\n \"description\": \"This is your default space!\",\n \"color\": \"#00bfb3\",\n \"initials\": \"D\",\n \"imageUrl\": \"\",\n \"disabledFeatures\": [\n \"siemV3\",\n \"securitySolutionCasesV3\",\n \"securitySolutionAssistant\",\n \"securitySolutionAttackDiscovery\",\n \"securitySolutionTimeline\",\n \"securitySolutionNotes\",\n \"securitySolutionSiemMigrations\"\n ],\n \"_reserved\": true,\n \"solution\": \"oblt\"\n} \n```\n2. Change the solution back to `classic` and enable all security\nfeatures.\n<img width=\"1252\" height=\"540\" alt=\"Screenshot 2025-08-04 at 12 35 36\"\nsrc=\"https://github.com/user-attachments/assets/bf0db3df-362f-4814-8fc8-2be3b6c8740c\"\n/>\n3. Update the space and go back to Edit Space page.\n3. Make sure the enabled features counter is correctly displayed in the\nUI.\n\n### Checklist\n\n- [x] [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- [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.\n\n\n__Fixes: https://github.com/elastic/kibana/issues/220743__\n\n\n## Release Note\nExcluded deprecated features from spaces solution visibility.","sha":"81f252c02d076b83d795ffadb9030e43ed09c0fb","branchLabelMapping":{"^v9.2.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Security","Feature:Security/Spaces","backport:prev-minor","backport:prev-major","v9.2.0"],"title":"[Spaces] Excluded deprecated features from solution visibility","number":230385,"url":"https://github.com/elastic/kibana/pull/230385","mergeCommit":{"message":"[Spaces] Excluded deprecated features from solution visibility (#230385)\n\n## Summary\n\nExcluded deprecated features from solution visibility.\n\n## How to test\n1. Change the solution from `classic` to `observability` for the very\nfirst time in the default space.\nMake sure the response of the active space `GET\ninternal/spaces/_active_space` doesn't contain deprecated features.\n(`siem`, `siemV2`, `securitySolutionCases` and `securitySolutionCasesV2`\nwere deprecated, so only `siemV3` and `securitySolutionCasesV3` should\nbe on the list)\n```\n{\n \"id\": \"default\",\n \"name\": \"Default\",\n \"description\": \"This is your default space!\",\n \"color\": \"#00bfb3\",\n \"initials\": \"D\",\n \"imageUrl\": \"\",\n \"disabledFeatures\": [\n \"siemV3\",\n \"securitySolutionCasesV3\",\n \"securitySolutionAssistant\",\n \"securitySolutionAttackDiscovery\",\n \"securitySolutionTimeline\",\n \"securitySolutionNotes\",\n \"securitySolutionSiemMigrations\"\n ],\n \"_reserved\": true,\n \"solution\": \"oblt\"\n} \n```\n2. Change the solution back to `classic` and enable all security\nfeatures.\n<img width=\"1252\" height=\"540\" alt=\"Screenshot 2025-08-04 at 12 35 36\"\nsrc=\"https://github.com/user-attachments/assets/bf0db3df-362f-4814-8fc8-2be3b6c8740c\"\n/>\n3. Update the space and go back to Edit Space page.\n3. Make sure the enabled features counter is correctly displayed in the\nUI.\n\n### Checklist\n\n- [x] [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- [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.\n\n\n__Fixes: https://github.com/elastic/kibana/issues/220743__\n\n\n## Release Note\nExcluded deprecated features from spaces solution visibility.","sha":"81f252c02d076b83d795ffadb9030e43ed09c0fb"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.2.0","branchLabelMappingKey":"^v9.2.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/230385","number":230385,"mergeCommit":{"message":"[Spaces] Excluded deprecated features from solution visibility (#230385)\n\n## Summary\n\nExcluded deprecated features from solution visibility.\n\n## How to test\n1. Change the solution from `classic` to `observability` for the very\nfirst time in the default space.\nMake sure the response of the active space `GET\ninternal/spaces/_active_space` doesn't contain deprecated features.\n(`siem`, `siemV2`, `securitySolutionCases` and `securitySolutionCasesV2`\nwere deprecated, so only `siemV3` and `securitySolutionCasesV3` should\nbe on the list)\n```\n{\n \"id\": \"default\",\n \"name\": \"Default\",\n \"description\": \"This is your default space!\",\n \"color\": \"#00bfb3\",\n \"initials\": \"D\",\n \"imageUrl\": \"\",\n \"disabledFeatures\": [\n \"siemV3\",\n \"securitySolutionCasesV3\",\n \"securitySolutionAssistant\",\n \"securitySolutionAttackDiscovery\",\n \"securitySolutionTimeline\",\n \"securitySolutionNotes\",\n \"securitySolutionSiemMigrations\"\n ],\n \"_reserved\": true,\n \"solution\": \"oblt\"\n} \n```\n2. Change the solution back to `classic` and enable all security\nfeatures.\n<img width=\"1252\" height=\"540\" alt=\"Screenshot 2025-08-04 at 12 35 36\"\nsrc=\"https://github.com/user-attachments/assets/bf0db3df-362f-4814-8fc8-2be3b6c8740c\"\n/>\n3. Update the space and go back to Edit Space page.\n3. Make sure the enabled features counter is correctly displayed in the\nUI.\n\n### Checklist\n\n- [x] [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- [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.\n\n\n__Fixes: https://github.com/elastic/kibana/issues/220743__\n\n\n## Release Note\nExcluded deprecated features from spaces solution visibility.","sha":"81f252c02d076b83d795ffadb9030e43ed09c0fb"}},{"url":"https://github.com/elastic/kibana/pull/230511","number":230511,"branch":"9.1","state":"OPEN"}]}] BACKPORT-->
delanni
pushed a commit
to delanni/kibana
that referenced
this pull request
Aug 5, 2025
…ic#230385) ## Summary Excluded deprecated features from solution visibility. ## How to test 1. Change the solution from `classic` to `observability` for the very first time in the default space. Make sure the response of the active space `GET internal/spaces/_active_space` doesn't contain deprecated features. (`siem`, `siemV2`, `securitySolutionCases` and `securitySolutionCasesV2` were deprecated, so only `siemV3` and `securitySolutionCasesV3` should be on the list) ``` { "id": "default", "name": "Default", "description": "This is your default space!", "color": "#00bfb3", "initials": "D", "imageUrl": "", "disabledFeatures": [ "siemV3", "securitySolutionCasesV3", "securitySolutionAssistant", "securitySolutionAttackDiscovery", "securitySolutionTimeline", "securitySolutionNotes", "securitySolutionSiemMigrations" ], "_reserved": true, "solution": "oblt" } ``` 2. Change the solution back to `classic` and enable all security features. <img width="1252" height="540" alt="Screenshot 2025-08-04 at 12 35 36" src="https://github.com/user-attachments/assets/bf0db3df-362f-4814-8fc8-2be3b6c8740c" /> 3. Update the space and go back to Edit Space page. 3. Make sure the enabled features counter is correctly displayed in the UI. ### 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. __Fixes: https://github.com/elastic/kibana/issues/220743__ ## Release Note Excluded deprecated features from spaces solution visibility.
NicholasPeretti
pushed a commit
to NicholasPeretti/kibana
that referenced
this pull request
Aug 18, 2025
…ic#230385) ## Summary Excluded deprecated features from solution visibility. ## How to test 1. Change the solution from `classic` to `observability` for the very first time in the default space. Make sure the response of the active space `GET internal/spaces/_active_space` doesn't contain deprecated features. (`siem`, `siemV2`, `securitySolutionCases` and `securitySolutionCasesV2` were deprecated, so only `siemV3` and `securitySolutionCasesV3` should be on the list) ``` { "id": "default", "name": "Default", "description": "This is your default space!", "color": "#00bfb3", "initials": "D", "imageUrl": "", "disabledFeatures": [ "siemV3", "securitySolutionCasesV3", "securitySolutionAssistant", "securitySolutionAttackDiscovery", "securitySolutionTimeline", "securitySolutionNotes", "securitySolutionSiemMigrations" ], "_reserved": true, "solution": "oblt" } ``` 2. Change the solution back to `classic` and enable all security features. <img width="1252" height="540" alt="Screenshot 2025-08-04 at 12 35 36" src="https://github.com/user-attachments/assets/bf0db3df-362f-4814-8fc8-2be3b6c8740c" /> 3. Update the space and go back to Edit Space page. 3. Make sure the enabled features counter is correctly displayed in the UI. ### 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. __Fixes: https://github.com/elastic/kibana/issues/220743__ ## Release Note Excluded deprecated features from spaces solution visibility.
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
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
Excluded deprecated features from solution visibility.
How to test
classictoobservabilityfor the very first time in the default space.Make sure the response of the active space
GET internal/spaces/_active_spacedoesn't contain deprecated features. (siem,siemV2,securitySolutionCasesandsecuritySolutionCasesV2were deprecated, so onlysiemV3andsecuritySolutionCasesV3should be on the list)classicand enable all security features.Checklist
release_note:*label is applied per the guidelinesbackport:*labels.Fixes: #220743
Release Note
Excluded deprecated features from spaces solution visibility.