mirror of
https://github.com/elastic/kibana.git
synced 2025-04-23 17:28:26 -04:00
21368 commits
Author | SHA1 | Message | Date | |
---|---|---|---|---|
|
74d11ff375
|
[8.6] [ML] Fixing model testing with index field selection (#146862) (#147317)
# Backport This will backport the following commits from `main` to `8.6`: - [[ML] Fixing model testing with index field selection (#146862)](https://github.com/elastic/kibana/pull/146862) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"James Gowdy","email":"jgowdy@elastic.co"},"sourceCommit":{"committedDate":"2022-12-05T17:37:09Z","message":"[ML] Fixing model testing with index field selection (#146862)\n\nFixes issue where changing the selected field or pressing the reload\r\nexamples button causes the default field name to be added to the\r\npipeline.\r\nThe inference still works as the field is also renamed in the supplied\r\ndocs. but it does mean the pipeline doesn't really match the real index\r\nfield name and so can't be used to ingest data.\r\n\r\nThe fix is to ensure `inferrer.setInputField(..)` is called whenever the\r\nfield select changes or examples are reloaded.","sha":"f7b74d0c4ee1f17af350c89f6507a4a23719bac1","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix",":ml","backport missing","auto-backport","Feature:3rd Party Models","v8.6.0","v8.7.0"],"number":146862,"url":"https://github.com/elastic/kibana/pull/146862","mergeCommit":{"message":"[ML] Fixing model testing with index field selection (#146862)\n\nFixes issue where changing the selected field or pressing the reload\r\nexamples button causes the default field name to be added to the\r\npipeline.\r\nThe inference still works as the field is also renamed in the supplied\r\ndocs. but it does mean the pipeline doesn't really match the real index\r\nfield name and so can't be used to ingest data.\r\n\r\nThe fix is to ensure `inferrer.setInputField(..)` is called whenever the\r\nfield select changes or examples are reloaded.","sha":"f7b74d0c4ee1f17af350c89f6507a4a23719bac1"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/146862","number":146862,"mergeCommit":{"message":"[ML] Fixing model testing with index field selection (#146862)\n\nFixes issue where changing the selected field or pressing the reload\r\nexamples button causes the default field name to be added to the\r\npipeline.\r\nThe inference still works as the field is also renamed in the supplied\r\ndocs. but it does mean the pipeline doesn't really match the real index\r\nfield name and so can't be used to ingest data.\r\n\r\nThe fix is to ensure `inferrer.setInputField(..)` is called whenever the\r\nfield select changes or examples are reloaded.","sha":"f7b74d0c4ee1f17af350c89f6507a4a23719bac1"}}]}] BACKPORT--> Co-authored-by: James Gowdy <jgowdy@elastic.co> |
||
|
03db76d9a4
|
[8.6] [Form lib] Fix validate method returning wrong state when called from onChange handler (#146371) (#147303)
# Backport This will backport the following commits from `main` to `8.6`: - [[Form lib] Fix validate method returning wrong state when called from onChange handler (#146371)](https://github.com/elastic/kibana/pull/146371) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Muhammad Ibragimov","email":"53621505+mibragimov@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-12-09T04:44:51Z","message":"[Form lib] Fix validate method returning wrong state when called from onChange handler (#146371)\n\nFixes https://github.com/elastic/kibana/issues/145846\r\n\r\n### Summary\r\nThis PR fixes a bug in the form lib where the `validate` method would\r\nreturn the wrong state when called from an `onChange` handler. See\r\nhttps://github.com/elastic/kibana/issues/145846#issue-1457815157 for\r\nmore details.\r\n\r\nCo-authored-by: Muhammad Ibragimov <muhammad.ibragimov@elastic.co>\r\nCo-authored-by: Yaroslav Kuznietsov <kuznetsov.yaroslav.yk@gmail.com>\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"6814ed7e9109f0a5f90cc5e261eb0619312c78a2","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Deployment Management","release_note:skip","backport:prev-minor","v8.7.0"],"number":146371,"url":"https://github.com/elastic/kibana/pull/146371","mergeCommit":{"message":"[Form lib] Fix validate method returning wrong state when called from onChange handler (#146371)\n\nFixes https://github.com/elastic/kibana/issues/145846\r\n\r\n### Summary\r\nThis PR fixes a bug in the form lib where the `validate` method would\r\nreturn the wrong state when called from an `onChange` handler. See\r\nhttps://github.com/elastic/kibana/issues/145846#issue-1457815157 for\r\nmore details.\r\n\r\nCo-authored-by: Muhammad Ibragimov <muhammad.ibragimov@elastic.co>\r\nCo-authored-by: Yaroslav Kuznietsov <kuznetsov.yaroslav.yk@gmail.com>\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"6814ed7e9109f0a5f90cc5e261eb0619312c78a2"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/146371","number":146371,"mergeCommit":{"message":"[Form lib] Fix validate method returning wrong state when called from onChange handler (#146371)\n\nFixes https://github.com/elastic/kibana/issues/145846\r\n\r\n### Summary\r\nThis PR fixes a bug in the form lib where the `validate` method would\r\nreturn the wrong state when called from an `onChange` handler. See\r\nhttps://github.com/elastic/kibana/issues/145846#issue-1457815157 for\r\nmore details.\r\n\r\nCo-authored-by: Muhammad Ibragimov <muhammad.ibragimov@elastic.co>\r\nCo-authored-by: Yaroslav Kuznietsov <kuznetsov.yaroslav.yk@gmail.com>\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"6814ed7e9109f0a5f90cc5e261eb0619312c78a2"}}]}] BACKPORT--> Co-authored-by: Muhammad Ibragimov <53621505+mibragimov@users.noreply.github.com> |
||
|
5e71a52c04
|
[8.6] Properly re-expose close method from the createPointInTimeFinderDecryptedAsInternalUser API. (#147241) (#147258)
# Backport This will backport the following commits from `main` to `8.6`: - [Properly re-expose `close` method from the `createPointInTimeFinderDecryptedAsInternalUser` API. (#147241)](https://github.com/elastic/kibana/pull/147241) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Aleh Zasypkin","email":"aleh.zasypkin@elastic.co"},"sourceCommit":{"committedDate":"2022-12-08T15:00:20Z","message":"Properly re-expose `close` method from the `createPointInTimeFinderDecryptedAsInternalUser` API. (#147241)","sha":"12e9e35eb642b3c1ba4f9c45a08929fba763da9d","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","Team:Security","release_note:skip","Feature:Security/Encrypted Saved Objects","backport:prev-minor","v8.7.0"],"number":147241,"url":"https://github.com/elastic/kibana/pull/147241","mergeCommit":{"message":"Properly re-expose `close` method from the `createPointInTimeFinderDecryptedAsInternalUser` API. (#147241)","sha":"12e9e35eb642b3c1ba4f9c45a08929fba763da9d"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147241","number":147241,"mergeCommit":{"message":"Properly re-expose `close` method from the `createPointInTimeFinderDecryptedAsInternalUser` API. (#147241)","sha":"12e9e35eb642b3c1ba4f9c45a08929fba763da9d"}}]}] BACKPORT--> Co-authored-by: Aleh Zasypkin <aleh.zasypkin@elastic.co> |
||
|
fd4a6fc293
|
[8.6] [Fleet] cancel tasks when 3rd retry failed (#147190) (#147230)
# Backport This will backport the following commits from `main` to `8.6`: - [[Fleet] cancel tasks when 3rd retry failed (#147190)](https://github.com/elastic/kibana/pull/147190) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Julia Bardi","email":"90178898+juliaElastic@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-12-08T08:14:33Z","message":"[Fleet] cancel tasks when 3rd retry failed (#147190)\n\n## Summary\r\n\r\nRelated to https://github.com/elastic/kibana/issues/144161\r\n\r\nFound that on a bulk update tags task failure, the task didn't stop\r\nafter 3 retries (should be over in less then a minute), the retries kept\r\nhappening for 2 hours.\r\nThis change removes the retry task if 3 retries are reached.\r\n\r\nAlso testing in cloud deployment to see if the tags error can be\r\nreproduced with this fix.\r\nI could reproduce the reported error locally, and seeing it goes away\r\nwith this fix.\r\n\r\nTo verify:\r\n- Add at least 50k agents with the `create_agents` script in kibana repo\r\n- open Kibana, select the 50k agents, and open Actions / Add tags\r\n- Try this in a few seconds: add 2 new tags, and remove one of them\r\n- Wait about 30s, the agents should reflect the changes\r\n- Check the logs to see that the tasks are removed after 3rd retry is\r\nreached or successful.\r\n- Check that there are no more running tasks. Any running task can be\r\nfound in Kibana Console by running this query: `GET\r\n.kibana_task_manager/_search?q=task.taskType:\"fleet:update_agent_tags:retry\"`\r\n\r\nLocally simulated an error to test that the retry (and check) task is\r\nremoved:\r\n\r\n```\r\n[2022-12-07T15:52:16.415+01:00][ERROR][plugins.fleet] Retry #3 of task fleet:update_agent_tags:retry:848984ab-c11d-4ebe-8d1f-606143dd656b failed: failing task\r\n[2022-12-07T15:52:16.416+01:00][WARN ][plugins.fleet] Stopping after 3rd retry. Error: failing task\r\n[2022-12-07T15:52:16.416+01:00][INFO ][plugins.fleet] Removing task fleet:update_agent_tags:retry:check:848984ab-c11d-4ebe-8d1f-606143dd656b\r\n[2022-12-07T15:52:16.416+01:00][INFO ][plugins.fleet] Removing task fleet:update_agent_tags:retry:848984ab-c11d-4ebe-8d1f-606143dd656b\r\n```","sha":"431c32b894077fc5910380252086442083734fce","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","v8.7.0","v8.6.1"],"number":147190,"url":"https://github.com/elastic/kibana/pull/147190","mergeCommit":{"message":"[Fleet] cancel tasks when 3rd retry failed (#147190)\n\n## Summary\r\n\r\nRelated to https://github.com/elastic/kibana/issues/144161\r\n\r\nFound that on a bulk update tags task failure, the task didn't stop\r\nafter 3 retries (should be over in less then a minute), the retries kept\r\nhappening for 2 hours.\r\nThis change removes the retry task if 3 retries are reached.\r\n\r\nAlso testing in cloud deployment to see if the tags error can be\r\nreproduced with this fix.\r\nI could reproduce the reported error locally, and seeing it goes away\r\nwith this fix.\r\n\r\nTo verify:\r\n- Add at least 50k agents with the `create_agents` script in kibana repo\r\n- open Kibana, select the 50k agents, and open Actions / Add tags\r\n- Try this in a few seconds: add 2 new tags, and remove one of them\r\n- Wait about 30s, the agents should reflect the changes\r\n- Check the logs to see that the tasks are removed after 3rd retry is\r\nreached or successful.\r\n- Check that there are no more running tasks. Any running task can be\r\nfound in Kibana Console by running this query: `GET\r\n.kibana_task_manager/_search?q=task.taskType:\"fleet:update_agent_tags:retry\"`\r\n\r\nLocally simulated an error to test that the retry (and check) task is\r\nremoved:\r\n\r\n```\r\n[2022-12-07T15:52:16.415+01:00][ERROR][plugins.fleet] Retry #3 of task fleet:update_agent_tags:retry:848984ab-c11d-4ebe-8d1f-606143dd656b failed: failing task\r\n[2022-12-07T15:52:16.416+01:00][WARN ][plugins.fleet] Stopping after 3rd retry. Error: failing task\r\n[2022-12-07T15:52:16.416+01:00][INFO ][plugins.fleet] Removing task fleet:update_agent_tags:retry:check:848984ab-c11d-4ebe-8d1f-606143dd656b\r\n[2022-12-07T15:52:16.416+01:00][INFO ][plugins.fleet] Removing task fleet:update_agent_tags:retry:848984ab-c11d-4ebe-8d1f-606143dd656b\r\n```","sha":"431c32b894077fc5910380252086442083734fce"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147190","number":147190,"mergeCommit":{"message":"[Fleet] cancel tasks when 3rd retry failed (#147190)\n\n## Summary\r\n\r\nRelated to https://github.com/elastic/kibana/issues/144161\r\n\r\nFound that on a bulk update tags task failure, the task didn't stop\r\nafter 3 retries (should be over in less then a minute), the retries kept\r\nhappening for 2 hours.\r\nThis change removes the retry task if 3 retries are reached.\r\n\r\nAlso testing in cloud deployment to see if the tags error can be\r\nreproduced with this fix.\r\nI could reproduce the reported error locally, and seeing it goes away\r\nwith this fix.\r\n\r\nTo verify:\r\n- Add at least 50k agents with the `create_agents` script in kibana repo\r\n- open Kibana, select the 50k agents, and open Actions / Add tags\r\n- Try this in a few seconds: add 2 new tags, and remove one of them\r\n- Wait about 30s, the agents should reflect the changes\r\n- Check the logs to see that the tasks are removed after 3rd retry is\r\nreached or successful.\r\n- Check that there are no more running tasks. Any running task can be\r\nfound in Kibana Console by running this query: `GET\r\n.kibana_task_manager/_search?q=task.taskType:\"fleet:update_agent_tags:retry\"`\r\n\r\nLocally simulated an error to test that the retry (and check) task is\r\nremoved:\r\n\r\n```\r\n[2022-12-07T15:52:16.415+01:00][ERROR][plugins.fleet] Retry #3 of task fleet:update_agent_tags:retry:848984ab-c11d-4ebe-8d1f-606143dd656b failed: failing task\r\n[2022-12-07T15:52:16.416+01:00][WARN ][plugins.fleet] Stopping after 3rd retry. Error: failing task\r\n[2022-12-07T15:52:16.416+01:00][INFO ][plugins.fleet] Removing task fleet:update_agent_tags:retry:check:848984ab-c11d-4ebe-8d1f-606143dd656b\r\n[2022-12-07T15:52:16.416+01:00][INFO ][plugins.fleet] Removing task fleet:update_agent_tags:retry:848984ab-c11d-4ebe-8d1f-606143dd656b\r\n```","sha":"431c32b894077fc5910380252086442083734fce"}},{"branch":"8.6","label":"v8.6.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com> |
||
|
b183fc5e1e
|
[8.6] [Fleet] Rename parameter source_uri to sourceURI in agent policy (#146303) (#147204)
# Backport This will backport the following commits from `main` to `8.6`: - [[Fleet] Rename parameter source_uri to sourceURI in agent policy (#146303)](https://github.com/elastic/kibana/pull/146303) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Cristina Amico","email":"criamico@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-11-30T13:46:19Z","message":"[Fleet] Rename parameter source_uri to sourceURI in agent policy (#146303)\n\n## Summary\r\nCloses https://github.com/elastic/kibana/issues/141470\r\n\r\nThe source_uri parameter in agent policy should actually be `sourceURI`.\r\nI didn't change the parameter everywhere in the code but only where is\r\nexposed to the agent policy/actions, since in other places is only used\r\ninternally by fleet.\r\n\r\n<img width=\"748\" alt=\"Screenshot 2022-11-24 at 15 59 54\"\r\nsrc=\"https://user-images.githubusercontent.com/16084106/203814663-b9e37be2-5017-4aba-94da-9f928de490c8.png\">\r\n\r\n\r\n### Checklist\r\n- [ ] [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\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"fbd040febb23db22a38ee40b0efdedaa65508f4d","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","backport:prev-minor","v8.7.0"],"number":146303,"url":"https://github.com/elastic/kibana/pull/146303","mergeCommit":{"message":"[Fleet] Rename parameter source_uri to sourceURI in agent policy (#146303)\n\n## Summary\r\nCloses https://github.com/elastic/kibana/issues/141470\r\n\r\nThe source_uri parameter in agent policy should actually be `sourceURI`.\r\nI didn't change the parameter everywhere in the code but only where is\r\nexposed to the agent policy/actions, since in other places is only used\r\ninternally by fleet.\r\n\r\n<img width=\"748\" alt=\"Screenshot 2022-11-24 at 15 59 54\"\r\nsrc=\"https://user-images.githubusercontent.com/16084106/203814663-b9e37be2-5017-4aba-94da-9f928de490c8.png\">\r\n\r\n\r\n### Checklist\r\n- [ ] [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\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"fbd040febb23db22a38ee40b0efdedaa65508f4d"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/146303","number":146303,"mergeCommit":{"message":"[Fleet] Rename parameter source_uri to sourceURI in agent policy (#146303)\n\n## Summary\r\nCloses https://github.com/elastic/kibana/issues/141470\r\n\r\nThe source_uri parameter in agent policy should actually be `sourceURI`.\r\nI didn't change the parameter everywhere in the code but only where is\r\nexposed to the agent policy/actions, since in other places is only used\r\ninternally by fleet.\r\n\r\n<img width=\"748\" alt=\"Screenshot 2022-11-24 at 15 59 54\"\r\nsrc=\"https://user-images.githubusercontent.com/16084106/203814663-b9e37be2-5017-4aba-94da-9f928de490c8.png\">\r\n\r\n\r\n### Checklist\r\n- [ ] [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\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"fbd040febb23db22a38ee40b0efdedaa65508f4d"}}]}] BACKPORT--> Co-authored-by: Cristina Amico <criamico@users.noreply.github.com> |
||
|
a1da1113a1
|
[8.6] [Security] Fix integration card(s) wrapped in EuiTour not inheriting grid row height (#147041) (#147203)
# Backport This will backport the following commits from `main` to `8.6`: - [[Security] Fix integration card(s) wrapped in EuiTour not inheriting grid row height (#147041)](https://github.com/elastic/kibana/pull/147041) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Cee","email":"constancecchen@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-12-07T17:13:10Z","message":"[Security] Fix integration card(s) wrapped in EuiTour not inheriting grid row height (#147041)\n\ncloses https://github.com/elastic/kibana/issues/147007","sha":"7e7a9fcc45bd97cb84e41f47ec784c67f7da9a55","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","v8.6.0","v8.7.0"],"number":147041,"url":"https://github.com/elastic/kibana/pull/147041","mergeCommit":{"message":"[Security] Fix integration card(s) wrapped in EuiTour not inheriting grid row height (#147041)\n\ncloses https://github.com/elastic/kibana/issues/147007","sha":"7e7a9fcc45bd97cb84e41f47ec784c67f7da9a55"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147041","number":147041,"mergeCommit":{"message":"[Security] Fix integration card(s) wrapped in EuiTour not inheriting grid row height (#147041)\n\ncloses https://github.com/elastic/kibana/issues/147007","sha":"7e7a9fcc45bd97cb84e41f47ec784c67f7da9a55"}}]}] BACKPORT--> Co-authored-by: Cee <constancecchen@users.noreply.github.com> |
||
|
f9f1c86186
|
[8.6] [Security Solution] [Exceptions] fixes error not displaying when importing invalid exception list (#147143) (#147192)
# Backport This will backport the following commits from `main` to `8.6`: - [[Security Solution] [Exceptions] fixes error not displaying when importing invalid exception list (#147143)](https://github.com/elastic/kibana/pull/147143) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Devin W. Hurley","email":"devin.hurley@elastic.co"},"sourceCommit":{"committedDate":"2022-12-07T15:06:24Z","message":"[Security Solution] [Exceptions] fixes error not displaying when importing invalid exception list (#147143)\n\n## Summary\r\n\r\nRef: https://github.com/elastic/kibana/issues/146871\r\n\r\nAlso restores functionality where if a user tries to import an exception\r\nlist that already exists within the system, they are offered up options\r\nas to how to proceed; either by overwriting the current list or\r\nimporting this list as a different list.","sha":"6d5b29263821b96ab2fdba8c92d59e0a264b91c1","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["review","release_note:skip","impact:critical","Feature:Rule Exceptions","Team:Security Solution Platform","v8.6.0","v8.7.0"],"number":147143,"url":"https://github.com/elastic/kibana/pull/147143","mergeCommit":{"message":"[Security Solution] [Exceptions] fixes error not displaying when importing invalid exception list (#147143)\n\n## Summary\r\n\r\nRef: https://github.com/elastic/kibana/issues/146871\r\n\r\nAlso restores functionality where if a user tries to import an exception\r\nlist that already exists within the system, they are offered up options\r\nas to how to proceed; either by overwriting the current list or\r\nimporting this list as a different list.","sha":"6d5b29263821b96ab2fdba8c92d59e0a264b91c1"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147143","number":147143,"mergeCommit":{"message":"[Security Solution] [Exceptions] fixes error not displaying when importing invalid exception list (#147143)\n\n## Summary\r\n\r\nRef: https://github.com/elastic/kibana/issues/146871\r\n\r\nAlso restores functionality where if a user tries to import an exception\r\nlist that already exists within the system, they are offered up options\r\nas to how to proceed; either by overwriting the current list or\r\nimporting this list as a different list.","sha":"6d5b29263821b96ab2fdba8c92d59e0a264b91c1"}}]}] BACKPORT--> Co-authored-by: Devin W. Hurley <devin.hurley@elastic.co> |
||
|
b16ce7f6d4
|
[8.6] [Index Management] Fix component template usage count sort (#147141) (#147184)
# Backport This will backport the following commits from `main` to `8.6`: - [[Index Management] Fix component template usage count sort (#147141)](https://github.com/elastic/kibana/pull/147141) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Alison Goryachev","email":"alison.goryachev@elastic.co"},"sourceCommit":{"committedDate":"2022-12-07T13:21:50Z","message":"[Index Management] Fix component template usage count sort (#147141)","sha":"031d8a8cead4840659a92e2694ed58603137aab9","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Feature:Index Management","Team:Deployment Management","backport:prev-minor","v8.6.0","v8.7.0"],"number":147141,"url":"https://github.com/elastic/kibana/pull/147141","mergeCommit":{"message":"[Index Management] Fix component template usage count sort (#147141)","sha":"031d8a8cead4840659a92e2694ed58603137aab9"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147141","number":147141,"mergeCommit":{"message":"[Index Management] Fix component template usage count sort (#147141)","sha":"031d8a8cead4840659a92e2694ed58603137aab9"}}]}] BACKPORT--> Co-authored-by: Alison Goryachev <alison.goryachev@elastic.co> |
||
|
b91dfc93e3
|
[8.6] changed agent versions to agents per version telemetry (#147164) (#147169)
# Backport This will backport the following commits from `main` to `8.6`: - [changed agent versions to agents per version telemetry (#147164)](https://github.com/elastic/kibana/pull/147164) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Julia Bardi","email":"90178898+juliaElastic@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-12-07T11:23:30Z","message":"changed agent versions to agents per version telemetry (#147164)\n\n## Summary\r\n\r\nChanged the list of agent versions to agent count per version in\r\nfleet-usages telemetry as requested\r\n[here](https://github.com/elastic/kibana/pull/145353#issuecomment-1331783758).\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":"e771fc8e9fa5f551d8692fc8558e5d7e2cbfef79","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","v8.7.0","v8.6.1"],"number":147164,"url":"https://github.com/elastic/kibana/pull/147164","mergeCommit":{"message":"changed agent versions to agents per version telemetry (#147164)\n\n## Summary\r\n\r\nChanged the list of agent versions to agent count per version in\r\nfleet-usages telemetry as requested\r\n[here](https://github.com/elastic/kibana/pull/145353#issuecomment-1331783758).\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":"e771fc8e9fa5f551d8692fc8558e5d7e2cbfef79"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147164","number":147164,"mergeCommit":{"message":"changed agent versions to agents per version telemetry (#147164)\n\n## Summary\r\n\r\nChanged the list of agent versions to agent count per version in\r\nfleet-usages telemetry as requested\r\n[here](https://github.com/elastic/kibana/pull/145353#issuecomment-1331783758).\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":"e771fc8e9fa5f551d8692fc8558e5d7e2cbfef79"}},{"branch":"8.6","label":"v8.6.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com> Co-authored-by: Julia Bardi <julia.bardi@elastic.co> |
||
|
11cde5b883
|
[8.6] [ML] Add API tests for index exists endpoint (#146400) (#147181)
# Backport This will backport the following commits from `main` to `8.6`: - [[ML] Add API tests for index exists endpoint (#146400)](https://github.com/elastic/kibana/pull/146400) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Pete Harverson","email":"pete@elastic.co"},"sourceCommit":{"committedDate":"2022-12-07T13:12:17Z","message":"[ML] Add API tests for index exists endpoint (#146400)\n\n## Summary\r\n\r\nAdds tests to check the response of the index exists endpoint:\r\n\r\n```\r\n/api/ml/index_exists\r\n```\r\n\r\nAlso fixed the behavior of the endpoint when passed an index with a\r\nwilcard expression so that it no longer returns `true` if an index does\r\nnot exist matching the expression by adding `allow_no_indices: false` to\r\nthe query parameters.\r\n\r\nPart of https://github.com/elastic/kibana/issues/142456\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\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"4294e3b17f559a0073f5453a47df7e9dc83c58ba","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["review",":ml","release_note:skip","test-api-integration","v8.6.0","v8.7.0"],"number":146400,"url":"https://github.com/elastic/kibana/pull/146400","mergeCommit":{"message":"[ML] Add API tests for index exists endpoint (#146400)\n\n## Summary\r\n\r\nAdds tests to check the response of the index exists endpoint:\r\n\r\n```\r\n/api/ml/index_exists\r\n```\r\n\r\nAlso fixed the behavior of the endpoint when passed an index with a\r\nwilcard expression so that it no longer returns `true` if an index does\r\nnot exist matching the expression by adding `allow_no_indices: false` to\r\nthe query parameters.\r\n\r\nPart of https://github.com/elastic/kibana/issues/142456\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\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"4294e3b17f559a0073f5453a47df7e9dc83c58ba"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/146400","number":146400,"mergeCommit":{"message":"[ML] Add API tests for index exists endpoint (#146400)\n\n## Summary\r\n\r\nAdds tests to check the response of the index exists endpoint:\r\n\r\n```\r\n/api/ml/index_exists\r\n```\r\n\r\nAlso fixed the behavior of the endpoint when passed an index with a\r\nwilcard expression so that it no longer returns `true` if an index does\r\nnot exist matching the expression by adding `allow_no_indices: false` to\r\nthe query parameters.\r\n\r\nPart of https://github.com/elastic/kibana/issues/142456\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\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"4294e3b17f559a0073f5453a47df7e9dc83c58ba"}}]}] BACKPORT--> Co-authored-by: Pete Harverson <pete@elastic.co> |
||
|
f0dd3dcd36 | skip flaky suite (#145187) | ||
|
3f8f60086b
|
[8.6] [Security Solution] Fix filtering on searching for lists (#147096) (#147104)
# Backport This will backport the following commits from `main` to `8.6`: - [ [Security Solution] Fix filtering on searching for lists (#147096)](https://github.com/elastic/kibana/pull/147096) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Wafaa Nasr","email":"wafaa.nasr@elastic.co"},"sourceCommit":{"committedDate":"2022-12-06T14:09:45Z","message":" [Security Solution] Fix filtering on searching for lists (#147096)\n\n## Summary\r\n\r\n- Addresses https://github.com/elastic/kibana/issues/145677\r\n- Use the filter of the list type every time we call the fetch list.\r\n- On search we need to append the ` types:\r\n[ExceptionListTypeEnum.DETECTION, ExceptionListTypeEnum.ENDPOINT],` to\r\nthe users' filters, to filter out the other list type that should not be\r\ndisplayed on `Rule Exceptions` page","sha":"727df5e36b22a078623111825ae89335533cc59e","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","ci:cloud-deploy","v8.6.0","v8.7.0"],"number":147096,"url":"https://github.com/elastic/kibana/pull/147096","mergeCommit":{"message":" [Security Solution] Fix filtering on searching for lists (#147096)\n\n## Summary\r\n\r\n- Addresses https://github.com/elastic/kibana/issues/145677\r\n- Use the filter of the list type every time we call the fetch list.\r\n- On search we need to append the ` types:\r\n[ExceptionListTypeEnum.DETECTION, ExceptionListTypeEnum.ENDPOINT],` to\r\nthe users' filters, to filter out the other list type that should not be\r\ndisplayed on `Rule Exceptions` page","sha":"727df5e36b22a078623111825ae89335533cc59e"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147096","number":147096,"mergeCommit":{"message":" [Security Solution] Fix filtering on searching for lists (#147096)\n\n## Summary\r\n\r\n- Addresses https://github.com/elastic/kibana/issues/145677\r\n- Use the filter of the list type every time we call the fetch list.\r\n- On search we need to append the ` types:\r\n[ExceptionListTypeEnum.DETECTION, ExceptionListTypeEnum.ENDPOINT],` to\r\nthe users' filters, to filter out the other list type that should not be\r\ndisplayed on `Rule Exceptions` page","sha":"727df5e36b22a078623111825ae89335533cc59e"}}]}] BACKPORT--> Co-authored-by: Wafaa Nasr <wafaa.nasr@elastic.co> |
||
|
06e6f19d32
|
[8.6] Fix z-index for exceptions (#147098) (#147105)
# Backport This will backport the following commits from `main` to `8.6`: - [Fix z-index for exceptions (#147098)](https://github.com/elastic/kibana/pull/147098) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Khristinin Nikita","email":"nikita.khristinin@elastic.co"},"sourceCommit":{"committedDate":"2022-12-06T14:09:58Z","message":"Fix z-index for exceptions (#147098)\n\nClose: https://github.com/elastic/kibana/issues/147066","sha":"da793b7a3cb0f7b22bef07fc936fb0679e8e6b30","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","v8.7.0"],"number":147098,"url":"https://github.com/elastic/kibana/pull/147098","mergeCommit":{"message":"Fix z-index for exceptions (#147098)\n\nClose: https://github.com/elastic/kibana/issues/147066","sha":"da793b7a3cb0f7b22bef07fc936fb0679e8e6b30"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147098","number":147098,"mergeCommit":{"message":"Fix z-index for exceptions (#147098)\n\nClose: https://github.com/elastic/kibana/issues/147066","sha":"da793b7a3cb0f7b22bef07fc936fb0679e8e6b30"}}]}] BACKPORT--> Co-authored-by: Khristinin Nikita <nikita.khristinin@elastic.co> |
||
|
48f43eb2a9
|
[8.6] [Security Solution]: List details page Save btn frontend + refresh exceptions in Rule Exceptions (#147021) (#147101)
# Backport This will backport the following commits from `main` to `8.6`: - [[Security Solution]: List details page Save btn frontend + refresh exceptions in Rule Exceptions (#147021)](https://github.com/elastic/kibana/pull/147021) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Wafaa Nasr","email":"wafaa.nasr@elastic.co"},"sourceCommit":{"committedDate":"2022-12-06T13:33:15Z","message":"[Security Solution]: List details page Save btn frontend + refresh exceptions in Rule Exceptions (#147021)\n\n## Summary\r\n\r\n- Add specific translations\r\n- Fix the frontend part for\r\nhttps://github.com/elastic/kibana/issues/146980 by clearing the `Save`\r\nbutton state and show the correct error\r\n- Refresh exceptions in `Rule exceptions` after a new item is created\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"e4a15a7d722e5615bff64d2366c0d6a57aa57c2d","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","ci:cloud-deploy","v8.6.0","v8.7.0"],"number":147021,"url":"https://github.com/elastic/kibana/pull/147021","mergeCommit":{"message":"[Security Solution]: List details page Save btn frontend + refresh exceptions in Rule Exceptions (#147021)\n\n## Summary\r\n\r\n- Add specific translations\r\n- Fix the frontend part for\r\nhttps://github.com/elastic/kibana/issues/146980 by clearing the `Save`\r\nbutton state and show the correct error\r\n- Refresh exceptions in `Rule exceptions` after a new item is created\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"e4a15a7d722e5615bff64d2366c0d6a57aa57c2d"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147021","number":147021,"mergeCommit":{"message":"[Security Solution]: List details page Save btn frontend + refresh exceptions in Rule Exceptions (#147021)\n\n## Summary\r\n\r\n- Add specific translations\r\n- Fix the frontend part for\r\nhttps://github.com/elastic/kibana/issues/146980 by clearing the `Save`\r\nbutton state and show the correct error\r\n- Refresh exceptions in `Rule exceptions` after a new item is created\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"e4a15a7d722e5615bff64d2366c0d6a57aa57c2d"}}]}] BACKPORT--> Co-authored-by: Wafaa Nasr <wafaa.nasr@elastic.co> |
||
|
bfeda52c26
|
[8.6] Fix default exception validation (#147038) (#147089)
# Backport This will backport the following commits from `main` to `8.6`: - [Fix default exception validation (#147038)](https://github.com/elastic/kibana/pull/147038) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Khristinin Nikita","email":"nikita.khristinin@elastic.co"},"sourceCommit":{"committedDate":"2022-12-06T11:59:10Z","message":"Fix default exception validation (#147038)\n\n## Summary\r\nValidation of default exception list for rule mutation works with id or\r\nrule_id property\r\n\r\nRelated: https://github.com/elastic/kibana/issues/146980\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"5fc860ce3104588bbc2de7af93060f1550f9efad","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","v8.7.0"],"number":147038,"url":"https://github.com/elastic/kibana/pull/147038","mergeCommit":{"message":"Fix default exception validation (#147038)\n\n## Summary\r\nValidation of default exception list for rule mutation works with id or\r\nrule_id property\r\n\r\nRelated: https://github.com/elastic/kibana/issues/146980\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"5fc860ce3104588bbc2de7af93060f1550f9efad"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147038","number":147038,"mergeCommit":{"message":"Fix default exception validation (#147038)\n\n## Summary\r\nValidation of default exception list for rule mutation works with id or\r\nrule_id property\r\n\r\nRelated: https://github.com/elastic/kibana/issues/146980\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"5fc860ce3104588bbc2de7af93060f1550f9efad"}}]}] BACKPORT--> Co-authored-by: Khristinin Nikita <nikita.khristinin@elastic.co> |
||
|
487c98381a
|
[8.6] [Security Solution][Rules] Don't display new features tour if guided onboarding is active (#146902) (#147073)
# Backport This will backport the following commits from `main` to `8.6`: - [[Security Solution][Rules] Don't display new features tour if guided onboarding is active (#146902)](https://github.com/elastic/kibana/pull/146902) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Marshall Main","email":"55718608+marshallmain@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-12-06T09:34:42Z","message":"[Security Solution][Rules] Don't display new features tour if guided onboarding is active (#146902)\n\nDue to the location of the guided onboarding tour, it can overlap with\r\nthe new features tour when a user is doing guided onboarding. This PR\r\ndisables the new features tour if the user is in the middle of guided\r\nonboarding.\r\n\r\nThere is still a remaining issue where after the user completes the 3\r\nsteps of the guided onboarding on the rules page, the\r\n`isGuideStepActive# Backport This will backport the following commits from `main` to `8.6`: - [[Security Solution][Rules] Don't display new features tour if guided onboarding is active (#146902)](https://github.com/elastic/kibana/pull/146902) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT API returns `false` even though there is still a\r\ntooltip open for the `Continue with the guide` option. The new features\r\ntour overlaps with this option.\r\n\r\n","sha":"6d12ced52b554c8e6297372a4daf52ef26f134ac","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team: SecuritySolution","Team:Detection Alerts","v8.6.0","v8.7.0"],"number":146902,"url":"https://github.com/elastic/kibana/pull/146902","mergeCommit":{"message":"[Security Solution][Rules] Don't display new features tour if guided onboarding is active (#146902)\n\nDue to the location of the guided onboarding tour, it can overlap with\r\nthe new features tour when a user is doing guided onboarding. This PR\r\ndisables the new features tour if the user is in the middle of guided\r\nonboarding.\r\n\r\nThere is still a remaining issue where after the user completes the 3\r\nsteps of the guided onboarding on the rules page, the\r\n`isGuideStepActive# Backport This will backport the following commits from `main` to `8.6`: - [[Security Solution][Rules] Don't display new features tour if guided onboarding is active (#146902)](https://github.com/elastic/kibana/pull/146902) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT API returns `false` even though there is still a\r\ntooltip open for the `Continue with the guide` option. The new features\r\ntour overlaps with this option.\r\n\r\n","sha":"6d12ced52b554c8e6297372a4daf52ef26f134ac"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/146902","number":146902,"mergeCommit":{"message":"[Security Solution][Rules] Don't display new features tour if guided onboarding is active (#146902)\n\nDue to the location of the guided onboarding tour, it can overlap with\r\nthe new features tour when a user is doing guided onboarding. This PR\r\ndisables the new features tour if the user is in the middle of guided\r\nonboarding.\r\n\r\nThere is still a remaining issue where after the user completes the 3\r\nsteps of the guided onboarding on the rules page, the\r\n`isGuideStepActive# Backport This will backport the following commits from `main` to `8.6`: - [[Security Solution][Rules] Don't display new features tour if guided onboarding is active (#146902)](https://github.com/elastic/kibana/pull/146902) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT API returns `false` even though there is still a\r\ntooltip open for the `Continue with the guide` option. The new features\r\ntour overlaps with this option.\r\n\r\n","sha":"6d12ced52b554c8e6297372a4daf52ef26f134ac"}}]}] BACKPORT--> Co-authored-by: Marshall Main <55718608+marshallmain@users.noreply.github.com> |
||
|
33c8b50323
|
[8.6] Invalidate cache for rules, after add shared exception (#146979) (#147074)
# Backport This will backport the following commits from `main` to `8.6`: - [Invalidate cache for rules, after add shared exception (#146979)](https://github.com/elastic/kibana/pull/146979) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Khristinin Nikita","email":"nikita.khristinin@elastic.co"},"sourceCommit":{"committedDate":"2022-12-06T09:37:46Z","message":"Invalidate cache for rules, after add shared exception (#146979)\n\n## Invalidate cache for rules, after adding shared exception\r\n\r\nRelated:\r\nhttps://github.com/elastic/kibana/issues/146962\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"ab8993679fbd199dfaf80c2ea96d480ba306a82a","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","ci:cloud-deploy","v8.7.0"],"number":146979,"url":"https://github.com/elastic/kibana/pull/146979","mergeCommit":{"message":"Invalidate cache for rules, after add shared exception (#146979)\n\n## Invalidate cache for rules, after adding shared exception\r\n\r\nRelated:\r\nhttps://github.com/elastic/kibana/issues/146962\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"ab8993679fbd199dfaf80c2ea96d480ba306a82a"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/146979","number":146979,"mergeCommit":{"message":"Invalidate cache for rules, after add shared exception (#146979)\n\n## Invalidate cache for rules, after adding shared exception\r\n\r\nRelated:\r\nhttps://github.com/elastic/kibana/issues/146962\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"ab8993679fbd199dfaf80c2ea96d480ba306a82a"}}]}] BACKPORT--> Co-authored-by: Khristinin Nikita <nikita.khristinin@elastic.co> |
||
|
74d4b3c710
|
[8.6] [Uptime] monitor management - adjust deletion logic (#146908) (#147060)
# Backport This will backport the following commits from `main` to `8.6`: - [[Uptime] monitor management - adjust deletion logic (#146908)](https://github.com/elastic/kibana/pull/146908) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Dominique Clarke","email":"dominique.clarke@elastic.co"},"sourceCommit":{"committedDate":"2022-12-05T18:51:08Z","message":"[Uptime] monitor management - adjust deletion logic (#146908)\n\n## Summary\r\n\r\nResolves https://github.com/elastic/kibana/issues/146932\r\n\r\nAdjusts monitor delete logic for Uptime to ensure that multiple monitors\r\nare able to be deleted in a row.\r\n\r\n### Testing\r\n1. Create at least two monitors\r\n2. Navigate to Uptime monitor management. Delete a monitor. Ensure the\r\nsuccess toast appears and the monitor is removed from the monitor list\r\n3. Delete a second monitor. Ensure the success toast appears and the\r\nmonitor is removed from the list.\r\n\r\nCo-authored-by: shahzad31 <shahzad31comp@gmail.com>","sha":"7e9f57ccce7a01883251928297411b9b579f97ab","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","Team:uptime","release_note:skip","v8.6.0","v8.7.0"],"number":146908,"url":"https://github.com/elastic/kibana/pull/146908","mergeCommit":{"message":"[Uptime] monitor management - adjust deletion logic (#146908)\n\n## Summary\r\n\r\nResolves https://github.com/elastic/kibana/issues/146932\r\n\r\nAdjusts monitor delete logic for Uptime to ensure that multiple monitors\r\nare able to be deleted in a row.\r\n\r\n### Testing\r\n1. Create at least two monitors\r\n2. Navigate to Uptime monitor management. Delete a monitor. Ensure the\r\nsuccess toast appears and the monitor is removed from the monitor list\r\n3. Delete a second monitor. Ensure the success toast appears and the\r\nmonitor is removed from the list.\r\n\r\nCo-authored-by: shahzad31 <shahzad31comp@gmail.com>","sha":"7e9f57ccce7a01883251928297411b9b579f97ab"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/146908","number":146908,"mergeCommit":{"message":"[Uptime] monitor management - adjust deletion logic (#146908)\n\n## Summary\r\n\r\nResolves https://github.com/elastic/kibana/issues/146932\r\n\r\nAdjusts monitor delete logic for Uptime to ensure that multiple monitors\r\nare able to be deleted in a row.\r\n\r\n### Testing\r\n1. Create at least two monitors\r\n2. Navigate to Uptime monitor management. Delete a monitor. Ensure the\r\nsuccess toast appears and the monitor is removed from the monitor list\r\n3. Delete a second monitor. Ensure the success toast appears and the\r\nmonitor is removed from the list.\r\n\r\nCo-authored-by: shahzad31 <shahzad31comp@gmail.com>","sha":"7e9f57ccce7a01883251928297411b9b579f97ab"}}]}] BACKPORT--> Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com> |
||
|
9ed9db0fac
|
[8.6] [Security Solution] [Exceptions] Only use z-index 5000 when exceptions within timeline (#147024) (#147055)
# Backport This will backport the following commits from `main` to `8.6`: - [[Security Solution] [Exceptions] Only use z-index 5000 when exceptions within timeline (#147024)](https://github.com/elastic/kibana/pull/147024) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Kevin Qualters","email":"56408403+kqualters-elastic@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-12-05T22:06:36Z","message":"[Security Solution] [Exceptions] Only use z-index 5000 when exceptions within timeline (#147024)\n\n## Summary\r\nThis pr is a bit of a hack to get around an issue with eui portals and\r\nthe z-index of the timeline, as the tags super select that is displayed\r\nwhen the exceptions flyout is opened when not specifically for a rule\r\ninstance, renders below the flyout due to z-index of 5000. This change\r\nmakes it so that the flyout has a z-index of 1000 in that case, and 5000\r\nin the timeline view, so that all elements are visible as expected.\r\n\r\n\r\nhttps://user-images.githubusercontent.com/56408403/205704409-9379e5af-2f01-45f0-b5d9-8479ac892b65.mov","sha":"83a334974c9d15ab3b45a5130979dcf5f6212382","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Feature:Rule Exceptions","v8.6.0","v8.7.0"],"number":147024,"url":"https://github.com/elastic/kibana/pull/147024","mergeCommit":{"message":"[Security Solution] [Exceptions] Only use z-index 5000 when exceptions within timeline (#147024)\n\n## Summary\r\nThis pr is a bit of a hack to get around an issue with eui portals and\r\nthe z-index of the timeline, as the tags super select that is displayed\r\nwhen the exceptions flyout is opened when not specifically for a rule\r\ninstance, renders below the flyout due to z-index of 5000. This change\r\nmakes it so that the flyout has a z-index of 1000 in that case, and 5000\r\nin the timeline view, so that all elements are visible as expected.\r\n\r\n\r\nhttps://user-images.githubusercontent.com/56408403/205704409-9379e5af-2f01-45f0-b5d9-8479ac892b65.mov","sha":"83a334974c9d15ab3b45a5130979dcf5f6212382"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147024","number":147024,"mergeCommit":{"message":"[Security Solution] [Exceptions] Only use z-index 5000 when exceptions within timeline (#147024)\n\n## Summary\r\nThis pr is a bit of a hack to get around an issue with eui portals and\r\nthe z-index of the timeline, as the tags super select that is displayed\r\nwhen the exceptions flyout is opened when not specifically for a rule\r\ninstance, renders below the flyout due to z-index of 5000. This change\r\nmakes it so that the flyout has a z-index of 1000 in that case, and 5000\r\nin the timeline view, so that all elements are visible as expected.\r\n\r\n\r\nhttps://user-images.githubusercontent.com/56408403/205704409-9379e5af-2f01-45f0-b5d9-8479ac892b65.mov","sha":"83a334974c9d15ab3b45a5130979dcf5f6212382"}}]}] BACKPORT--> Co-authored-by: Kevin Qualters <56408403+kqualters-elastic@users.noreply.github.com> |
||
|
1c3951956d
|
[8.6] [Fleet] Ensure top-level package vars are parsed when reading archive (#147040) (#147051)
# Backport This will backport the following commits from `main` to `8.6`: - [[Fleet] Ensure top-level package vars are parsed when reading archive (#147040)](https://github.com/elastic/kibana/pull/147040) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Kyle Pollich","email":"kyle.pollich@elastic.co"},"sourceCommit":{"committedDate":"2022-12-05T20:13:19Z","message":"[Fleet] Ensure top-level package vars are parsed when reading archive (#147040)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/147028\r\n\r\n## Testing instructions\r\n\r\nSee steps to reproduce in linked issue. Verify AWS credential variables\r\nappear on this branch.\r\n\r\n\r\n\r\n\r\nI took a pass at adding tests for our `parseAndVeryArchive` method but\r\nit's sort of a recursive chain of mocked `Buffer` -> `yaml.safeLoad`\r\noperations and got pretty involved to set up from scratch. The other\r\noption would be to add an FTR API test that catches this case, but we'd\r\nneed a package with top-level variables loaded into the test registry,\r\nwhich we may not have readily available if\r\nhttps://github.com/elastic/kibana/pull/146809 lands.\r\n\r\nI would love some alternative ideas on adding test coverage for this\r\nfix, but if it's going to involved I don't want to block this fix from\r\nlanding in 8.6 on tests.","sha":"b6696ef6c7da83c0ef396d24f471cb6589e5413a","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","backport:prev-minor","v8.7.0"],"number":147040,"url":"https://github.com/elastic/kibana/pull/147040","mergeCommit":{"message":"[Fleet] Ensure top-level package vars are parsed when reading archive (#147040)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/147028\r\n\r\n## Testing instructions\r\n\r\nSee steps to reproduce in linked issue. Verify AWS credential variables\r\nappear on this branch.\r\n\r\n\r\n\r\n\r\nI took a pass at adding tests for our `parseAndVeryArchive` method but\r\nit's sort of a recursive chain of mocked `Buffer` -> `yaml.safeLoad`\r\noperations and got pretty involved to set up from scratch. The other\r\noption would be to add an FTR API test that catches this case, but we'd\r\nneed a package with top-level variables loaded into the test registry,\r\nwhich we may not have readily available if\r\nhttps://github.com/elastic/kibana/pull/146809 lands.\r\n\r\nI would love some alternative ideas on adding test coverage for this\r\nfix, but if it's going to involved I don't want to block this fix from\r\nlanding in 8.6 on tests.","sha":"b6696ef6c7da83c0ef396d24f471cb6589e5413a"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147040","number":147040,"mergeCommit":{"message":"[Fleet] Ensure top-level package vars are parsed when reading archive (#147040)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/147028\r\n\r\n## Testing instructions\r\n\r\nSee steps to reproduce in linked issue. Verify AWS credential variables\r\nappear on this branch.\r\n\r\n\r\n\r\n\r\nI took a pass at adding tests for our `parseAndVeryArchive` method but\r\nit's sort of a recursive chain of mocked `Buffer` -> `yaml.safeLoad`\r\noperations and got pretty involved to set up from scratch. The other\r\noption would be to add an FTR API test that catches this case, but we'd\r\nneed a package with top-level variables loaded into the test registry,\r\nwhich we may not have readily available if\r\nhttps://github.com/elastic/kibana/pull/146809 lands.\r\n\r\nI would love some alternative ideas on adding test coverage for this\r\nfix, but if it's going to involved I don't want to block this fix from\r\nlanding in 8.6 on tests.","sha":"b6696ef6c7da83c0ef396d24f471cb6589e5413a"}}]}] BACKPORT--> Co-authored-by: Kyle Pollich <kyle.pollich@elastic.co> |
||
|
9b8e563574
|
[8.6] Remove id from item list (#146805) (#147033)
# Backport This will backport the following commits from `main` to `8.6`: - [Remove id from item list (#146805)](https://github.com/elastic/kibana/pull/146805) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Khristinin Nikita","email":"nikita.khristinin@elastic.co"},"sourceCommit":{"committedDate":"2022-12-05T18:01:02Z","message":"Remove id from item list (#146805)\n\n## Remove id from item list when try to close alerts during update\r\nexceptions\r\nclose: https://github.com/elastic/kibana/issues/146661\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"7261175571b0bcfd68c538067c60eac12dad84e1","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","backport:prev-minor","v8.7.0"],"number":146805,"url":"https://github.com/elastic/kibana/pull/146805","mergeCommit":{"message":"Remove id from item list (#146805)\n\n## Remove id from item list when try to close alerts during update\r\nexceptions\r\nclose: https://github.com/elastic/kibana/issues/146661\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"7261175571b0bcfd68c538067c60eac12dad84e1"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/146805","number":146805,"mergeCommit":{"message":"Remove id from item list (#146805)\n\n## Remove id from item list when try to close alerts during update\r\nexceptions\r\nclose: https://github.com/elastic/kibana/issues/146661\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"7261175571b0bcfd68c538067c60eac12dad84e1"}}]}] BACKPORT--> Co-authored-by: Khristinin Nikita <nikita.khristinin@elastic.co> |
||
|
a91d495b66
|
[8.6] [Security Solution] Change Actions Log Management text to Response Actions History (#146918) (#147022)
# Backport This will backport the following commits from `main` to `8.6`: - [[Security Solution] Change Actions Log Management text to Response Actions History (#146918)](https://github.com/elastic/kibana/pull/146918) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Kevin Logan","email":"56395104+kevinlog@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-12-05T16:46:15Z","message":"[Security Solution] Change Actions Log Management text to Response Actions History (#146918)\n\n## Summary\r\n\r\nUpdate the \"Actions Log Management\" text to be \"Response Actions\r\nHistory\"\r\n\r\n<img width=\"1728\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/56395104/205371149-b4dd8443-edef-4464-8257-90e8a5ff87a0.png\">\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\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\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"b5ba42bf1af74bea87619d7ebaa1d48cab88b7d3","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Onboarding and Lifecycle Mgt","auto-backport","v8.6.0","v8.7.0"],"number":146918,"url":"https://github.com/elastic/kibana/pull/146918","mergeCommit":{"message":"[Security Solution] Change Actions Log Management text to Response Actions History (#146918)\n\n## Summary\r\n\r\nUpdate the \"Actions Log Management\" text to be \"Response Actions\r\nHistory\"\r\n\r\n<img width=\"1728\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/56395104/205371149-b4dd8443-edef-4464-8257-90e8a5ff87a0.png\">\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\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\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"b5ba42bf1af74bea87619d7ebaa1d48cab88b7d3"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/146918","number":146918,"mergeCommit":{"message":"[Security Solution] Change Actions Log Management text to Response Actions History (#146918)\n\n## Summary\r\n\r\nUpdate the \"Actions Log Management\" text to be \"Response Actions\r\nHistory\"\r\n\r\n<img width=\"1728\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/56395104/205371149-b4dd8443-edef-4464-8257-90e8a5ff87a0.png\">\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\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\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"b5ba42bf1af74bea87619d7ebaa1d48cab88b7d3"}}]}] BACKPORT--> Co-authored-by: Kevin Logan <56395104+kevinlog@users.noreply.github.com> |
||
|
de3b26d832
|
[8.6] [TIP] Fix broken refresh button on the indicators page (#146526) (#147011)
# Backport This will backport the following commits from `main` to `8.6`: - [[TIP] Fix broken refresh button on the indicators page (#146526)](https://github.com/elastic/kibana/pull/146526) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Luke Gmys","email":"lgmys@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-12-05T15:12:53Z","message":"[TIP] Fix broken refresh button on the indicators page (#146526)\n\n## Summary\r\n\r\nThis PR fixes the broken refresh button noticed during the 8.6 demo.\r\n\r\nIncludes an e2e test to verify if it is working or not.\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\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\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"e89ba22953eba604fb61fe1d95ec5cbc7d22a6b8","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","backport:prev-minor","Team: Protections Experience","v8.7.0"],"number":146526,"url":"https://github.com/elastic/kibana/pull/146526","mergeCommit":{"message":"[TIP] Fix broken refresh button on the indicators page (#146526)\n\n## Summary\r\n\r\nThis PR fixes the broken refresh button noticed during the 8.6 demo.\r\n\r\nIncludes an e2e test to verify if it is working or not.\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\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\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"e89ba22953eba604fb61fe1d95ec5cbc7d22a6b8"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/146526","number":146526,"mergeCommit":{"message":"[TIP] Fix broken refresh button on the indicators page (#146526)\n\n## Summary\r\n\r\nThis PR fixes the broken refresh button noticed during the 8.6 demo.\r\n\r\nIncludes an e2e test to verify if it is working or not.\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\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\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"e89ba22953eba604fb61fe1d95ec5cbc7d22a6b8"}}]}] BACKPORT--> Co-authored-by: Luke Gmys <lgmys@users.noreply.github.com> |
||
|
f3c36f206b
|
[8.6] Fix user authentication area chart (#146783) (#147005)
# Backport This will backport the following commits from `main` to `8.6`: - [Fix user authentication area chart (#146783)](https://github.com/elastic/kibana/pull/146783) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Angela Chuang","email":"6295984+angorayc@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-12-05T14:47:57Z","message":"Fix user authentication area chart (#146783)\n\n## Summary\r\n\r\nOriginal issue: https://github.com/elastic/kibana/issues/131791\r\n\r\nBefore: No area chart displayed for user authentications:\r\n\r\n<img width=\"1505\" alt=\"Screenshot 2022-12-01 at 13 02 17\"\r\nsrc=\"https://user-images.githubusercontent.com/6295984/205059727-2be51425-9b61-4595-8ad6-9a80b4a4bea5.png\">\r\n\r\n\r\n<img width=\"1101\" alt=\"Screenshot 2022-12-01 at 12 55 42\"\r\nsrc=\"https://user-images.githubusercontent.com/6295984/205058753-1f97cca1-b3b8-4b58-ae8a-9e5ada107e9f.png\">\r\n\r\nMost of the data of area charts look like:\r\n\r\n```\r\n[\r\n {\r\n \"key_as_string\": \"2022-12-01T00:00:00.000Z\",\r\n \"key\": 1669852800000, // x\r\n \"doc_count\": 12,\r\n \"count\": {\r\n \"value\": 0 // y\r\n }\r\n }\r\n]\r\n```\r\n\r\nbut user authentications' data looks like:\r\n```\r\n[\r\n {\r\n \"key_as_string\": \"2022-12-01T00:00:00.000Z\",\r\n \"key\": 1669852800000, // x\r\n \"doc_count\": 12,\r\n \"count\": {\r\n \"doc_count\": 0 // y\r\n }\r\n }\r\n]\r\n```\r\nThe parser (formatGeneralHistogramData) picked up only count.value and\r\nignored count.doc_count. Therefore y value for user authentication was\r\nnot picked up and no data for rendering the area chart.\r\n\r\n\r\nAfter: User authentication area chart should be displayed properly.\r\n<img width=\"1505\" alt=\"Screenshot 2022-12-01 at 13 07 21\"\r\nsrc=\"https://user-images.githubusercontent.com/6295984/205060657-a9fbfa42-5ae5-449d-84d5-6df3f97d2464.png\">\r\n\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\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":"4f7685484d7e7f33b8e124b93b271e06961848e8","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:Threat Hunting","fixed","Team: SecuritySolution","Team:Threat Hunting:Explore","v8.6.0","v8.7.0"],"number":146783,"url":"https://github.com/elastic/kibana/pull/146783","mergeCommit":{"message":"Fix user authentication area chart (#146783)\n\n## Summary\r\n\r\nOriginal issue: https://github.com/elastic/kibana/issues/131791\r\n\r\nBefore: No area chart displayed for user authentications:\r\n\r\n<img width=\"1505\" alt=\"Screenshot 2022-12-01 at 13 02 17\"\r\nsrc=\"https://user-images.githubusercontent.com/6295984/205059727-2be51425-9b61-4595-8ad6-9a80b4a4bea5.png\">\r\n\r\n\r\n<img width=\"1101\" alt=\"Screenshot 2022-12-01 at 12 55 42\"\r\nsrc=\"https://user-images.githubusercontent.com/6295984/205058753-1f97cca1-b3b8-4b58-ae8a-9e5ada107e9f.png\">\r\n\r\nMost of the data of area charts look like:\r\n\r\n```\r\n[\r\n {\r\n \"key_as_string\": \"2022-12-01T00:00:00.000Z\",\r\n \"key\": 1669852800000, // x\r\n \"doc_count\": 12,\r\n \"count\": {\r\n \"value\": 0 // y\r\n }\r\n }\r\n]\r\n```\r\n\r\nbut user authentications' data looks like:\r\n```\r\n[\r\n {\r\n \"key_as_string\": \"2022-12-01T00:00:00.000Z\",\r\n \"key\": 1669852800000, // x\r\n \"doc_count\": 12,\r\n \"count\": {\r\n \"doc_count\": 0 // y\r\n }\r\n }\r\n]\r\n```\r\nThe parser (formatGeneralHistogramData) picked up only count.value and\r\nignored count.doc_count. Therefore y value for user authentication was\r\nnot picked up and no data for rendering the area chart.\r\n\r\n\r\nAfter: User authentication area chart should be displayed properly.\r\n<img width=\"1505\" alt=\"Screenshot 2022-12-01 at 13 07 21\"\r\nsrc=\"https://user-images.githubusercontent.com/6295984/205060657-a9fbfa42-5ae5-449d-84d5-6df3f97d2464.png\">\r\n\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\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":"4f7685484d7e7f33b8e124b93b271e06961848e8"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/146783","number":146783,"mergeCommit":{"message":"Fix user authentication area chart (#146783)\n\n## Summary\r\n\r\nOriginal issue: https://github.com/elastic/kibana/issues/131791\r\n\r\nBefore: No area chart displayed for user authentications:\r\n\r\n<img width=\"1505\" alt=\"Screenshot 2022-12-01 at 13 02 17\"\r\nsrc=\"https://user-images.githubusercontent.com/6295984/205059727-2be51425-9b61-4595-8ad6-9a80b4a4bea5.png\">\r\n\r\n\r\n<img width=\"1101\" alt=\"Screenshot 2022-12-01 at 12 55 42\"\r\nsrc=\"https://user-images.githubusercontent.com/6295984/205058753-1f97cca1-b3b8-4b58-ae8a-9e5ada107e9f.png\">\r\n\r\nMost of the data of area charts look like:\r\n\r\n```\r\n[\r\n {\r\n \"key_as_string\": \"2022-12-01T00:00:00.000Z\",\r\n \"key\": 1669852800000, // x\r\n \"doc_count\": 12,\r\n \"count\": {\r\n \"value\": 0 // y\r\n }\r\n }\r\n]\r\n```\r\n\r\nbut user authentications' data looks like:\r\n```\r\n[\r\n {\r\n \"key_as_string\": \"2022-12-01T00:00:00.000Z\",\r\n \"key\": 1669852800000, // x\r\n \"doc_count\": 12,\r\n \"count\": {\r\n \"doc_count\": 0 // y\r\n }\r\n }\r\n]\r\n```\r\nThe parser (formatGeneralHistogramData) picked up only count.value and\r\nignored count.doc_count. Therefore y value for user authentication was\r\nnot picked up and no data for rendering the area chart.\r\n\r\n\r\nAfter: User authentication area chart should be displayed properly.\r\n<img width=\"1505\" alt=\"Screenshot 2022-12-01 at 13 07 21\"\r\nsrc=\"https://user-images.githubusercontent.com/6295984/205060657-a9fbfa42-5ae5-449d-84d5-6df3f97d2464.png\">\r\n\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\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":"4f7685484d7e7f33b8e124b93b271e06961848e8"}}]}] BACKPORT--> Co-authored-by: Angela Chuang <6295984+angorayc@users.noreply.github.com> |
||
|
fbcb7951bd
|
[8.6] [Security Solution] [Exceptions] Hook for exceptions to fetch the security solution default data view was missing the space id (#146915) (#146994)
# Backport This will backport the following commits from `main` to `8.6`: - [[Security Solution] [Exceptions] Hook for exceptions to fetch the security solution default data view was missing the space id (#146915)](https://github.com/elastic/kibana/pull/146915) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Devin W. Hurley","email":"devin.hurley@elastic.co"},"sourceCommit":{"committedDate":"2022-12-05T13:16:15Z","message":"[Security Solution] [Exceptions] Hook for exceptions to fetch the security solution default data view was missing the space id (#146915)\n\n## Summary\r\n\r\nappend space id to security solution default data view in\r\n`useFetchIndexPatterns` hook in rule exceptions\r\n\r\nCo-authored-by: Gloria Hornero <gloria.hornero@elastic.co>","sha":"ed9e9627706d9b894f429a5b8084f5afa9f5f271","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","review","release_note:skip","impact:critical","Feature:Rule Exceptions","Team:Security Solution Platform","v8.6.0","v8.7.0"],"number":146915,"url":"https://github.com/elastic/kibana/pull/146915","mergeCommit":{"message":"[Security Solution] [Exceptions] Hook for exceptions to fetch the security solution default data view was missing the space id (#146915)\n\n## Summary\r\n\r\nappend space id to security solution default data view in\r\n`useFetchIndexPatterns` hook in rule exceptions\r\n\r\nCo-authored-by: Gloria Hornero <gloria.hornero@elastic.co>","sha":"ed9e9627706d9b894f429a5b8084f5afa9f5f271"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/146915","number":146915,"mergeCommit":{"message":"[Security Solution] [Exceptions] Hook for exceptions to fetch the security solution default data view was missing the space id (#146915)\n\n## Summary\r\n\r\nappend space id to security solution default data view in\r\n`useFetchIndexPatterns` hook in rule exceptions\r\n\r\nCo-authored-by: Gloria Hornero <gloria.hornero@elastic.co>","sha":"ed9e9627706d9b894f429a5b8084f5afa9f5f271"}}]}] BACKPORT--> Co-authored-by: Devin W. Hurley <devin.hurley@elastic.co> |
||
|
22d65ee969
|
[8.6] [profiling] Ensure constant colors in profiling bar chart (#146696) (#146776)
# Backport This will backport the following commits from `main` to `8.6`: - [[profiling] Ensure constant colors in profiling bar chart (#146696)](https://github.com/elastic/kibana/pull/146696) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Thomas Dullien","email":"thomas.dullien@googlemail.com"},"sourceCommit":{"committedDate":"2022-12-01T11:11:49Z","message":"[profiling] Ensure constant colors in profiling bar chart (#146696)\n\n## Summary\r\n\r\nMake sure that identical objects in the bar chart always get assigned\r\nthe same colors.\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Tim Rühsen <tim.ruhsen@elastic.co>","sha":"0a065f3c1d18b881209f510c574c7f463c401ffc","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v8.7.0","v8.6.1"],"number":146696,"url":"https://github.com/elastic/kibana/pull/146696","mergeCommit":{"message":"[profiling] Ensure constant colors in profiling bar chart (#146696)\n\n## Summary\r\n\r\nMake sure that identical objects in the bar chart always get assigned\r\nthe same colors.\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Tim Rühsen <tim.ruhsen@elastic.co>","sha":"0a065f3c1d18b881209f510c574c7f463c401ffc"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/146696","number":146696,"mergeCommit":{"message":"[profiling] Ensure constant colors in profiling bar chart (#146696)\n\n## Summary\r\n\r\nMake sure that identical objects in the bar chart always get assigned\r\nthe same colors.\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Tim Rühsen <tim.ruhsen@elastic.co>","sha":"0a065f3c1d18b881209f510c574c7f463c401ffc"}},{"branch":"8.6","label":"v8.6.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Thomas Dullien <thomas.dullien@googlemail.com> Co-authored-by: Tim Rühsen <tim.ruhsen@elastic.co> |
||
|
aae164cfe8
|
[8.6] [Osquery] [Fix] Fix redundant policy revision update after osquery integration is added (#146959) (#146977)
# Backport This will backport the following commits from `main` to `8.6`: - [[Osquery] [Fix] Fix redundant policy revision update after osquery integration is added (#146959)](https://github.com/elastic/kibana/pull/146959) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Tomasz Ciecierski","email":"tomasz.ciecierski@elastic.co"},"sourceCommit":{"committedDate":"2022-12-05T10:04:16Z","message":"[Osquery] [Fix] Fix redundant policy revision update after osquery integration is added (#146959)","sha":"18ee50264221d453ece7755344992e54b564cb18","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:Asset Management","Feature:Osquery","v8.6.0","v8.7.0"],"number":146959,"url":"https://github.com/elastic/kibana/pull/146959","mergeCommit":{"message":"[Osquery] [Fix] Fix redundant policy revision update after osquery integration is added (#146959)","sha":"18ee50264221d453ece7755344992e54b564cb18"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/146959","number":146959,"mergeCommit":{"message":"[Osquery] [Fix] Fix redundant policy revision update after osquery integration is added (#146959)","sha":"18ee50264221d453ece7755344992e54b564cb18"}}]}] BACKPORT--> Co-authored-by: Tomasz Ciecierski <tomasz.ciecierski@elastic.co> |
||
|
9c6ef32ec1
|
[8.6] [RAM] clear scheduleTaskId when cloning rule #146717 (#146929)
# Backport This will backport the following commits from `main` to `8.6`: - [[Synthetics] adjust quick filers (#146717)](https://github.com/elastic/kibana/pull/146717) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Dominique Clarke","email":"dominique.clarke@elastic.co"},"sourceCommit":{"committedDate":"2022-12-02T21:14:23Z","message":"[Synthetics] adjust quick filers (#146886)\n\n## Summary\r\n\r\nResolves https://github.com/elastic/kibana/issues/146824\r\n\r\nAdjusts logic for querying down monitors to rely on `config_id` (the\r\nsaved object id) rather than `id` (the monitor query id).\r\n\r\n### Testing\r\n1. Create at least 1 project monitor and 1 UI monitor that are\r\nconsistently down\r\n2. Navigate to Synthetics Overview page\r\n3. Click the down filter\r\n4. Ensure both monitors appear","sha":"a4a89cf8ab3c4e4123bb7691f46ba28738165e3a","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","Team:uptime","release_note:skip","v8.6.0","v8.7.0"],"number":146886,"url":"https://github.com/elastic/kibana/pull/146886","mergeCommit":{"message":"[Synthetics] adjust quick filers (#146886)\n\n## Summary\r\n\r\nResolves https://github.com/elastic/kibana/issues/146824\r\n\r\nAdjusts logic for querying down monitors to rely on `config_id` (the\r\nsaved object id) rather than `id` (the monitor query id).\r\n\r\n### Testing\r\n1. Create at least 1 project monitor and 1 UI monitor that are\r\nconsistently down\r\n2. Navigate to Synthetics Overview page\r\n3. Click the down filter\r\n4. Ensure both monitors appear","sha":"a4a89cf8ab3c4e4123bb7691f46ba28738165e3a"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/146886","number":146886,"mergeCommit":{"message":"[Synthetics] adjust quick filers (#146886)\n\n## Summary\r\n\r\nResolves https://github.com/elastic/kibana/issues/146824\r\n\r\nAdjusts logic for querying down monitors to rely on `config_id` (the\r\nsaved object id) rather than `id` (the monitor query id).\r\n\r\n### Testing\r\n1. Create at least 1 project monitor and 1 UI monitor that are\r\nconsistently down\r\n2. Navigate to Synthetics Overview page\r\n3. Click the down filter\r\n4. Ensure both monitors appear","sha":"a4a89cf8ab3c4e4123bb7691f46ba28738165e3a"}}]}] BACKPORT--> |
||
|
3372c87ea3
|
[8.6] fix Exception lists are shared between different spaces (#146889) (#146923)
# Backport This will backport the following commits from `main` to `8.6`: - [fix Exception lists are shared between different spaces (#146889)](https://github.com/elastic/kibana/pull/146889) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Wafaa Nasr","email":"wafaa.nasr@elastic.co"},"sourceCommit":{"committedDate":"2022-12-02T20:59:53Z","message":"fix Exception lists are shared between different spaces (#146889)\n\n## Summary\r\n\r\n- Addresses https://github.com/elastic/kibana/issues/146461 \r\n- Fix transition state when `Add to shared list is loading`","sha":"f677b3b135b9f2a93fb6d73ee24f2779edb92f39","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Security Solution Platform","backport:prev-minor","ci:cloud-deploy","v8.7.0"],"number":146889,"url":"https://github.com/elastic/kibana/pull/146889","mergeCommit":{"message":"fix Exception lists are shared between different spaces (#146889)\n\n## Summary\r\n\r\n- Addresses https://github.com/elastic/kibana/issues/146461 \r\n- Fix transition state when `Add to shared list is loading`","sha":"f677b3b135b9f2a93fb6d73ee24f2779edb92f39"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/146889","number":146889,"mergeCommit":{"message":"fix Exception lists are shared between different spaces (#146889)\n\n## Summary\r\n\r\n- Addresses https://github.com/elastic/kibana/issues/146461 \r\n- Fix transition state when `Add to shared list is loading`","sha":"f677b3b135b9f2a93fb6d73ee24f2779edb92f39"}}]}] BACKPORT--> Co-authored-by: Wafaa Nasr <wafaa.nasr@elastic.co> |
||
|
e10d203951
|
[8.6] [Synthetics] adjust quick filers (#146886) (#146925)
# Backport This will backport the following commits from `main` to `8.6`: - [[Synthetics] adjust quick filers (#146886)](https://github.com/elastic/kibana/pull/146886) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Dominique Clarke","email":"dominique.clarke@elastic.co"},"sourceCommit":{"committedDate":"2022-12-02T21:14:23Z","message":"[Synthetics] adjust quick filers (#146886)\n\n## Summary\r\n\r\nResolves https://github.com/elastic/kibana/issues/146824\r\n\r\nAdjusts logic for querying down monitors to rely on `config_id` (the\r\nsaved object id) rather than `id` (the monitor query id).\r\n\r\n### Testing\r\n1. Create at least 1 project monitor and 1 UI monitor that are\r\nconsistently down\r\n2. Navigate to Synthetics Overview page\r\n3. Click the down filter\r\n4. Ensure both monitors appear","sha":"a4a89cf8ab3c4e4123bb7691f46ba28738165e3a","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","Team:uptime","release_note:skip","v8.6.0","v8.7.0"],"number":146886,"url":"https://github.com/elastic/kibana/pull/146886","mergeCommit":{"message":"[Synthetics] adjust quick filers (#146886)\n\n## Summary\r\n\r\nResolves https://github.com/elastic/kibana/issues/146824\r\n\r\nAdjusts logic for querying down monitors to rely on `config_id` (the\r\nsaved object id) rather than `id` (the monitor query id).\r\n\r\n### Testing\r\n1. Create at least 1 project monitor and 1 UI monitor that are\r\nconsistently down\r\n2. Navigate to Synthetics Overview page\r\n3. Click the down filter\r\n4. Ensure both monitors appear","sha":"a4a89cf8ab3c4e4123bb7691f46ba28738165e3a"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/146886","number":146886,"mergeCommit":{"message":"[Synthetics] adjust quick filers (#146886)\n\n## Summary\r\n\r\nResolves https://github.com/elastic/kibana/issues/146824\r\n\r\nAdjusts logic for querying down monitors to rely on `config_id` (the\r\nsaved object id) rather than `id` (the monitor query id).\r\n\r\n### Testing\r\n1. Create at least 1 project monitor and 1 UI monitor that are\r\nconsistently down\r\n2. Navigate to Synthetics Overview page\r\n3. Click the down filter\r\n4. Ensure both monitors appear","sha":"a4a89cf8ab3c4e4123bb7691f46ba28738165e3a"}}]}] BACKPORT--> Co-authored-by: Dominique Clarke <dominique.clarke@elastic.co> |
||
|
a3b8bc3bad
|
[8.6] [Security Solution] Failed to Fetch Rules and Timeline in Preview Flyout (#146904) (#146921)
# Backport This will backport the following commits from `main` to `8.6`: - [[Security Solution] Failed to Fetch Rules and Timeline in Preview Flyout (#146904)](https://github.com/elastic/kibana/pull/146904) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Ievgen Sorokopud","email":"ievgen.sorokopud@elastic.co"},"sourceCommit":{"committedDate":"2022-12-02T20:17:54Z","message":"[Security Solution] Failed to Fetch Rules and Timeline in Preview Flyout (#146904)\n\n## Summary\r\n\r\nThese changes fixes the issue with the unexpected \"Failed to Fetch Rule\"\r\nerror toast that appears when user opens the alert details from the Rule\r\nPreview page.\r\n\r\nThe issue was introduced by [recent\r\nrefactoring](https://github.com/elastic/kibana/pull/142950) where we\r\nswitched from the optional toast to showing error toast always when it\r\nis not possible to fetch the rule (see `useRuleWithFallback` hook). In\r\ncase of Rule Preview the rule does not exist and thus server returns 404\r\n(not found) error. In case of Rule Preview we would like to ignore this\r\nerror and build the rule from the alert.\r\n\r\nBug Ticket: #146858","sha":"1b4c66101b02dd4c01582a0e7b684eb5b499101a","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team: SecuritySolution","Team:Detection Rules","Team:Detection Alerts","backport:prev-minor","ci:cloud-deploy","v8.7.0"],"number":146904,"url":"https://github.com/elastic/kibana/pull/146904","mergeCommit":{"message":"[Security Solution] Failed to Fetch Rules and Timeline in Preview Flyout (#146904)\n\n## Summary\r\n\r\nThese changes fixes the issue with the unexpected \"Failed to Fetch Rule\"\r\nerror toast that appears when user opens the alert details from the Rule\r\nPreview page.\r\n\r\nThe issue was introduced by [recent\r\nrefactoring](https://github.com/elastic/kibana/pull/142950) where we\r\nswitched from the optional toast to showing error toast always when it\r\nis not possible to fetch the rule (see `useRuleWithFallback` hook). In\r\ncase of Rule Preview the rule does not exist and thus server returns 404\r\n(not found) error. In case of Rule Preview we would like to ignore this\r\nerror and build the rule from the alert.\r\n\r\nBug Ticket: #146858","sha":"1b4c66101b02dd4c01582a0e7b684eb5b499101a"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/146904","number":146904,"mergeCommit":{"message":"[Security Solution] Failed to Fetch Rules and Timeline in Preview Flyout (#146904)\n\n## Summary\r\n\r\nThese changes fixes the issue with the unexpected \"Failed to Fetch Rule\"\r\nerror toast that appears when user opens the alert details from the Rule\r\nPreview page.\r\n\r\nThe issue was introduced by [recent\r\nrefactoring](https://github.com/elastic/kibana/pull/142950) where we\r\nswitched from the optional toast to showing error toast always when it\r\nis not possible to fetch the rule (see `useRuleWithFallback` hook). In\r\ncase of Rule Preview the rule does not exist and thus server returns 404\r\n(not found) error. In case of Rule Preview we would like to ignore this\r\nerror and build the rule from the alert.\r\n\r\nBug Ticket: #146858","sha":"1b4c66101b02dd4c01582a0e7b684eb5b499101a"}}]}] BACKPORT--> Co-authored-by: Ievgen Sorokopud <ievgen.sorokopud@elastic.co> |
||
|
399d39e60e
|
[8.6] [Lens] fix lucene object query bug (#146846) (#146914)
# Backport This will backport the following commits from `main` to `8.6`: - [[Lens] fix lucene object query bug (#146846)](https://github.com/elastic/kibana/pull/146846) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Andrew Tate","email":"andrew.tate@elastic.co"},"sourceCommit":{"committedDate":"2022-12-02T19:05:53Z","message":"[Lens] fix lucene object query bug (#146846)\n\n## Summary\r\n\r\nfix https://github.com/elastic/kibana/issues/146819","sha":"3c351fffc184d23eafd98a0c61d6c3e28840a59d","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Visualizations","Feature:Lens","backport:prev-minor","v8.7.0"],"number":146846,"url":"https://github.com/elastic/kibana/pull/146846","mergeCommit":{"message":"[Lens] fix lucene object query bug (#146846)\n\n## Summary\r\n\r\nfix https://github.com/elastic/kibana/issues/146819","sha":"3c351fffc184d23eafd98a0c61d6c3e28840a59d"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/146846","number":146846,"mergeCommit":{"message":"[Lens] fix lucene object query bug (#146846)\n\n## Summary\r\n\r\nfix https://github.com/elastic/kibana/issues/146819","sha":"3c351fffc184d23eafd98a0c61d6c3e28840a59d"}}]}] BACKPORT--> Co-authored-by: Andrew Tate <andrew.tate@elastic.co> |
||
|
502fed4c91
|
[8.6] [Security Solution][Exception]: Add to shared lists fixes (#146750) (#146887)
# Backport This will backport the following commits from `main` to `8.6`: - [[Security Solution][Exception]: Add to shared lists fixes (#146750)](https://github.com/elastic/kibana/pull/146750) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Wafaa Nasr","email":"wafaa.nasr@elastic.co"},"sourceCommit":{"committedDate":"2022-12-02T14:02:33Z","message":"[Security Solution][Exception]: Add to shared lists fixes (#146750)\n\n## Summary\r\n\r\n- Continuing from [PR](https://github.com/elastic/kibana/pull/146121) to\r\napply the same changes to the `Add to Shared Lists`.\r\n- Fix showing the number of Linked rules correctly => in `route.ts` use\r\nthe `list.namespaceType` instead of namespaceTypes array\r\n- Apply docs comment on the text\r\n- Use the HeaderMenu item from the `kbn` package for the `Number of\r\nLinked rules` menu\r\n- Allow displaying the HeaderMenu without iconType\r\n- Update snapshots and add tests in HeaderMenu","sha":"78b4851a214e5018c8ea6535477ca9374ffb377f","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","auto-backport","Team:Security Solution Platform","ci:cloud-deploy","v8.6.0"],"number":146750,"url":"https://github.com/elastic/kibana/pull/146750","mergeCommit":{"message":"[Security Solution][Exception]: Add to shared lists fixes (#146750)\n\n## Summary\r\n\r\n- Continuing from [PR](https://github.com/elastic/kibana/pull/146121) to\r\napply the same changes to the `Add to Shared Lists`.\r\n- Fix showing the number of Linked rules correctly => in `route.ts` use\r\nthe `list.namespaceType` instead of namespaceTypes array\r\n- Apply docs comment on the text\r\n- Use the HeaderMenu item from the `kbn` package for the `Number of\r\nLinked rules` menu\r\n- Allow displaying the HeaderMenu without iconType\r\n- Update snapshots and add tests in HeaderMenu","sha":"78b4851a214e5018c8ea6535477ca9374ffb377f"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Wafaa Nasr <wafaa.nasr@elastic.co> |
||
|
c695be7bd8
|
[8.6] [Enterprise Search] Update sync dates when canceling (#146879) (#146891)
# Backport This will backport the following commits from `main` to `8.6`: - [[Enterprise Search] Update sync dates when canceling (#146879)](https://github.com/elastic/kibana/pull/146879) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Sander Philipse","email":"94373878+sphilipse@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-12-02T14:46:49Z","message":"[Enterprise Search] Update sync dates when canceling (#146879)\n\nThis updates relevant date fields when canceling a synchronization job.","sha":"de8f368ca231e11ca6a71b7b1afd0798e225245f","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:EnterpriseSearch","v8.6.0","v8.7.0"],"number":146879,"url":"https://github.com/elastic/kibana/pull/146879","mergeCommit":{"message":"[Enterprise Search] Update sync dates when canceling (#146879)\n\nThis updates relevant date fields when canceling a synchronization job.","sha":"de8f368ca231e11ca6a71b7b1afd0798e225245f"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/146879","number":146879,"mergeCommit":{"message":"[Enterprise Search] Update sync dates when canceling (#146879)\n\nThis updates relevant date fields when canceling a synchronization job.","sha":"de8f368ca231e11ca6a71b7b1afd0798e225245f"}}]}] BACKPORT--> Co-authored-by: Sander Philipse <94373878+sphilipse@users.noreply.github.com> |
||
|
8a58292881
|
[8.6] [Enterprise Search] Show only connector error on config page (#146880) (#146890)
# Backport This will backport the following commits from `main` to `8.6`: - [[Enterprise Search] Show only connector error on config page (#146880)](https://github.com/elastic/kibana/pull/146880) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Sander Philipse","email":"94373878+sphilipse@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-12-02T14:46:26Z","message":"[Enterprise Search] Show only connector error on config page (#146880)\n\nThis removes synchronization errors from the connector configuration\r\nscreen, showing only connector errors.","sha":"215c567baa146da28aac3923083060dc8ef53275","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:EnterpriseSearch","v8.6.0","v8.7.0"],"number":146880,"url":"https://github.com/elastic/kibana/pull/146880","mergeCommit":{"message":"[Enterprise Search] Show only connector error on config page (#146880)\n\nThis removes synchronization errors from the connector configuration\r\nscreen, showing only connector errors.","sha":"215c567baa146da28aac3923083060dc8ef53275"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/146880","number":146880,"mergeCommit":{"message":"[Enterprise Search] Show only connector error on config page (#146880)\n\nThis removes synchronization errors from the connector configuration\r\nscreen, showing only connector errors.","sha":"215c567baa146da28aac3923083060dc8ef53275"}}]}] BACKPORT--> Co-authored-by: Sander Philipse <94373878+sphilipse@users.noreply.github.com> |
||
|
e8f51486f9
|
[8.6] [Security Solution] Suppress alerts by default message refactor (#146520) (#146878)
# Backport This will backport the following commits from `main` to `8.6`: - [[Security Solution] `Suppress alerts by` default message refactor (#146520)](https://github.com/elastic/kibana/pull/146520) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Gloria Hornero","email":"gloria.hornero@elastic.co"},"sourceCommit":{"committedDate":"2022-12-02T12:16:35Z","message":"[Security Solution] `Suppress alerts by` default message refactor (#146520)\n\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"79ebd290be0226efdedb91b00923245caaa4c4a8","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Detections and Resp","v8.6.0","v8.7.0"],"number":146520,"url":"https://github.com/elastic/kibana/pull/146520","mergeCommit":{"message":"[Security Solution] `Suppress alerts by` default message refactor (#146520)\n\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"79ebd290be0226efdedb91b00923245caaa4c4a8"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/146520","number":146520,"mergeCommit":{"message":"[Security Solution] `Suppress alerts by` default message refactor (#146520)\n\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"79ebd290be0226efdedb91b00923245caaa4c4a8"}}]}] BACKPORT--> Co-authored-by: Gloria Hornero <gloria.hornero@elastic.co> |
||
|
e4a9eb90fd
|
[8.6] [Synthetics] Fixes project monitor edit code path (#146416) (#146853)
# Backport This will backport the following commits from `main` to `8.6`: - [[Synthetics] Fixes project monitor edit code path (#146416)](https://github.com/elastic/kibana/pull/146416) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Shahzad","email":"shahzad.muhammad@elastic.co"},"sourceCommit":{"committedDate":"2022-12-02T08:56:29Z","message":"[Synthetics] Fixes project monitor edit code path (#146416)\n\n## Summary\n\nFixed project monitor editor code path, it was called un-necessarily on\neach request.","sha":"dc2b29add974e8ab086979f11f7ff7fa8967a495","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:uptime","release_note:skip","v8.6.0","v8.7.0"],"number":146416,"url":"https://github.com/elastic/kibana/pull/146416","mergeCommit":{"message":"[Synthetics] Fixes project monitor edit code path (#146416)\n\n## Summary\n\nFixed project monitor editor code path, it was called un-necessarily on\neach request.","sha":"dc2b29add974e8ab086979f11f7ff7fa8967a495"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/146416","number":146416,"mergeCommit":{"message":"[Synthetics] Fixes project monitor edit code path (#146416)\n\n## Summary\n\nFixed project monitor editor code path, it was called un-necessarily on\neach request.","sha":"dc2b29add974e8ab086979f11f7ff7fa8967a495"}}]}] BACKPORT--> Co-authored-by: Shahzad <shahzad.muhammad@elastic.co> |
||
|
258c9ef31b
|
[8.6] [Osquery] [Fix] Response action pack's queries update (#146782) (#146825)
# Backport This will backport the following commits from `main` to `8.6`: - [[Osquery] [Fix] Response action pack's queries update (#146782)](https://github.com/elastic/kibana/pull/146782) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Tomasz Ciecierski","email":"tomasz.ciecierski@elastic.co"},"sourceCommit":{"committedDate":"2022-12-01T20:30:20Z","message":"[Osquery] [Fix] Response action pack's queries update (#146782)","sha":"ec7ba49dcaf5fb7232553c8f739a489174d4ea16","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","Team:Asset Management","Feature:Osquery","v8.6.0","v8.7.0"],"number":146782,"url":"https://github.com/elastic/kibana/pull/146782","mergeCommit":{"message":"[Osquery] [Fix] Response action pack's queries update (#146782)","sha":"ec7ba49dcaf5fb7232553c8f739a489174d4ea16"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/146782","number":146782,"mergeCommit":{"message":"[Osquery] [Fix] Response action pack's queries update (#146782)","sha":"ec7ba49dcaf5fb7232553c8f739a489174d4ea16"}}]}] BACKPORT--> Co-authored-by: Tomasz Ciecierski <tomasz.ciecierski@elastic.co> |
||
|
acede4b442
|
[8.6] Quick-fix Users can’t upgrade their clusters when riskScore experimental feature is enabled (#146780) (#146813)
# Backport This will backport the following commits from `main` to `8.6`: - [Quick-fix Users can’t upgrade their clusters when `riskScore` experimental feature is enabled (#146780)](https://github.com/elastic/kibana/pull/146780) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Pablo Machado","email":"pablo.nevesmachado@elastic.co"},"sourceCommit":{"committedDate":"2022-12-01T17:25:46Z","message":"Quick-fix Users can’t upgrade their clusters when `riskScore` experimental feature is enabled (#146780)\n\nUsers can't upgrade their clusters when an old experimental feature is\r\nenabled.\r\n\r\nWhile we don't have a final solution for this issue, I am adding the\r\nexperimental flag configuration back to prevent users from having this\r\nfrustrating experience.\r\n\r\nQuick-fix for: https://github.com/elastic/kibana/issues/146777\r\nOriginal report:\r\nhttps://elastic.slack.com/archives/C6E3MTCD7/p1669236299374339\r\n\r\nFix\r\n```\r\nFATAL Error: [config validation of [xpack.securitySolution].enableExperimental]: [riskyUsersEnabled] is not allowed. Allowed values are: tGridEnabled, tGridEventRenderedViewEnabled, excludePoliciesInFilterEnabled, kubernetesEnabled, disableIsolationUIPendingStatuses, pendingActionResponsesWithAck, policyListEnabled, policyResponseInFleetEnabled, previewTelemetryUrlEnabled, responseActionsConsoleEnabled, insightsRelatedAlertsByProcessAncestry, extendedRuleExecutionLoggingEnabled, socTrendsEnabled, responseActionsEnabled\r\n```\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"c3d1d9ec284f81f3c5d713010e52cd9d4f09c39e","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","Team:Threat Hunting","Team: SecuritySolution","Team:Threat Hunting:Explore","v8.6.0","v8.7.0","v8.6.1"],"number":146780,"url":"https://github.com/elastic/kibana/pull/146780","mergeCommit":{"message":"Quick-fix Users can’t upgrade their clusters when `riskScore` experimental feature is enabled (#146780)\n\nUsers can't upgrade their clusters when an old experimental feature is\r\nenabled.\r\n\r\nWhile we don't have a final solution for this issue, I am adding the\r\nexperimental flag configuration back to prevent users from having this\r\nfrustrating experience.\r\n\r\nQuick-fix for: https://github.com/elastic/kibana/issues/146777\r\nOriginal report:\r\nhttps://elastic.slack.com/archives/C6E3MTCD7/p1669236299374339\r\n\r\nFix\r\n```\r\nFATAL Error: [config validation of [xpack.securitySolution].enableExperimental]: [riskyUsersEnabled] is not allowed. Allowed values are: tGridEnabled, tGridEventRenderedViewEnabled, excludePoliciesInFilterEnabled, kubernetesEnabled, disableIsolationUIPendingStatuses, pendingActionResponsesWithAck, policyListEnabled, policyResponseInFleetEnabled, previewTelemetryUrlEnabled, responseActionsConsoleEnabled, insightsRelatedAlertsByProcessAncestry, extendedRuleExecutionLoggingEnabled, socTrendsEnabled, responseActionsEnabled\r\n```\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"c3d1d9ec284f81f3c5d713010e52cd9d4f09c39e"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/146780","number":146780,"mergeCommit":{"message":"Quick-fix Users can’t upgrade their clusters when `riskScore` experimental feature is enabled (#146780)\n\nUsers can't upgrade their clusters when an old experimental feature is\r\nenabled.\r\n\r\nWhile we don't have a final solution for this issue, I am adding the\r\nexperimental flag configuration back to prevent users from having this\r\nfrustrating experience.\r\n\r\nQuick-fix for: https://github.com/elastic/kibana/issues/146777\r\nOriginal report:\r\nhttps://elastic.slack.com/archives/C6E3MTCD7/p1669236299374339\r\n\r\nFix\r\n```\r\nFATAL Error: [config validation of [xpack.securitySolution].enableExperimental]: [riskyUsersEnabled] is not allowed. Allowed values are: tGridEnabled, tGridEventRenderedViewEnabled, excludePoliciesInFilterEnabled, kubernetesEnabled, disableIsolationUIPendingStatuses, pendingActionResponsesWithAck, policyListEnabled, policyResponseInFleetEnabled, previewTelemetryUrlEnabled, responseActionsConsoleEnabled, insightsRelatedAlertsByProcessAncestry, extendedRuleExecutionLoggingEnabled, socTrendsEnabled, responseActionsEnabled\r\n```\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"c3d1d9ec284f81f3c5d713010e52cd9d4f09c39e"}}]}] BACKPORT--> Co-authored-by: Pablo Machado <pablo.nevesmachado@elastic.co> |
||
|
bcfb02af8b
|
[8.6] [Synthetics] Fixes monitors search by location/hosts (#146529) (#146800)
# Backport This will backport the following commits from `main` to `8.6`: - [[Synthetics] Fixes monitors search by location/hosts (#146529)](https://github.com/elastic/kibana/pull/146529) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Shahzad","email":"shahzad.muhammad@elastic.co"},"sourceCommit":{"committedDate":"2022-12-01T15:26:53Z","message":"[Synthetics] Fixes monitors search by location/hosts (#146529)\n\nFixes https://github.com/elastic/kibana/issues/146077\r\nFixes https://github.com/elastic/kibana/issues/146078","sha":"6f7c6ad947ce860231a4737b35ee6efdb8d4bc84","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:uptime","release_note:skip","v8.6.0","v8.7.0"],"number":146529,"url":"https://github.com/elastic/kibana/pull/146529","mergeCommit":{"message":"[Synthetics] Fixes monitors search by location/hosts (#146529)\n\nFixes https://github.com/elastic/kibana/issues/146077\r\nFixes https://github.com/elastic/kibana/issues/146078","sha":"6f7c6ad947ce860231a4737b35ee6efdb8d4bc84"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/146529","number":146529,"mergeCommit":{"message":"[Synthetics] Fixes monitors search by location/hosts (#146529)\n\nFixes https://github.com/elastic/kibana/issues/146077\r\nFixes https://github.com/elastic/kibana/issues/146078","sha":"6f7c6ad947ce860231a4737b35ee6efdb8d4bc84"}}]}] BACKPORT--> Co-authored-by: Shahzad <shahzad.muhammad@elastic.co> |
||
|
2d72a47604
|
[8.6] Make page titles more consistent for Overview, Alerts, Rules, Rule Detail and Cases pages (#146150) (#146807)
# Backport This will backport the following commits from `main` to `8.6`: - [Make page titles more consistent for Overview, Alerts, Rules, Rule Detail and Cases pages (#146150)](https://github.com/elastic/kibana/pull/146150) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Coen Warmer","email":"coen.warmer@gmail.com"},"sourceCommit":{"committedDate":"2022-11-24T12:11:28Z","message":"Make page titles more consistent for Overview, Alerts, Rules, Rule Detail and Cases pages (#146150)\n\nCloses https://github.com/elastic/kibana/issues/142859.\r\n\r\n## Summary\r\n\r\nThis PR updates the Observability Overview, Alerts, Rules, Rule Details\r\nand Cases pages so their headers are more consistent with one another.\r\n\r\n**Previously:**\r\n\r\n\r\nhttps://user-images.githubusercontent.com/535564/203364454-35002377-d23a-4327-91b0-d1f473869f6a.mov\r\n\r\n**With this PR:**\r\n\r\n\r\nhttps://user-images.githubusercontent.com/535564/203364851-9afd2950-0fba-4f6b-ad52-0b81da77451a.mov","sha":"b3c022dc05fbe9f941627f526ba301cb1c29eefd","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v8.6.0","v8.7.0"],"number":146150,"url":"https://github.com/elastic/kibana/pull/146150","mergeCommit":{"message":"Make page titles more consistent for Overview, Alerts, Rules, Rule Detail and Cases pages (#146150)\n\nCloses https://github.com/elastic/kibana/issues/142859.\r\n\r\n## Summary\r\n\r\nThis PR updates the Observability Overview, Alerts, Rules, Rule Details\r\nand Cases pages so their headers are more consistent with one another.\r\n\r\n**Previously:**\r\n\r\n\r\nhttps://user-images.githubusercontent.com/535564/203364454-35002377-d23a-4327-91b0-d1f473869f6a.mov\r\n\r\n**With this PR:**\r\n\r\n\r\nhttps://user-images.githubusercontent.com/535564/203364851-9afd2950-0fba-4f6b-ad52-0b81da77451a.mov","sha":"b3c022dc05fbe9f941627f526ba301cb1c29eefd"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/146150","number":146150,"mergeCommit":{"message":"Make page titles more consistent for Overview, Alerts, Rules, Rule Detail and Cases pages (#146150)\n\nCloses https://github.com/elastic/kibana/issues/142859.\r\n\r\n## Summary\r\n\r\nThis PR updates the Observability Overview, Alerts, Rules, Rule Details\r\nand Cases pages so their headers are more consistent with one another.\r\n\r\n**Previously:**\r\n\r\n\r\nhttps://user-images.githubusercontent.com/535564/203364454-35002377-d23a-4327-91b0-d1f473869f6a.mov\r\n\r\n**With this PR:**\r\n\r\n\r\nhttps://user-images.githubusercontent.com/535564/203364851-9afd2950-0fba-4f6b-ad52-0b81da77451a.mov","sha":"b3c022dc05fbe9f941627f526ba301cb1c29eefd"}}]}] BACKPORT--> Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com> |
||
|
fa936350f5
|
[8.6] [Fleet] Fix agent status computation to support agent v2 uppercase (#146757) (#146789)
# Backport This will backport the following commits from `main` to `8.6`: - [[Fleet] Fix agent status computation to support agent v2 uppercase (#146757)](https://github.com/elastic/kibana/pull/146757) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Nicolas Chaulet","email":"nicolas.chaulet@elastic.co"},"sourceCommit":{"committedDate":"2022-12-01T14:12:53Z","message":"[Fleet] Fix agent status computation to support agent v2 uppercase (#146757)","sha":"11451129d2b3c14e989a4071d188937af98a614d","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","v8.6.0","v8.7.0"],"number":146757,"url":"https://github.com/elastic/kibana/pull/146757","mergeCommit":{"message":"[Fleet] Fix agent status computation to support agent v2 uppercase (#146757)","sha":"11451129d2b3c14e989a4071d188937af98a614d"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/146757","number":146757,"mergeCommit":{"message":"[Fleet] Fix agent status computation to support agent v2 uppercase (#146757)","sha":"11451129d2b3c14e989a4071d188937af98a614d"}}]}] BACKPORT--> Co-authored-by: Nicolas Chaulet <nicolas.chaulet@elastic.co> |
||
|
0cbcf24414
|
[8.6] [i18n] Fix ja-JP locale causing FATAL error when starting kibana (#146704) (#146742)
# Backport This will backport the following commits from `main` to `8.6`: - [[i18n] Fix ja-JP locale causing FATAL error when starting kibana (#146704)](https://github.com/elastic/kibana/pull/146704) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Ahmad Bamieh","email":"ahmad.bamyeh@elastic.co"},"sourceCommit":{"committedDate":"2022-11-30T18:28:28Z","message":"[i18n] Fix ja-JP locale causing FATAL error when starting kibana (#146704)\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCloses https://github.com/elastic/kibana/issues/146693","sha":"1323fd8de68e0da9e56a6fd26b12b3c031cb74fd","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","v8.6.0","v8.7.0","v8.5.3"],"number":146704,"url":"https://github.com/elastic/kibana/pull/146704","mergeCommit":{"message":"[i18n] Fix ja-JP locale causing FATAL error when starting kibana (#146704)\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCloses https://github.com/elastic/kibana/issues/146693","sha":"1323fd8de68e0da9e56a6fd26b12b3c031cb74fd"}},"sourceBranch":"main","suggestedTargetBranches":["8.6","8.5"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/146704","number":146704,"mergeCommit":{"message":"[i18n] Fix ja-JP locale causing FATAL error when starting kibana (#146704)\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCloses https://github.com/elastic/kibana/issues/146693","sha":"1323fd8de68e0da9e56a6fd26b12b3c031cb74fd"}},{"branch":"8.5","label":"v8.5.3","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Ahmad Bamieh <ahmad.bamyeh@elastic.co> Co-authored-by: Ahmad Bamieh <ahmadbamieh@gmail.com> |
||
|
35cf7309fd
|
[8.6] [Security Solution][Alerts] Add suppression info to alert details insights (#145766) (#146749)
# Backport This will backport the following commits from `main` to `8.6`: - [[Security Solution][Alerts] Add suppression info to alert details insights (#145766)](https://github.com/elastic/kibana/pull/145766) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Marshall Main","email":"55718608+marshallmain@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-11-30T19:54:11Z","message":"[Security Solution][Alerts] Add suppression info to alert details insights (#145766)\n\n## Summary\r\n\r\nhttps://github.com/elastic/kibana/issues/145678 - Alert suppression info\r\ndoes not display in the details flyout (issue mentions highlighted\r\nfields, but we add it to `Insights` as shown in the\r\n[mocks]( |
||
|
7747da8246
|
[8.6] [Security Solution][Alerts] Don't use maxSignals for topHits agg size (#146564) (#146712)
# Backport This will backport the following commits from `main` to `8.6`: - [[Security Solution][Alerts] Don't use maxSignals for topHits agg size (#146564)](https://github.com/elastic/kibana/pull/146564) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Marshall Main","email":"55718608+marshallmain@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-11-30T15:50:16Z","message":"[Security Solution][Alerts] Don't use maxSignals for topHits agg size (#146564)\n\n## Summary\r\n\r\nAddresses https://github.com/elastic/kibana/issues/146494\r\n\r\nWe only need the first document from the bucket to create the alert, not\r\n`maxSignals` documents. If `maxSignals` was greater than 100, this\r\ncaused an error in the search.","sha":"d659ee6f2eb04e81b240db137996aa2a4c4378b1","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team: SecuritySolution","Team:Detection Alerts","v8.6.0","v8.7.0"],"number":146564,"url":"https://github.com/elastic/kibana/pull/146564","mergeCommit":{"message":"[Security Solution][Alerts] Don't use maxSignals for topHits agg size (#146564)\n\n## Summary\r\n\r\nAddresses https://github.com/elastic/kibana/issues/146494\r\n\r\nWe only need the first document from the bucket to create the alert, not\r\n`maxSignals` documents. If `maxSignals` was greater than 100, this\r\ncaused an error in the search.","sha":"d659ee6f2eb04e81b240db137996aa2a4c4378b1"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/146564","number":146564,"mergeCommit":{"message":"[Security Solution][Alerts] Don't use maxSignals for topHits agg size (#146564)\n\n## Summary\r\n\r\nAddresses https://github.com/elastic/kibana/issues/146494\r\n\r\nWe only need the first document from the bucket to create the alert, not\r\n`maxSignals` documents. If `maxSignals` was greater than 100, this\r\ncaused an error in the search.","sha":"d659ee6f2eb04e81b240db137996aa2a4c4378b1"}}]}] BACKPORT--> Co-authored-by: Marshall Main <55718608+marshallmain@users.noreply.github.com> |
||
|
582fed3615
|
[8.6] [Security Solution] Full Screen of Rule Preview breaking the UI under Rule Creation form (#146687) (#146736)
# Backport This will backport the following commits from `main` to `8.6`: - [[Security Solution] Full Screen of Rule Preview breaking the UI under Rule Creation form (#146687)](https://github.com/elastic/kibana/pull/146687) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Ievgen Sorokopud","email":"ievgen.sorokopud@elastic.co"},"sourceCommit":{"committedDate":"2022-11-30T17:57:30Z","message":"[Security Solution] Full Screen of Rule Preview breaking the UI under Rule Creation form (#146687)\n\n## Summary\r\n\r\nThese changes fix broken fullscreen table that displays the rule preview\r\nresults.\r\n\r\nFullscreen table before fix:\r\n\r\n<img width=\"1879\" alt=\"Screenshot 2022-11-30 at 14 46 00\"\r\nsrc=\"https://user-images.githubusercontent.com/2700761/204812399-52138490-a42a-4ea2-bd00-04680375580a.png\">\r\n\r\nFullscreen table after fix:\r\n\r\n<img width=\"1881\" alt=\"Screenshot 2022-11-30 at 14 45 20\"\r\nsrc=\"https://user-images.githubusercontent.com/2700761/204812419-5b528ae5-02e4-4808-adcc-14ede7cec56b.png\">\r\n\r\nTicket: #145954\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"d9b690f97a450fa29ea602e8181861045242c35f","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Alerts","backport:prev-minor","ci:cloud-deploy","v8.7.0"],"number":146687,"url":"https://github.com/elastic/kibana/pull/146687","mergeCommit":{"message":"[Security Solution] Full Screen of Rule Preview breaking the UI under Rule Creation form (#146687)\n\n## Summary\r\n\r\nThese changes fix broken fullscreen table that displays the rule preview\r\nresults.\r\n\r\nFullscreen table before fix:\r\n\r\n<img width=\"1879\" alt=\"Screenshot 2022-11-30 at 14 46 00\"\r\nsrc=\"https://user-images.githubusercontent.com/2700761/204812399-52138490-a42a-4ea2-bd00-04680375580a.png\">\r\n\r\nFullscreen table after fix:\r\n\r\n<img width=\"1881\" alt=\"Screenshot 2022-11-30 at 14 45 20\"\r\nsrc=\"https://user-images.githubusercontent.com/2700761/204812419-5b528ae5-02e4-4808-adcc-14ede7cec56b.png\">\r\n\r\nTicket: #145954\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"d9b690f97a450fa29ea602e8181861045242c35f"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/146687","number":146687,"mergeCommit":{"message":"[Security Solution] Full Screen of Rule Preview breaking the UI under Rule Creation form (#146687)\n\n## Summary\r\n\r\nThese changes fix broken fullscreen table that displays the rule preview\r\nresults.\r\n\r\nFullscreen table before fix:\r\n\r\n<img width=\"1879\" alt=\"Screenshot 2022-11-30 at 14 46 00\"\r\nsrc=\"https://user-images.githubusercontent.com/2700761/204812399-52138490-a42a-4ea2-bd00-04680375580a.png\">\r\n\r\nFullscreen table after fix:\r\n\r\n<img width=\"1881\" alt=\"Screenshot 2022-11-30 at 14 45 20\"\r\nsrc=\"https://user-images.githubusercontent.com/2700761/204812419-5b528ae5-02e4-4808-adcc-14ede7cec56b.png\">\r\n\r\nTicket: #145954\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"d9b690f97a450fa29ea602e8181861045242c35f"}}]}] BACKPORT--> Co-authored-by: Ievgen Sorokopud <ievgen.sorokopud@elastic.co> |
||
|
1e9de03293
|
[8.6] [Security Solution] [Exceptions] fixes affects shared lists route on rule details -> view exceptions (#146448) (#146735)
# Backport This will backport the following commits from `main` to `8.6`: - [[Security Solution] [Exceptions] fixes affects shared lists route on rule details -> view exceptions (#146448)](https://github.com/elastic/kibana/pull/146448) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Devin W. Hurley","email":"devin.hurley@elastic.co"},"sourceCommit":{"committedDate":"2022-11-30T17:55:52Z","message":"[Security Solution] [Exceptions] fixes affects shared lists route on rule details -> view exceptions (#146448)\n\n## Summary\r\n\r\nFixes: https://github.com/elastic/kibana/issues/144602\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"ebfc715105b9d1172cb778142cc62e37b4acf8f8","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["review","release_note:skip","Team:Security Solution Platform","backport:prev-minor","v8.6.0","v8.7.0"],"number":146448,"url":"https://github.com/elastic/kibana/pull/146448","mergeCommit":{"message":"[Security Solution] [Exceptions] fixes affects shared lists route on rule details -> view exceptions (#146448)\n\n## Summary\r\n\r\nFixes: https://github.com/elastic/kibana/issues/144602\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"ebfc715105b9d1172cb778142cc62e37b4acf8f8"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/146448","number":146448,"mergeCommit":{"message":"[Security Solution] [Exceptions] fixes affects shared lists route on rule details -> view exceptions (#146448)\n\n## Summary\r\n\r\nFixes: https://github.com/elastic/kibana/issues/144602\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"ebfc715105b9d1172cb778142cc62e37b4acf8f8"}}]}] BACKPORT--> Co-authored-by: Devin W. Hurley <devin.hurley@elastic.co> |
||
|
817c3c9ffd
|
[Detection Rules] Fix - Updating Pre-Packaged Rules to Mirror Main for 8.6 Release (#146730)
## Summary This PR copies all pre-packaged rules from main and mirrors them in 8.6. From the prior rule update to FS rules, backporting failed and had to be manually triggered to backport from main to 8.6. However, after further inspection, the rules were not mirrored correctly. * Rule updates for 8.6 to main: https://github.com/elastic/kibana/pull/146402 * Manual backport to 8.6: https://github.com/elastic/kibana/pull/146588 ### Checklist Delete any items that are not applicable to this PR. - [x] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md) |
||
|
89882ccca9
|
[8.6] Catching saved object not found error, do not delete referenced package assets (#146274) (#146411)
# Backport This will backport the following commits from `main` to `8.6`: - [Catching saved object not found error, do not delete referenced package assets (#146274)](https://github.com/elastic/kibana/pull/146274) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Julia Bardi","email":"90178898+juliaElastic@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-11-28T15:07:20Z","message":"Catching saved object not found error, do not delete referenced package assets (#146274)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/142112\r\n\r\nImprovements coming out of SDHs, to handle Fleet errors more robustly.\r\n\r\n### 1. Catching package assets not found error and logging a warning, to\r\nprevent it blocking setup/install.\r\n### 2. In assets cleanup logic, doing a check that the assets are not\r\nreferenced by packages before deleting them.\r\n\r\nVerifying 1. and 2. hard, because I don't have a way to reproduce the\r\nassets not found error. Tried to install/delete different versions of a\r\npackage, but didn't run into the issues.\r\n\r\n### 3. Force removing a package deletes package policies as well\r\n\r\nTo verify:\r\n- add at least one integration (e.g. system package)\r\n- force delete integration with API\r\n```\r\nDELETE http://elastic:changeme@localhost:5601/julia/api/fleet/epm/packages/system/1.20.4\r\nkbn-xsrf: kibana\r\n\r\n{ \"force\": true }\r\n```\r\n- verify that package policies are deleted as well\r\n- there is an info log added:\r\n```\r\n[2022-11-24T14:10:29.138+01:00][INFO ][plugins.fleet] deleting package policies of system package because force flag was enabled: 84a4e5d4-e363-4045-9240-9ab151f2b376,6d34a544-7467-48fd-a779-c2d30d808aa6\r\n```\r\n\r\n### 4. Catching saved object not found error when tagging package assets\r\nTo verify:\r\n- follow the steps above to force delete a package\r\n- add system integration again \r\n- verify that it succeeds, and there is a warning log\r\n```\r\n[2022-11-24T14:07:47.960+01:00][WARN ][plugins.fleet] Error: Saved object [dashboard/system-01c54730-fee6-11e9-8405-516218e3d268] not found\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\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"7198faf5ee61faf26c41c4549b48d83a7eff0069","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","v8.7.0","v8.6.1"],"number":146274,"url":"https://github.com/elastic/kibana/pull/146274","mergeCommit":{"message":"Catching saved object not found error, do not delete referenced package assets (#146274)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/142112\r\n\r\nImprovements coming out of SDHs, to handle Fleet errors more robustly.\r\n\r\n### 1. Catching package assets not found error and logging a warning, to\r\nprevent it blocking setup/install.\r\n### 2. In assets cleanup logic, doing a check that the assets are not\r\nreferenced by packages before deleting them.\r\n\r\nVerifying 1. and 2. hard, because I don't have a way to reproduce the\r\nassets not found error. Tried to install/delete different versions of a\r\npackage, but didn't run into the issues.\r\n\r\n### 3. Force removing a package deletes package policies as well\r\n\r\nTo verify:\r\n- add at least one integration (e.g. system package)\r\n- force delete integration with API\r\n```\r\nDELETE http://elastic:changeme@localhost:5601/julia/api/fleet/epm/packages/system/1.20.4\r\nkbn-xsrf: kibana\r\n\r\n{ \"force\": true }\r\n```\r\n- verify that package policies are deleted as well\r\n- there is an info log added:\r\n```\r\n[2022-11-24T14:10:29.138+01:00][INFO ][plugins.fleet] deleting package policies of system package because force flag was enabled: 84a4e5d4-e363-4045-9240-9ab151f2b376,6d34a544-7467-48fd-a779-c2d30d808aa6\r\n```\r\n\r\n### 4. Catching saved object not found error when tagging package assets\r\nTo verify:\r\n- follow the steps above to force delete a package\r\n- add system integration again \r\n- verify that it succeeds, and there is a warning log\r\n```\r\n[2022-11-24T14:07:47.960+01:00][WARN ][plugins.fleet] Error: Saved object [dashboard/system-01c54730-fee6-11e9-8405-516218e3d268] not found\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\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"7198faf5ee61faf26c41c4549b48d83a7eff0069"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/146274","number":146274,"mergeCommit":{"message":"Catching saved object not found error, do not delete referenced package assets (#146274)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/142112\r\n\r\nImprovements coming out of SDHs, to handle Fleet errors more robustly.\r\n\r\n### 1. Catching package assets not found error and logging a warning, to\r\nprevent it blocking setup/install.\r\n### 2. In assets cleanup logic, doing a check that the assets are not\r\nreferenced by packages before deleting them.\r\n\r\nVerifying 1. and 2. hard, because I don't have a way to reproduce the\r\nassets not found error. Tried to install/delete different versions of a\r\npackage, but didn't run into the issues.\r\n\r\n### 3. Force removing a package deletes package policies as well\r\n\r\nTo verify:\r\n- add at least one integration (e.g. system package)\r\n- force delete integration with API\r\n```\r\nDELETE http://elastic:changeme@localhost:5601/julia/api/fleet/epm/packages/system/1.20.4\r\nkbn-xsrf: kibana\r\n\r\n{ \"force\": true }\r\n```\r\n- verify that package policies are deleted as well\r\n- there is an info log added:\r\n```\r\n[2022-11-24T14:10:29.138+01:00][INFO ][plugins.fleet] deleting package policies of system package because force flag was enabled: 84a4e5d4-e363-4045-9240-9ab151f2b376,6d34a544-7467-48fd-a779-c2d30d808aa6\r\n```\r\n\r\n### 4. Catching saved object not found error when tagging package assets\r\nTo verify:\r\n- follow the steps above to force delete a package\r\n- add system integration again \r\n- verify that it succeeds, and there is a warning log\r\n```\r\n[2022-11-24T14:07:47.960+01:00][WARN ][plugins.fleet] Error: Saved object [dashboard/system-01c54730-fee6-11e9-8405-516218e3d268] not found\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\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"7198faf5ee61faf26c41c4549b48d83a7eff0069"}},{"branch":"8.6","label":"v8.6.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com> |
||
|
262f09cf9b
|
[8.6] [Security Solution] Refactors All exception lists - read only tests to remove flakiness (#146677) (#146708)
# Backport This will backport the following commits from `main` to `8.6`: - [[Security Solution] Refactors `All exception lists - read only` tests to remove flakiness (#146677)](https://github.com/elastic/kibana/pull/146677) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Gloria Hornero","email":"gloria.hornero@elastic.co"},"sourceCommit":{"committedDate":"2022-11-30T15:41:44Z","message":"[Security Solution] Refactors `All exception lists - read only` tests to remove flakiness (#146677)\n\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"8a6cc0cd26425afa67a448ffadc4de15f82d208d","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Detections and Resp","Team:Security Solution Platform","v8.6.0","v8.7.0"],"number":146677,"url":"https://github.com/elastic/kibana/pull/146677","mergeCommit":{"message":"[Security Solution] Refactors `All exception lists - read only` tests to remove flakiness (#146677)\n\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"8a6cc0cd26425afa67a448ffadc4de15f82d208d"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/146677","number":146677,"mergeCommit":{"message":"[Security Solution] Refactors `All exception lists - read only` tests to remove flakiness (#146677)\n\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"8a6cc0cd26425afa67a448ffadc4de15f82d208d"}}]}] BACKPORT--> Co-authored-by: Gloria Hornero <gloria.hornero@elastic.co> |