Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[8.x] [SecuritySolution] Fix schedule risk engine callout when engine…
… is installed but disabled (#196496) (#196525) # Backport This will backport the following commits from `main` to `8.x`: - [[SecuritySolution] Fix schedule risk engine callout when engine is installed but disabled (#196496)](#196496) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Pablo Machado","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-10-16T10:29:26Z","message":"[SecuritySolution] Fix schedule risk engine callout when engine is installed but disabled (#196496)\n\n## Summary\r\n\r\nFix the visibility of the Schedule Risk Engine Callout inside the asset\r\ncriticality bulk upload when the risk engine is disabled.\r\nThe callout should not be displayed when the risk engine is installed\r\nbut disabled.\r\n\r\n\r\n### How to test it?\r\n* Open Kibana - Security Solution\r\n* Navigate to the risk engine page and install the risk engine\r\n* On the same page, disable the risk engine\r\n* Navigate to the asset criticality page\r\n* Successfully upload a document \r\n* You should see a \"success\" but no risk engine callout.\r\n\r\n![Screenshot 2024-10-16 at 10 41\r\n39](https://github.com/user-attachments/assets/5c8f078e-4588-434e-8c76-03d72b1c5a16)\r\n\r\n\r\n\r\n### Checklist\r\n\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":"1de6fb5b639ccfe044bf388cb301e99c19890f03","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","v9.0.0","Team: SecuritySolution","backport:prev-major","Theme: entity_analytics","Feature:Entity Analytics","Team:Entity Analytics"],"title":"[SecuritySolution] Fix schedule risk engine callout when engine is installed but disabled","number":196496,"url":"https://github.com/elastic/kibana/pull/196496","mergeCommit":{"message":"[SecuritySolution] Fix schedule risk engine callout when engine is installed but disabled (#196496)\n\n## Summary\r\n\r\nFix the visibility of the Schedule Risk Engine Callout inside the asset\r\ncriticality bulk upload when the risk engine is disabled.\r\nThe callout should not be displayed when the risk engine is installed\r\nbut disabled.\r\n\r\n\r\n### How to test it?\r\n* Open Kibana - Security Solution\r\n* Navigate to the risk engine page and install the risk engine\r\n* On the same page, disable the risk engine\r\n* Navigate to the asset criticality page\r\n* Successfully upload a document \r\n* You should see a \"success\" but no risk engine callout.\r\n\r\n![Screenshot 2024-10-16 at 10 41\r\n39](https://github.com/user-attachments/assets/5c8f078e-4588-434e-8c76-03d72b1c5a16)\r\n\r\n\r\n\r\n### Checklist\r\n\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":"1de6fb5b639ccfe044bf388cb301e99c19890f03"}},"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/196496","number":196496,"mergeCommit":{"message":"[SecuritySolution] Fix schedule risk engine callout when engine is installed but disabled (#196496)\n\n## Summary\r\n\r\nFix the visibility of the Schedule Risk Engine Callout inside the asset\r\ncriticality bulk upload when the risk engine is disabled.\r\nThe callout should not be displayed when the risk engine is installed\r\nbut disabled.\r\n\r\n\r\n### How to test it?\r\n* Open Kibana - Security Solution\r\n* Navigate to the risk engine page and install the risk engine\r\n* On the same page, disable the risk engine\r\n* Navigate to the asset criticality page\r\n* Successfully upload a document \r\n* You should see a \"success\" but no risk engine callout.\r\n\r\n![Screenshot 2024-10-16 at 10 41\r\n39](https://github.com/user-attachments/assets/5c8f078e-4588-434e-8c76-03d72b1c5a16)\r\n\r\n\r\n\r\n### Checklist\r\n\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":"1de6fb5b639ccfe044bf388cb301e99c19890f03"}}]}] BACKPORT--> Co-authored-by: Pablo Machado <[email protected]>
- Loading branch information