Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[9.0] [ResponseOps][Security][Rules] Fix fields missing from Cases ac…
…tion in Security Solution rule form (#210547) (#211944) # Backport This will backport the following commits from `main` to `9.0`: - [[ResponseOps][Security][Rules] Fix fields missing from Cases action in Security Solution rule form (#210547)](#210547) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Umberto Pepato","email":"umbopepato@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-20T17:36:39Z","message":"[ResponseOps][Security][Rules] Fix fields missing from Cases action in Security Solution rule form (#210547)\n\n## Summary\n\nCorrectly forwards the selected rule type id to the actions form section\nin the Security Solution rule creation/update flow.\nAdds a functional test case to cover the bug.\n\n## To verify\n\n1. Navigate to `Security > Rules > Detection rules > Create new rule`\n2. Fill in the first 3 steps\n3. In the Actions step, select the Cases action\n4. Check that the `Group by alert field` dropdown shows the correct\nalert fields\n5. Create the rule, then repeat point 5 in the rule editing UI\n\n## References\n\nFixes #210209","sha":"0abbd173b124bcb5f83a377c3923f57120f144e9","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","v9.0.0","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[ResponseOps][Security][Rules] Fix fields missing from Cases action in Security Solution rule form","number":210547,"url":"https://github.com/elastic/kibana/pull/210547","mergeCommit":{"message":"[ResponseOps][Security][Rules] Fix fields missing from Cases action in Security Solution rule form (#210547)\n\n## Summary\n\nCorrectly forwards the selected rule type id to the actions form section\nin the Security Solution rule creation/update flow.\nAdds a functional test case to cover the bug.\n\n## To verify\n\n1. Navigate to `Security > Rules > Detection rules > Create new rule`\n2. Fill in the first 3 steps\n3. In the Actions step, select the Cases action\n4. Check that the `Group by alert field` dropdown shows the correct\nalert fields\n5. Create the rule, then repeat point 5 in the rule editing UI\n\n## References\n\nFixes #210209","sha":"0abbd173b124bcb5f83a377c3923f57120f144e9"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/210547","number":210547,"mergeCommit":{"message":"[ResponseOps][Security][Rules] Fix fields missing from Cases action in Security Solution rule form (#210547)\n\n## Summary\n\nCorrectly forwards the selected rule type id to the actions form section\nin the Security Solution rule creation/update flow.\nAdds a functional test case to cover the bug.\n\n## To verify\n\n1. Navigate to `Security > Rules > Detection rules > Create new rule`\n2. Fill in the first 3 steps\n3. In the Actions step, select the Cases action\n4. Check that the `Group by alert field` dropdown shows the correct\nalert fields\n5. Create the rule, then repeat point 5 in the rule editing UI\n\n## References\n\nFixes #210209","sha":"0abbd173b124bcb5f83a377c3923f57120f144e9"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Umberto Pepato <umbopepato@users.noreply.github.com>
- Loading branch information