[8.19] [Security Solution] Actualize prebuilt rule upgrade test plans (#222606)#225040
Merged
kibanamachine merged 1 commit intoelastic:8.19from Jun 24, 2025
Merged
Conversation
…ic#222606) **Addresses:** elastic#202078 **Resolves:** elastic#166215 ## Summary This PR actualizes prebuilt rule upgrade test plans to correspond to the current feature state. ## Details The changes are summarized in the following items - Missing scenarios were added - elastic#166215 was addressed - The wording was fixed to make the test scenarios shorter and focused - Prebuilt Rules Customization Milestone 2 test scenarios were migrated to a separate test plan `prebuilt_rule_json_diff.md`. The functionality is still relevant and used for rule type changes and under low-tier licenses. (cherry picked from commit 1a59438)
maximpn
added a commit
that referenced
this pull request
Jul 7, 2025
…#222606) (#226785) # Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution] Actualize prebuilt rule upgrade test plans (#222606)](#222606) <!--- Backport version: 10.0.1 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Maxim Palenov","email":"maxim.palenov@elastic.co"},"sourceCommit":{"committedDate":"2025-06-24T10:09:52Z","message":"[Security Solution] Actualize prebuilt rule upgrade test plans (#222606)\n\n**Addresses:** https://github.com/elastic/kibana/issues/202078\n**Resolves:** https://github.com/elastic/kibana/issues/166215\n\n## Summary\n\nThis PR actualizes prebuilt rule upgrade test plans to correspond to the current feature state.\n\n## Details\n\nThe changes are summarized in the following items\n\n- Missing scenarios were added\n- #166215 was addressed\n- The wording was fixed to make the test scenarios shorter and focused\n- Prebuilt Rules Customization Milestone 2 test scenarios were migrated to a separate test plan `prebuilt_rule_json_diff.md`. The functionality is still relevant and used for rule type changes and under low-tier licenses.","sha":"1a59438b125e45418d01cab29cc06ca0838740a2","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","test-plan","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","Feature:Prebuilt Detection Rules","backport:version","v9.1.0","v8.19.0"],"title":"[Security Solution] Actualize prebuilt rule upgrade test plans","number":222606,"url":"https://github.com/elastic/kibana/pull/222606","mergeCommit":{"message":"[Security Solution] Actualize prebuilt rule upgrade test plans (#222606)\n\n**Addresses:** https://github.com/elastic/kibana/issues/202078\n**Resolves:** https://github.com/elastic/kibana/issues/166215\n\n## Summary\n\nThis PR actualizes prebuilt rule upgrade test plans to correspond to the current feature state.\n\n## Details\n\nThe changes are summarized in the following items\n\n- Missing scenarios were added\n- #166215 was addressed\n- The wording was fixed to make the test scenarios shorter and focused\n- Prebuilt Rules Customization Milestone 2 test scenarios were migrated to a separate test plan `prebuilt_rule_json_diff.md`. The functionality is still relevant and used for rule type changes and under low-tier licenses.","sha":"1a59438b125e45418d01cab29cc06ca0838740a2"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/222606","number":222606,"mergeCommit":{"message":"[Security Solution] Actualize prebuilt rule upgrade test plans (#222606)\n\n**Addresses:** https://github.com/elastic/kibana/issues/202078\n**Resolves:** https://github.com/elastic/kibana/issues/166215\n\n## Summary\n\nThis PR actualizes prebuilt rule upgrade test plans to correspond to the current feature state.\n\n## Details\n\nThe changes are summarized in the following items\n\n- Missing scenarios were added\n- #166215 was addressed\n- The wording was fixed to make the test scenarios shorter and focused\n- Prebuilt Rules Customization Milestone 2 test scenarios were migrated to a separate test plan `prebuilt_rule_json_diff.md`. The functionality is still relevant and used for rule type changes and under low-tier licenses.","sha":"1a59438b125e45418d01cab29cc06ca0838740a2"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/225040","number":225040,"state":"MERGED","mergeCommit":{"sha":"8fdd25d5af7b5d8726539d945519da0ab4c55106","message":"[8.19] [Security Solution] Actualize prebuilt rule upgrade test plans (#222606) (#225040)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.19`:\n- [[Security Solution] Actualize prebuilt rule upgrade test plans\n(#222606)](https://github.com/elastic/kibana/pull/222606)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Maxim Palenov <maxim.palenov@elastic.co>"}}]}] BACKPORT-->
maximpn
added a commit
that referenced
this pull request
Jul 7, 2025
…222606) (#226784) # Backport This will backport the following commits from `main` to `9.0`: - [[Security Solution] Actualize prebuilt rule upgrade test plans (#222606)](#222606) <!--- Backport version: 10.0.1 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Maxim Palenov","email":"maxim.palenov@elastic.co"},"sourceCommit":{"committedDate":"2025-06-24T10:09:52Z","message":"[Security Solution] Actualize prebuilt rule upgrade test plans (#222606)\n\n**Addresses:** https://github.com/elastic/kibana/issues/202078\n**Resolves:** https://github.com/elastic/kibana/issues/166215\n\n## Summary\n\nThis PR actualizes prebuilt rule upgrade test plans to correspond to the current feature state.\n\n## Details\n\nThe changes are summarized in the following items\n\n- Missing scenarios were added\n- #166215 was addressed\n- The wording was fixed to make the test scenarios shorter and focused\n- Prebuilt Rules Customization Milestone 2 test scenarios were migrated to a separate test plan `prebuilt_rule_json_diff.md`. The functionality is still relevant and used for rule type changes and under low-tier licenses.","sha":"1a59438b125e45418d01cab29cc06ca0838740a2","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","test-plan","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","Feature:Prebuilt Detection Rules","backport:version","v9.1.0","v8.19.0"],"title":"[Security Solution] Actualize prebuilt rule upgrade test plans","number":222606,"url":"https://github.com/elastic/kibana/pull/222606","mergeCommit":{"message":"[Security Solution] Actualize prebuilt rule upgrade test plans (#222606)\n\n**Addresses:** https://github.com/elastic/kibana/issues/202078\n**Resolves:** https://github.com/elastic/kibana/issues/166215\n\n## Summary\n\nThis PR actualizes prebuilt rule upgrade test plans to correspond to the current feature state.\n\n## Details\n\nThe changes are summarized in the following items\n\n- Missing scenarios were added\n- #166215 was addressed\n- The wording was fixed to make the test scenarios shorter and focused\n- Prebuilt Rules Customization Milestone 2 test scenarios were migrated to a separate test plan `prebuilt_rule_json_diff.md`. The functionality is still relevant and used for rule type changes and under low-tier licenses.","sha":"1a59438b125e45418d01cab29cc06ca0838740a2"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/222606","number":222606,"mergeCommit":{"message":"[Security Solution] Actualize prebuilt rule upgrade test plans (#222606)\n\n**Addresses:** https://github.com/elastic/kibana/issues/202078\n**Resolves:** https://github.com/elastic/kibana/issues/166215\n\n## Summary\n\nThis PR actualizes prebuilt rule upgrade test plans to correspond to the current feature state.\n\n## Details\n\nThe changes are summarized in the following items\n\n- Missing scenarios were added\n- #166215 was addressed\n- The wording was fixed to make the test scenarios shorter and focused\n- Prebuilt Rules Customization Milestone 2 test scenarios were migrated to a separate test plan `prebuilt_rule_json_diff.md`. The functionality is still relevant and used for rule type changes and under low-tier licenses.","sha":"1a59438b125e45418d01cab29cc06ca0838740a2"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/225040","number":225040,"state":"MERGED","mergeCommit":{"sha":"8fdd25d5af7b5d8726539d945519da0ab4c55106","message":"[8.19] [Security Solution] Actualize prebuilt rule upgrade test plans (#222606) (#225040)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.19`:\n- [[Security Solution] Actualize prebuilt rule upgrade test plans\n(#222606)](https://github.com/elastic/kibana/pull/222606)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Maxim Palenov <maxim.palenov@elastic.co>"}}]}] BACKPORT-->
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
2 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.
Backport
This will backport the following commits from
mainto8.19:Questions ?
Please refer to the Backport tool documentation