Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[8.x] [Security Solution][Alert details] - bring back last alert stat…
…us change to flyout (elastic#205224) (elastic#205835) # Backport This will backport the following commits from `main` to `8.x`: - [[Security Solution][Alert details] - bring back last alert status change to flyout (elastic#205224)](elastic#205224) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Philippe Oberti","email":"[email protected]"},"sourceCommit":{"committedDate":"2025-01-08T04:50:44Z","message":"[Security Solution][Alert details] - bring back last alert status change to flyout (elastic#205224)\n\n## Summary\r\n\r\nOver a year ago, [this\r\nPR](elastic#171589) added some\r\ninformation to the alert details flyout, to show when an alert's status\r\n(`closed`, `open` or `aknowledged`) had been modified last and by which\r\nuser.\r\nShortly after, [this follow up\r\nPR](elastic#172888) removed the UI from\r\nthe alert details flyout, as the information wasn't extremely important\r\nand was taking some valuable vertical space, pushing down below the\r\n`Highlighted fields` section, that users were finding very important.\r\n\r\nA few months later, we added the ability to persist which of the top\r\nsections (`About`, `Investigation`, `Visualizations`, `Insights` and\r\n`Response`) were collapsed or expanded. That way the user wouldn't have\r\nto always collapse or expand sections they would often don't need.\r\n\r\nThis PR brings back the alert's last status changes to the `About`\r\nsection, as the vertical space is no longer a big issues, because users\r\ncan now collapse the entire `About` section.\r\n\r\n#### If data is not present, the last change UI is not shown\r\n![Screenshot 2024-12-27 at 3 46\r\n14 PM](https://github.com/user-attachments/assets/24e033d7-fb15-496a-97be-ecf78996d243)\r\n\r\n#### If the correct data is shown:\r\n![Screenshot 2024-12-27 at 3 50\r\n12 PM](https://github.com/user-attachments/assets/a13f54d8-1804-4baf-a12b-5203beb4f92d)\r\n\r\n### How to test\r\n\r\n- have a few alerts in the alerts table\r\n- open the alert details flyout for one alert and change the status\r\n(button in the header)\r\n- verify that the last status change section is shown in the `About`\r\nsection\r\n\r\n### Checklist\r\n\r\n- [x] 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/packages/kbn-i18n/README.md)\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","sha":"a4b1975fced9f5fd6c408401d19b79650a4fc56d","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["v9.0.0","release_note:feature","Team:Threat Hunting:Investigations","backport:version","v8.18.0"],"title":"[Security Solution][Alert details] - bring back last alert status change to flyout","number":205224,"url":"https://github.com/elastic/kibana/pull/205224","mergeCommit":{"message":"[Security Solution][Alert details] - bring back last alert status change to flyout (elastic#205224)\n\n## Summary\r\n\r\nOver a year ago, [this\r\nPR](elastic#171589) added some\r\ninformation to the alert details flyout, to show when an alert's status\r\n(`closed`, `open` or `aknowledged`) had been modified last and by which\r\nuser.\r\nShortly after, [this follow up\r\nPR](elastic#172888) removed the UI from\r\nthe alert details flyout, as the information wasn't extremely important\r\nand was taking some valuable vertical space, pushing down below the\r\n`Highlighted fields` section, that users were finding very important.\r\n\r\nA few months later, we added the ability to persist which of the top\r\nsections (`About`, `Investigation`, `Visualizations`, `Insights` and\r\n`Response`) were collapsed or expanded. That way the user wouldn't have\r\nto always collapse or expand sections they would often don't need.\r\n\r\nThis PR brings back the alert's last status changes to the `About`\r\nsection, as the vertical space is no longer a big issues, because users\r\ncan now collapse the entire `About` section.\r\n\r\n#### If data is not present, the last change UI is not shown\r\n![Screenshot 2024-12-27 at 3 46\r\n14 PM](https://github.com/user-attachments/assets/24e033d7-fb15-496a-97be-ecf78996d243)\r\n\r\n#### If the correct data is shown:\r\n![Screenshot 2024-12-27 at 3 50\r\n12 PM](https://github.com/user-attachments/assets/a13f54d8-1804-4baf-a12b-5203beb4f92d)\r\n\r\n### How to test\r\n\r\n- have a few alerts in the alerts table\r\n- open the alert details flyout for one alert and change the status\r\n(button in the header)\r\n- verify that the last status change section is shown in the `About`\r\nsection\r\n\r\n### Checklist\r\n\r\n- [x] 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/packages/kbn-i18n/README.md)\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","sha":"a4b1975fced9f5fd6c408401d19b79650a4fc56d"}},"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/205224","number":205224,"mergeCommit":{"message":"[Security Solution][Alert details] - bring back last alert status change to flyout (elastic#205224)\n\n## Summary\r\n\r\nOver a year ago, [this\r\nPR](elastic#171589) added some\r\ninformation to the alert details flyout, to show when an alert's status\r\n(`closed`, `open` or `aknowledged`) had been modified last and by which\r\nuser.\r\nShortly after, [this follow up\r\nPR](elastic#172888) removed the UI from\r\nthe alert details flyout, as the information wasn't extremely important\r\nand was taking some valuable vertical space, pushing down below the\r\n`Highlighted fields` section, that users were finding very important.\r\n\r\nA few months later, we added the ability to persist which of the top\r\nsections (`About`, `Investigation`, `Visualizations`, `Insights` and\r\n`Response`) were collapsed or expanded. That way the user wouldn't have\r\nto always collapse or expand sections they would often don't need.\r\n\r\nThis PR brings back the alert's last status changes to the `About`\r\nsection, as the vertical space is no longer a big issues, because users\r\ncan now collapse the entire `About` section.\r\n\r\n#### If data is not present, the last change UI is not shown\r\n![Screenshot 2024-12-27 at 3 46\r\n14 PM](https://github.com/user-attachments/assets/24e033d7-fb15-496a-97be-ecf78996d243)\r\n\r\n#### If the correct data is shown:\r\n![Screenshot 2024-12-27 at 3 50\r\n12 PM](https://github.com/user-attachments/assets/a13f54d8-1804-4baf-a12b-5203beb4f92d)\r\n\r\n### How to test\r\n\r\n- have a few alerts in the alerts table\r\n- open the alert details flyout for one alert and change the status\r\n(button in the header)\r\n- verify that the last status change section is shown in the `About`\r\nsection\r\n\r\n### Checklist\r\n\r\n- [x] 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/packages/kbn-i18n/README.md)\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","sha":"a4b1975fced9f5fd6c408401d19b79650a4fc56d"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Philippe Oberti <[email protected]>
- Loading branch information