Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[8.x] [Cloud Security] changed findings group by name to group by id (#…
…206379) (#207170) # Backport This will backport the following commits from `main` to `8.x`: - [[Cloud Security] changed findings group by name to group by id (#206379)](#206379) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](/~https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Alex Prozorov","email":"alex.prozorov@elastic.co"},"sourceCommit":{"committedDate":"2025-01-16T16:24:10Z","message":"[Cloud Security] changed findings group by name to group by id (#206379)\n\n## Summary\r\nThis PR fixes group by logic in the findings table to be based on\r\nresource.id instead of resource.name.\r\n\r\n### Screenshots\r\n\r\n![image](/~https://github.com/user-attachments/assets/5d480501-9f44-4395-82bd-e069b4a3c3f7)\r\n\r\n\r\n\r\n### Closes\r\n- /~https://github.com/elastic/security-team/issues/9782\r\n\r\n### Definition of done\r\n- [x] When grouping findings by Resource, the findings are grouped by\r\nresource.id\r\n- [x] The group title should still contain resource.name for better UX\r\nin combination with the id\r\n- [x] The label in the grouping properties should be Resource ID, not\r\njust Resource\r\n\r\n### Checklist\r\n- [x] [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- [x] 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)","sha":"22e047a1f62331cbf80b886b7a4275b1143b3446","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","good first issue","release_note:skip","backport:skip","v9.0.0","Team:Cloud Security"],"title":"[Cloud Security] changed findings group by name to group by id","number":206379,"url":"/~https://github.com/elastic/kibana/pull/206379","mergeCommit":{"message":"[Cloud Security] changed findings group by name to group by id (#206379)\n\n## Summary\r\nThis PR fixes group by logic in the findings table to be based on\r\nresource.id instead of resource.name.\r\n\r\n### Screenshots\r\n\r\n![image](/~https://github.com/user-attachments/assets/5d480501-9f44-4395-82bd-e069b4a3c3f7)\r\n\r\n\r\n\r\n### Closes\r\n- /~https://github.com/elastic/security-team/issues/9782\r\n\r\n### Definition of done\r\n- [x] When grouping findings by Resource, the findings are grouped by\r\nresource.id\r\n- [x] The group title should still contain resource.name for better UX\r\nin combination with the id\r\n- [x] The label in the grouping properties should be Resource ID, not\r\njust Resource\r\n\r\n### Checklist\r\n- [x] [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- [x] 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)","sha":"22e047a1f62331cbf80b886b7a4275b1143b3446"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"/~https://github.com/elastic/kibana/pull/206379","number":206379,"mergeCommit":{"message":"[Cloud Security] changed findings group by name to group by id (#206379)\n\n## Summary\r\nThis PR fixes group by logic in the findings table to be based on\r\nresource.id instead of resource.name.\r\n\r\n### Screenshots\r\n\r\n![image](/~https://github.com/user-attachments/assets/5d480501-9f44-4395-82bd-e069b4a3c3f7)\r\n\r\n\r\n\r\n### Closes\r\n- /~https://github.com/elastic/security-team/issues/9782\r\n\r\n### Definition of done\r\n- [x] When grouping findings by Resource, the findings are grouped by\r\nresource.id\r\n- [x] The group title should still contain resource.name for better UX\r\nin combination with the id\r\n- [x] The label in the grouping properties should be Resource ID, not\r\njust Resource\r\n\r\n### Checklist\r\n- [x] [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- [x] 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)","sha":"22e047a1f62331cbf80b886b7a4275b1143b3446"}}]}] BACKPORT-->
- Loading branch information