27426 commits

Author	SHA1	Message	Date
Kibana Machine	441904d391	[8.11] [EDR Workflows] Fix failing attach to case functionality when isolating/releasing a host (#172912) (#172967) ... # Backport This will backport the following commits from `main` to `8.11`: - [[EDR Workflows] Fix failing attach to case functionality when isolating/releasing a host (#172912)](https://github.com/elastic/kibana/pull/172912) <!--- 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":"2023-12-08T15:54:48Z","message":"[EDR Workflows] Fix failing attach to case functionality when isolating/releasing a host (#172912)","sha":"a5528e3e7ded7ca3388cf552c60de4c30e521781","branchLabelMapping":{"^v8.13.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","Team:Defend Workflows","v8.12.0","v8.13.0","v8.11.3"],"number":172912,"url":"https://github.com/elastic/kibana/pull/172912","mergeCommit":{"message":"[EDR Workflows] Fix failing attach to case functionality when isolating/releasing a host (#172912)","sha":"a5528e3e7ded7ca3388cf552c60de4c30e521781"}},"sourceBranch":"main","suggestedTargetBranches":["8.12","8.11"],"targetPullRequestStates":[{"branch":"8.12","label":"v8.12.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.13.0","labelRegex":"^v8.13.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/172912","number":172912,"mergeCommit":{"message":"[EDR Workflows] Fix failing attach to case functionality when isolating/releasing a host (#172912)","sha":"a5528e3e7ded7ca3388cf552c60de4c30e521781"}},{"branch":"8.11","label":"v8.11.3","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Tomasz Ciecierski <tomasz.ciecierski@elastic.co>	2023-12-08 10:35:23 -07:00
Kibana Machine	5940f41d16	[8.11] [Fleet] Fix 500 in Fleet API when request to product versions endpoint throws ECONNREFUSED (#172850) (#172864) ... # Backport This will backport the following commits from `main` to `8.11`: - [[Fleet] Fix 500 in Fleet API when request to product versions endpoint throws ECONNREFUSED (#172850)](https://github.com/elastic/kibana/pull/172850) <!--- 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":"2023-12-07T18:14:35Z","message":"[Fleet] Fix 500 in Fleet API when request to product versions endpoint throws ECONNREFUSED (#172850)\n\n## Summary\r\n\r\nNetwork-level errors will cause `fetch` to `throw` rather than resolving\r\nwith a status code. This PR updates our logic to handle this case for\r\nairgapped environments where `ECONNREFUSED` style errors squash HTTP\r\nrequests at the DNS level.","sha":"be6fbc4dcc8fff7e7419cf3fa9b05a6b13e3edba","branchLabelMapping":{"^v8.13.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Fleet","backport:prev-minor","v8.12.0","v8.13.0","v8.11.3"],"number":172850,"url":"https://github.com/elastic/kibana/pull/172850","mergeCommit":{"message":"[Fleet] Fix 500 in Fleet API when request to product versions endpoint throws ECONNREFUSED (#172850)\n\n## Summary\r\n\r\nNetwork-level errors will cause `fetch` to `throw` rather than resolving\r\nwith a status code. This PR updates our logic to handle this case for\r\nairgapped environments where `ECONNREFUSED` style errors squash HTTP\r\nrequests at the DNS level.","sha":"be6fbc4dcc8fff7e7419cf3fa9b05a6b13e3edba"}},"sourceBranch":"main","suggestedTargetBranches":["8.12","8.11"],"targetPullRequestStates":[{"branch":"8.12","label":"v8.12.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.13.0","labelRegex":"^v8.13.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/172850","number":172850,"mergeCommit":{"message":"[Fleet] Fix 500 in Fleet API when request to product versions endpoint throws ECONNREFUSED (#172850)\n\n## Summary\r\n\r\nNetwork-level errors will cause `fetch` to `throw` rather than resolving\r\nwith a status code. This PR updates our logic to handle this case for\r\nairgapped environments where `ECONNREFUSED` style errors squash HTTP\r\nrequests at the DNS level.","sha":"be6fbc4dcc8fff7e7419cf3fa9b05a6b13e3edba"}},{"branch":"8.11","label":"v8.11.3","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Kyle Pollich <kyle.pollich@elastic.co>	2023-12-07 12:41:29 -07:00
Quynh Nguyen (Quinn)	bea397e64a	[8.11] [ML] Fix Data visualizer/ML field stats and Data Frame Analytics should exclude _tier field (#172223) (#172585) ... # Backport This will backport the following commits from `main` to `8.11`: - [[ML] Fix Data visualizer/ML field stats and Data Frame Analytics should exclude _tier field (#172223)](https://github.com/elastic/kibana/pull/172223) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Quynh Nguyen (Quinn)","email":"43350163+qn895@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-12-04T16:46:31Z","message":"[ML] Fix Data visualizer/ML field stats and Data Frame Analytics should exclude _tier field (#172223)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/171243. This PR adds\r\nfield `_tier` to the list of omit fields to not show or display. This is\r\nespecially relevant when `_tier` is added in the list of meta fields in\r\nKibana.\r\n\r\nSteps to reproduce:\r\n1. In Advanced settings, add `_tier` to the list of meta fields. This\r\nwill show _tier as a field across Kibana if data has a tier applied.\r\n<img width=\"976\" alt=\"image\"\r\nsrc=\"86ecbbba-c574-42f6-97cf-c465ec334d7e\">\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [ ] 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\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\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- [ ] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n- [ ] Any UI touched in this PR does not create any new axe failures\r\n(run axe in browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n- [ ] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n- [ ] This renders correctly on smaller devices using a responsive\r\nlayout. (You can test this [in your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n- [ ] This was checked for [cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n\r\n### Risk Matrix\r\n\r\nDelete this section if it is not applicable to this PR.\r\n\r\nBefore closing this PR, invite QA, stakeholders, and other developers to\r\nidentify risks that should be tested prior to the change/feature\r\nrelease.\r\n\r\nWhen forming the risk matrix, consider some of the following examples\r\nand how they may potentially impact the change:\r\n\r\n| Risk | Probability | Severity | Mitigation/Notes |\r\n\r\n|---------------------------|-------------|----------|-------------------------|\r\n| Multiple Spaces&mdash;unexpected behavior in non-default Kibana Space.\r\n| Low | High | Integration tests will verify that all features are still\r\nsupported in non-default Kibana Space and when user switches between\r\nspaces. |\r\n| Multiple nodes&mdash;Elasticsearch polling might have race conditions\r\nwhen multiple Kibana nodes are polling for the same tasks. | High | Low\r\n| Tasks are idempotent, so executing them multiple times will not result\r\nin logical error, but will degrade performance. To test for this case we\r\nadd plenty of unit tests around this logic and document manual testing\r\nprocedure. |\r\n| Code should gracefully handle cases when feature X or plugin Y are\r\ndisabled. | Medium | High | Unit tests will verify that any feature flag\r\nor plugin combination still results in our service operational. |\r\n| [See more potential risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) |\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"2e39b64082895c8e779baa8b0bdd98e7dfce797c","branchLabelMapping":{"^v8.12.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix",":ml","v8.12.0","v8.11.2"],"number":172223,"url":"https://github.com/elastic/kibana/pull/172223","mergeCommit":{"message":"[ML] Fix Data visualizer/ML field stats and Data Frame Analytics should exclude _tier field (#172223)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/171243. This PR adds\r\nfield `_tier` to the list of omit fields to not show or display. This is\r\nespecially relevant when `_tier` is added in the list of meta fields in\r\nKibana.\r\n\r\nSteps to reproduce:\r\n1. In Advanced settings, add `_tier` to the list of meta fields. This\r\nwill show _tier as a field across Kibana if data has a tier applied.\r\n<img width=\"976\" alt=\"image\"\r\nsrc=\"86ecbbba-c574-42f6-97cf-c465ec334d7e\">\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [ ] 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\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\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- [ ] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n- [ ] Any UI touched in this PR does not create any new axe failures\r\n(run axe in browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n- [ ] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n- [ ] This renders correctly on smaller devices using a responsive\r\nlayout. (You can test this [in your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n- [ ] This was checked for [cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n\r\n### Risk Matrix\r\n\r\nDelete this section if it is not applicable to this PR.\r\n\r\nBefore closing this PR, invite QA, stakeholders, and other developers to\r\nidentify risks that should be tested prior to the change/feature\r\nrelease.\r\n\r\nWhen forming the risk matrix, consider some of the following examples\r\nand how they may potentially impact the change:\r\n\r\n| Risk | Probability | Severity | Mitigation/Notes |\r\n\r\n|---------------------------|-------------|----------|-------------------------|\r\n| Multiple Spaces&mdash;unexpected behavior in non-default Kibana Space.\r\n| Low | High | Integration tests will verify that all features are still\r\nsupported in non-default Kibana Space and when user switches between\r\nspaces. |\r\n| Multiple nodes&mdash;Elasticsearch polling might have race conditions\r\nwhen multiple Kibana nodes are polling for the same tasks. | High | Low\r\n| Tasks are idempotent, so executing them multiple times will not result\r\nin logical error, but will degrade performance. To test for this case we\r\nadd plenty of unit tests around this logic and document manual testing\r\nprocedure. |\r\n| Code should gracefully handle cases when feature X or plugin Y are\r\ndisabled. | Medium | High | Unit tests will verify that any feature flag\r\nor plugin combination still results in our service operational. |\r\n| [See more potential risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) |\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"2e39b64082895c8e779baa8b0bdd98e7dfce797c"}},"sourceBranch":"main","suggestedTargetBranches":["8.11"],"targetPullRequestStates":[{"branch":"main","label":"v8.12.0","labelRegex":"^v8.12.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/172223","number":172223,"mergeCommit":{"message":"[ML] Fix Data visualizer/ML field stats and Data Frame Analytics should exclude _tier field (#172223)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/171243. This PR adds\r\nfield `_tier` to the list of omit fields to not show or display. This is\r\nespecially relevant when `_tier` is added in the list of meta fields in\r\nKibana.\r\n\r\nSteps to reproduce:\r\n1. In Advanced settings, add `_tier` to the list of meta fields. This\r\nwill show _tier as a field across Kibana if data has a tier applied.\r\n<img width=\"976\" alt=\"image\"\r\nsrc=\"86ecbbba-c574-42f6-97cf-c465ec334d7e\">\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [ ] 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\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\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- [ ] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n- [ ] Any UI touched in this PR does not create any new axe failures\r\n(run axe in browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n- [ ] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n- [ ] This renders correctly on smaller devices using a responsive\r\nlayout. (You can test this [in your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n- [ ] This was checked for [cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n\r\n### Risk Matrix\r\n\r\nDelete this section if it is not applicable to this PR.\r\n\r\nBefore closing this PR, invite QA, stakeholders, and other developers to\r\nidentify risks that should be tested prior to the change/feature\r\nrelease.\r\n\r\nWhen forming the risk matrix, consider some of the following examples\r\nand how they may potentially impact the change:\r\n\r\n| Risk | Probability | Severity | Mitigation/Notes |\r\n\r\n|---------------------------|-------------|----------|-------------------------|\r\n| Multiple Spaces&mdash;unexpected behavior in non-default Kibana Space.\r\n| Low | High | Integration tests will verify that all features are still\r\nsupported in non-default Kibana Space and when user switches between\r\nspaces. |\r\n| Multiple nodes&mdash;Elasticsearch polling might have race conditions\r\nwhen multiple Kibana nodes are polling for the same tasks. | High | Low\r\n| Tasks are idempotent, so executing them multiple times will not result\r\nin logical error, but will degrade performance. To test for this case we\r\nadd plenty of unit tests around this logic and document manual testing\r\nprocedure. |\r\n| Code should gracefully handle cases when feature X or plugin Y are\r\ndisabled. | Medium | High | Unit tests will verify that any feature flag\r\nor plugin combination still results in our service operational. |\r\n| [See more potential risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) |\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"2e39b64082895c8e779baa8b0bdd98e7dfce797c"}},{"branch":"8.11","label":"v8.11.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>	2023-12-07 10:36:42 -06:00
Kyle Pollich	d77caccd10	[Fleet] Backport fixes for updating secrets to 8.11 (#172730) ... ## Summary Backports the following PR's to 8.11 - https://github.com/elastic/kibana/pull/172673 - https://github.com/elastic/kibana/pull/172695 cc @juliaElastic --------- Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com> Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>	2023-12-07 08:22:43 +01:00
Kibana Machine	05b98ad2d9	[8.11] [Fleet] Fix agent policy timeout to accept only integer (#172222) (#172619) ... # Backport This will backport the following commits from `main` to `8.11`: - [[Fleet] Fix agent policy timeout to accept only integer (#172222)](https://github.com/elastic/kibana/pull/172222) <!--- 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":"2023-12-05T19:01:04Z","message":"[Fleet] Fix agent policy timeout to accept only integer (#172222)","sha":"3ff891003c3ec9fe801c03015a972b2095e003c8","branchLabelMapping":{"^v8.12.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","Team:Fleet","backport:prev-minor","v8.12.0"],"number":172222,"url":"https://github.com/elastic/kibana/pull/172222","mergeCommit":{"message":"[Fleet] Fix agent policy timeout to accept only integer (#172222)","sha":"3ff891003c3ec9fe801c03015a972b2095e003c8"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.12.0","labelRegex":"^v8.12.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/172222","number":172222,"mergeCommit":{"message":"[Fleet] Fix agent policy timeout to accept only integer (#172222)","sha":"3ff891003c3ec9fe801c03015a972b2095e003c8"}}]}] BACKPORT--> Co-authored-by: Nicolas Chaulet <nicolas.chaulet@elastic.co>	2023-12-05 13:31:32 -07:00
Kibana Machine	727e19a019	[8.11] [ML] Fix data drift numeric fields not showing correctly (#172504) (#172591) ... # Backport This will backport the following commits from `main` to `8.11`: - [[ML] Fix data drift numeric fields not showing correctly (#172504)](https://github.com/elastic/kibana/pull/172504) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Quynh Nguyen (Quinn)","email":"43350163+qn895@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-12-05T15:35:06Z","message":"[ML] Fix data drift numeric fields not showing correctly (#172504)\n\n## Summary\r\n\r\nThis PR fixes an issue with data drift not showing numeric fields\r\ncorrectly for datasets that automatically uses random sampling.\r\n\r\n<img width=\"1720\" alt=\"image\"\r\nsrc=\"65e5efce-e428-40fc-8b53-c373c5771dd0\">","sha":"b692493c6f152308e44a99d5404fd9c166690729","branchLabelMapping":{"^v8.12.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix",":ml","v8.12.0","v8.11.2"],"number":172504,"url":"https://github.com/elastic/kibana/pull/172504","mergeCommit":{"message":"[ML] Fix data drift numeric fields not showing correctly (#172504)\n\n## Summary\r\n\r\nThis PR fixes an issue with data drift not showing numeric fields\r\ncorrectly for datasets that automatically uses random sampling.\r\n\r\n<img width=\"1720\" alt=\"image\"\r\nsrc=\"65e5efce-e428-40fc-8b53-c373c5771dd0\">","sha":"b692493c6f152308e44a99d5404fd9c166690729"}},"sourceBranch":"main","suggestedTargetBranches":["8.11"],"targetPullRequestStates":[{"branch":"main","label":"v8.12.0","labelRegex":"^v8.12.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/172504","number":172504,"mergeCommit":{"message":"[ML] Fix data drift numeric fields not showing correctly (#172504)\n\n## Summary\r\n\r\nThis PR fixes an issue with data drift not showing numeric fields\r\ncorrectly for datasets that automatically uses random sampling.\r\n\r\n<img width=\"1720\" alt=\"image\"\r\nsrc=\"65e5efce-e428-40fc-8b53-c373c5771dd0\">","sha":"b692493c6f152308e44a99d5404fd9c166690729"}},{"branch":"8.11","label":"v8.11.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Quynh Nguyen (Quinn) <43350163+qn895@users.noreply.github.com>	2023-12-05 10:03:34 -07:00
Kibana Machine	92746356b6	[8.11] [Connectors][ServiceNow ITOM] Edit required labels and automate screenshots (#172229) (#172516) ... # Backport This will backport the following commits from `main` to `8.11`: - [[Connectors][ServiceNow ITOM] Edit required labels and automate screenshots (#172229)](https://github.com/elastic/kibana/pull/172229) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Lisa Cawley","email":"lcawley@elastic.co"},"sourceCommit":{"committedDate":"2023-12-04T19:50:07Z","message":"[Connectors][ServiceNow ITOM] Edit required labels and automate screenshots (#172229)","sha":"e69063e08256b315175af9f749de762197537ca3","branchLabelMapping":{"^v8.12.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","docs","Feature:Actions/ConnectorTypes","backport:prev-minor","v8.12.0","v8.12.1"],"number":172229,"url":"https://github.com/elastic/kibana/pull/172229","mergeCommit":{"message":"[Connectors][ServiceNow ITOM] Edit required labels and automate screenshots (#172229)","sha":"e69063e08256b315175af9f749de762197537ca3"}},"sourceBranch":"main","suggestedTargetBranches":["8.12"],"targetPullRequestStates":[{"branch":"main","label":"v8.12.0","labelRegex":"^v8.12.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/172229","number":172229,"mergeCommit":{"message":"[Connectors][ServiceNow ITOM] Edit required labels and automate screenshots (#172229)","sha":"e69063e08256b315175af9f749de762197537ca3"}},{"branch":"8.12","label":"v8.12.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Lisa Cawley <lcawley@elastic.co>	2023-12-04 14:02:58 -07:00
Cristina Amico	1258c38a8e	[8.11] [Fleet] Replace dataviews suggestions in KQL searchboxes with internal ones (#172190) (#172437) ... # Backport This will backport the following commits from `main` to `8.11`: - [[Fleet] Replace dataviews suggestions in KQL searchboxes with internal ones (#172190)](https://github.com/elastic/kibana/pull/172190) <!--- Backport version: 8.9.8 --> ### 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":"2023-12-04T08:19:26Z","message":"[Fleet] Replace dataviews suggestions in KQL searchboxes with internal ones (#172190)\n\nFixes https://github.com/elastic/kibana/issues/169760\r\nRelated to https://github.com/elastic/kibana/issues/171425\r\n\r\n## Summary\r\n\r\n[Fleet] Replace dataviews suggestions in KQL searchboxes with internal\r\nones. Now using Fleet mappings to create the suggestions fields instead\r\nof fetching them through dataView plugin.\r\nThis is done for two reasons:\r\n\r\n- Solves [permission\r\nproblems](https://github.com/elastic/kibana/issues/169760) when the user\r\ndoesn't have privileges to read Fleet indices\r\n- Allows us to search only those mappings that we want to expose,\r\ninstead of all of them\r\n\r\nOnly weird thing is that the [querystring\r\ncomponent](1f8c816901/src/plugins/unified_search/public/query_string_input/query_string_input.tsx (L161))\r\nhas a cap to show max 50 suggestions. Since for agents suggestions we\r\nare showing some more fields, so the ones starting with `u` are not\r\nvisible anymore. I though I had a bug in the way I was creating the\r\n`fieldsMap` but in reality there's no way to show more suggestions than\r\n50 (without touching the original component, which I would gladly\r\navoid).\r\n\r\n\r\n### Screenshots\r\nThere should be no visible difference with the current suggestions. \r\n<details>\r\n <summary>Agents</summary>\r\n\r\n\r\n\r\n\r\n \r\n</details>\r\n\r\n<details>\r\n <summary>Agent policies</summary>\r\n\r\n\r\n\r\n</details>\r\n\r\n<details>\r\n <summary>Enrollment keys</summary>\r\n\r\n\r\n\r\n\r\n</details>\r\n\r\n### Testing\r\n1. With a normal user, navigate to the \"agents\", \"agent policies\" and\r\n\"enrollment keys\" tabs and click on the searchboxes. The suggestions\r\nshould be visible as normal\r\n2. Create a user with role Fleet \"all\", Integrations \"all\". Log in and\r\ncheck the above searchboxes, the suggestions should be visible as\r\nnormal. Previously they weren't.\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- [ ] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"ad663136c963562abd654e3ab8bce97b752dd3de","branchLabelMapping":{"^v8.12.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","backport:prev-minor","v8.12.0"],"number":172190,"url":"https://github.com/elastic/kibana/pull/172190","mergeCommit":{"message":"[Fleet] Replace dataviews suggestions in KQL searchboxes with internal ones (#172190)\n\nFixes https://github.com/elastic/kibana/issues/169760\r\nRelated to https://github.com/elastic/kibana/issues/171425\r\n\r\n## Summary\r\n\r\n[Fleet] Replace dataviews suggestions in KQL searchboxes with internal\r\nones. Now using Fleet mappings to create the suggestions fields instead\r\nof fetching them through dataView plugin.\r\nThis is done for two reasons:\r\n\r\n- Solves [permission\r\nproblems](https://github.com/elastic/kibana/issues/169760) when the user\r\ndoesn't have privileges to read Fleet indices\r\n- Allows us to search only those mappings that we want to expose,\r\ninstead of all of them\r\n\r\nOnly weird thing is that the [querystring\r\ncomponent](1f8c816901/src/plugins/unified_search/public/query_string_input/query_string_input.tsx (L161))\r\nhas a cap to show max 50 suggestions. Since for agents suggestions we\r\nare showing some more fields, so the ones starting with `u` are not\r\nvisible anymore. I though I had a bug in the way I was creating the\r\n`fieldsMap` but in reality there's no way to show more suggestions than\r\n50 (without touching the original component, which I would gladly\r\navoid).\r\n\r\n\r\n### Screenshots\r\nThere should be no visible difference with the current suggestions. \r\n<details>\r\n <summary>Agents</summary>\r\n\r\n\r\n\r\n\r\n \r\n</details>\r\n\r\n<details>\r\n <summary>Agent policies</summary>\r\n\r\n\r\n\r\n</details>\r\n\r\n<details>\r\n <summary>Enrollment keys</summary>\r\n\r\n\r\n\r\n\r\n</details>\r\n\r\n### Testing\r\n1. With a normal user, navigate to the \"agents\", \"agent policies\" and\r\n\"enrollment keys\" tabs and click on the searchboxes. The suggestions\r\nshould be visible as normal\r\n2. Create a user with role Fleet \"all\", Integrations \"all\". Log in and\r\ncheck the above searchboxes, the suggestions should be visible as\r\nnormal. Previously they weren't.\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- [ ] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"ad663136c963562abd654e3ab8bce97b752dd3de"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.12.0","labelRegex":"^v8.12.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/172190","number":172190,"mergeCommit":{"message":"[Fleet] Replace dataviews suggestions in KQL searchboxes with internal ones (#172190)\n\nFixes https://github.com/elastic/kibana/issues/169760\r\nRelated to https://github.com/elastic/kibana/issues/171425\r\n\r\n## Summary\r\n\r\n[Fleet] Replace dataviews suggestions in KQL searchboxes with internal\r\nones. Now using Fleet mappings to create the suggestions fields instead\r\nof fetching them through dataView plugin.\r\nThis is done for two reasons:\r\n\r\n- Solves [permission\r\nproblems](https://github.com/elastic/kibana/issues/169760) when the user\r\ndoesn't have privileges to read Fleet indices\r\n- Allows us to search only those mappings that we want to expose,\r\ninstead of all of them\r\n\r\nOnly weird thing is that the [querystring\r\ncomponent](1f8c816901/src/plugins/unified_search/public/query_string_input/query_string_input.tsx (L161))\r\nhas a cap to show max 50 suggestions. Since for agents suggestions we\r\nare showing some more fields, so the ones starting with `u` are not\r\nvisible anymore. I though I had a bug in the way I was creating the\r\n`fieldsMap` but in reality there's no way to show more suggestions than\r\n50 (without touching the original component, which I would gladly\r\navoid).\r\n\r\n\r\n### Screenshots\r\nThere should be no visible difference with the current suggestions. \r\n<details>\r\n <summary>Agents</summary>\r\n\r\n\r\n\r\n\r\n \r\n</details>\r\n\r\n<details>\r\n <summary>Agent policies</summary>\r\n\r\n\r\n\r\n</details>\r\n\r\n<details>\r\n <summary>Enrollment keys</summary>\r\n\r\n\r\n\r\n\r\n</details>\r\n\r\n### Testing\r\n1. With a normal user, navigate to the \"agents\", \"agent policies\" and\r\n\"enrollment keys\" tabs and click on the searchboxes. The suggestions\r\nshould be visible as normal\r\n2. Create a user with role Fleet \"all\", Integrations \"all\". Log in and\r\ncheck the above searchboxes, the suggestions should be visible as\r\nnormal. Previously they weren't.\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- [ ] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"ad663136c963562abd654e3ab8bce97b752dd3de"}}]}] BACKPORT--> --------- Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>	2023-12-04 08:22:55 -07:00
Chris Cowan	f698bed1aa	[SLO][8.11] Add date_formats to SLI ingest pipeline template (#172377) ... ## Summary This PR fixes #172372 by adding the `date_formats` attribute to the `date_index_name` pipeline step for the SLI ingest pipeline that every SLO runs through. This PR is only for 8.11, the fix for main will be included with: https://github.com/elastic/kibana/pull/172224	2023-12-01 13:49:28 -07:00
christineweng	44b9cf26ee	[Security Solution]Fix page reload crash when preview panel is open in alerts flyout (#172323) ... ## Summary Fixes page reload crash when the preview panel is open. https://github.com/elastic/kibana/issues/172324 ### Checklist - [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)	2023-12-01 11:49:28 -06:00
Kibana Machine	bf69b7f459	[8.11] [Lens] Handle invalid values gracefully for static value operation (#172198) (#172370) ... # Backport This will backport the following commits from `main` to `8.11`: - [[Lens] Handle invalid values gracefully for static value operation (#172198)](https://github.com/elastic/kibana/pull/172198) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Marco Liberati","email":"dej611@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-12-01T09:45:42Z","message":"[Lens] Handle invalid values gracefully for static value operation (#172198)\n\n## Summary\r\n\r\nFixes #171959 \r\n\r\nI've extended valid static value check to 15 digits (which is the max\r\nsupport by JS as implementing the [64-bit IEEE\r\n574](https://en.wikipedia.org/wiki/Double-precision_floating-point_format)).\r\n\r\n<img width=\"1224\" alt=\"Screenshot 2023-11-30 at 10 23 13\"\r\nsrc=\"bf88c0c8-9e51-4c8f-912d-abd82f292eda\">\r\n\r\nNote: an alternative approach would be to make it pass nonetheless and\r\ntrunc the numeric value at 15th digit.\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- [ ] [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\n---------\r\n\r\nCo-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>","sha":"1f8c816901fa286b842ac652b0fce86608d01202","branchLabelMapping":{"^v8.12.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Visualizations","Feature:Lens","backport:prev-minor","v8.12.0"],"number":172198,"url":"https://github.com/elastic/kibana/pull/172198","mergeCommit":{"message":"[Lens] Handle invalid values gracefully for static value operation (#172198)\n\n## Summary\r\n\r\nFixes #171959 \r\n\r\nI've extended valid static value check to 15 digits (which is the max\r\nsupport by JS as implementing the [64-bit IEEE\r\n574](https://en.wikipedia.org/wiki/Double-precision_floating-point_format)).\r\n\r\n<img width=\"1224\" alt=\"Screenshot 2023-11-30 at 10 23 13\"\r\nsrc=\"bf88c0c8-9e51-4c8f-912d-abd82f292eda\">\r\n\r\nNote: an alternative approach would be to make it pass nonetheless and\r\ntrunc the numeric value at 15th digit.\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- [ ] [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\n---------\r\n\r\nCo-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>","sha":"1f8c816901fa286b842ac652b0fce86608d01202"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.12.0","labelRegex":"^v8.12.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/172198","number":172198,"mergeCommit":{"message":"[Lens] Handle invalid values gracefully for static value operation (#172198)\n\n## Summary\r\n\r\nFixes #171959 \r\n\r\nI've extended valid static value check to 15 digits (which is the max\r\nsupport by JS as implementing the [64-bit IEEE\r\n574](https://en.wikipedia.org/wiki/Double-precision_floating-point_format)).\r\n\r\n<img width=\"1224\" alt=\"Screenshot 2023-11-30 at 10 23 13\"\r\nsrc=\"bf88c0c8-9e51-4c8f-912d-abd82f292eda\">\r\n\r\nNote: an alternative approach would be to make it pass nonetheless and\r\ntrunc the numeric value at 15th digit.\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- [ ] [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\n---------\r\n\r\nCo-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>","sha":"1f8c816901fa286b842ac652b0fce86608d01202"}}]}] BACKPORT--> Co-authored-by: Marco Liberati <dej611@users.noreply.github.com>	2023-12-01 09:33:01 -07:00
Davis McPhee	11eb765f54	[8.11] [Discover/CSV Reporting] Fix support for nested field columns in CSV reports (#172240) (#172335) ... # Backport This will backport the following commits from `main` to `8.11`: - [[Discover/CSV Reporting] Fix support for nested field columns in CSV reports (#172240)](https://github.com/elastic/kibana/pull/172240) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Davis McPhee","email":"davis.mcphee@elastic.co"},"sourceCommit":{"committedDate":"2023-11-30T16:43:39Z","message":"[Discover/CSV Reporting] Fix support for nested field columns in CSV reports (#172240)\n\n## Summary\r\n\r\nWhen we generate the parameters for the report, we add all of the\r\nselected columns as entries in the search request `fields` array (or `*`\r\nif none are selected, which is why this case works), but this doesn't\r\nwork for nested fields since [the fields API doesn't support nested\r\nfield\r\nroots](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-fields.html#search-fields-nested):\r\n>However, when the `fields` pattern targets the nested `user` field\r\ndirectly, no values will be returned because the pattern doesn’t match\r\nany leaf fields.\r\n\r\nInstead we can detect nested fields and add them to the `fields` array\r\nas `{nestedFieldName}.*`, ensuring that all of the leaf fields are\r\nreturned in the response.\r\n\r\nFixes #172236.\r\n\r\n### Checklist\r\n\r\n- [ ] 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\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\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- [ ] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n- [ ] Any UI touched in this PR does not create any new axe failures\r\n(run axe in browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n- [ ] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n- [ ] This renders correctly on smaller devices using a responsive\r\nlayout. (You can test this [in your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n- [ ] This was checked for [cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"ab5ff9ca626baa90c3cc0e92813ff70cb5956e23","branchLabelMapping":{"^v8.12.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:DataDiscovery","backport:prev-minor","backport:prev-MAJOR","v8.12.0"],"number":172240,"url":"https://github.com/elastic/kibana/pull/172240","mergeCommit":{"message":"[Discover/CSV Reporting] Fix support for nested field columns in CSV reports (#172240)\n\n## Summary\r\n\r\nWhen we generate the parameters for the report, we add all of the\r\nselected columns as entries in the search request `fields` array (or `*`\r\nif none are selected, which is why this case works), but this doesn't\r\nwork for nested fields since [the fields API doesn't support nested\r\nfield\r\nroots](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-fields.html#search-fields-nested):\r\n>However, when the `fields` pattern targets the nested `user` field\r\ndirectly, no values will be returned because the pattern doesn’t match\r\nany leaf fields.\r\n\r\nInstead we can detect nested fields and add them to the `fields` array\r\nas `{nestedFieldName}.*`, ensuring that all of the leaf fields are\r\nreturned in the response.\r\n\r\nFixes #172236.\r\n\r\n### Checklist\r\n\r\n- [ ] 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\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\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- [ ] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n- [ ] Any UI touched in this PR does not create any new axe failures\r\n(run axe in browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n- [ ] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n- [ ] This renders correctly on smaller devices using a responsive\r\nlayout. (You can test this [in your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n- [ ] This was checked for [cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"ab5ff9ca626baa90c3cc0e92813ff70cb5956e23"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.12.0","labelRegex":"^v8.12.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/172240","number":172240,"mergeCommit":{"message":"[Discover/CSV Reporting] Fix support for nested field columns in CSV reports (#172240)\n\n## Summary\r\n\r\nWhen we generate the parameters for the report, we add all of the\r\nselected columns as entries in the search request `fields` array (or `*`\r\nif none are selected, which is why this case works), but this doesn't\r\nwork for nested fields since [the fields API doesn't support nested\r\nfield\r\nroots](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-fields.html#search-fields-nested):\r\n>However, when the `fields` pattern targets the nested `user` field\r\ndirectly, no values will be returned because the pattern doesn’t match\r\nany leaf fields.\r\n\r\nInstead we can detect nested fields and add them to the `fields` array\r\nas `{nestedFieldName}.*`, ensuring that all of the leaf fields are\r\nreturned in the response.\r\n\r\nFixes #172236.\r\n\r\n### Checklist\r\n\r\n- [ ] 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\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\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- [ ] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n- [ ] Any UI touched in this PR does not create any new axe failures\r\n(run axe in browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n- [ ] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n- [ ] This renders correctly on smaller devices using a responsive\r\nlayout. (You can test this [in your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n- [ ] This was checked for [cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"ab5ff9ca626baa90c3cc0e92813ff70cb5956e23"}}]}] BACKPORT-->	2023-12-01 11:56:34 -04:00
Kibana Machine	fb019230f0	[8.11] [Security Solution] Fix analyzer panel width (#172026) (#172328) ... # Backport This will backport the following commits from `main` to `8.11`: - [[Security Solution] Fix analyzer panel width (#172026)](https://github.com/elastic/kibana/pull/172026) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"christineweng","email":"18648970+christineweng@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-11-30T21:14:57Z","message":"[Security Solution] Fix analyzer panel width (#172026)\n\n## Summary\r\n\r\nFixes column not breaking correctly in analyzer. 3 places where this bug\r\noccured: node details, event details and control panel. Event details\r\npanel was fixed in [PR](https://github.com/elastic/kibana/pull/170329).\r\nThis PR covers the other two.\r\n\r\n\r\n\r\n\r\n### Checklist\r\n\r\n- [x] This was checked for [cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)","sha":"2e52943bc70f49b7b3dab448d839c4af0e636328","branchLabelMapping":{"^v8.12.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team: SecuritySolution","Team:Threat Hunting:Investigations","v8.12.0","v8.11.2"],"number":172026,"url":"https://github.com/elastic/kibana/pull/172026","mergeCommit":{"message":"[Security Solution] Fix analyzer panel width (#172026)\n\n## Summary\r\n\r\nFixes column not breaking correctly in analyzer. 3 places where this bug\r\noccured: node details, event details and control panel. Event details\r\npanel was fixed in [PR](https://github.com/elastic/kibana/pull/170329).\r\nThis PR covers the other two.\r\n\r\n\r\n\r\n\r\n### Checklist\r\n\r\n- [x] This was checked for [cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)","sha":"2e52943bc70f49b7b3dab448d839c4af0e636328"}},"sourceBranch":"main","suggestedTargetBranches":["8.11"],"targetPullRequestStates":[{"branch":"main","label":"v8.12.0","labelRegex":"^v8.12.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/172026","number":172026,"mergeCommit":{"message":"[Security Solution] Fix analyzer panel width (#172026)\n\n## Summary\r\n\r\nFixes column not breaking correctly in analyzer. 3 places where this bug\r\noccured: node details, event details and control panel. Event details\r\npanel was fixed in [PR](https://github.com/elastic/kibana/pull/170329).\r\nThis PR covers the other two.\r\n\r\n\r\n\r\n\r\n### Checklist\r\n\r\n- [x] This was checked for [cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)","sha":"2e52943bc70f49b7b3dab448d839c4af0e636328"}},{"branch":"8.11","label":"v8.11.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: christineweng <18648970+christineweng@users.noreply.github.com>	2023-11-30 15:43:16 -07:00
Tiago Vila Verde	1de9b5b3fc	[8.11] [Security Solution] [Entity Analytics] Correct References under 'Useful Links' in Risk Score Enablement page (#171089) (#171838) ... # Backport This will backport the following commits from `main` to `8.11`: - [[Security Solution] [Entity Analytics] Correct References under 'Useful Links' in Risk Score Enablement page (#171089)](https://github.com/elastic/kibana/pull/171089) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Tiago Vila Verde","email":"tiago.vilaverde@elastic.co"},"sourceCommit":{"committedDate":"2023-11-23T10:20:23Z","message":"[Security Solution] [Entity Analytics] Correct References under 'Useful Links' in Risk Score Enablement page (#171089)\n\n## Summary\r\n\r\nGet rid of `Host/User` distinction in risk scoring and replace it with\r\n`Entity`, as per:\r\n[#7920](https://github.com/elastic/security-team/issues/7920)\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] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [x]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n- [x] Any UI touched in this PR does not create any new axe failures\r\n(run axe in browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n- [x] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n- [x] This renders correctly on smaller devices using a responsive\r\nlayout. (You can test this [in your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n- [x] This was checked for [cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n\r\n\r\n### For maintainers\r\n\r\n- [x] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by: Sergi Massaneda <sergi.massaneda@gmail.com>\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"3ec310b5192f4bac9b325d3160549800e302fe3e","branchLabelMapping":{"^v8.12.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","Team: SecuritySolution","v8.12.0","Team:Entity Analytics","v8.11.2"],"number":171089,"url":"https://github.com/elastic/kibana/pull/171089","mergeCommit":{"message":"[Security Solution] [Entity Analytics] Correct References under 'Useful Links' in Risk Score Enablement page (#171089)\n\n## Summary\r\n\r\nGet rid of `Host/User` distinction in risk scoring and replace it with\r\n`Entity`, as per:\r\n[#7920](https://github.com/elastic/security-team/issues/7920)\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] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [x]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n- [x] Any UI touched in this PR does not create any new axe failures\r\n(run axe in browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n- [x] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n- [x] This renders correctly on smaller devices using a responsive\r\nlayout. (You can test this [in your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n- [x] This was checked for [cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n\r\n\r\n### For maintainers\r\n\r\n- [x] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by: Sergi Massaneda <sergi.massaneda@gmail.com>\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"3ec310b5192f4bac9b325d3160549800e302fe3e"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.12.0","labelRegex":"^v8.12.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/171089","number":171089,"mergeCommit":{"message":"[Security Solution] [Entity Analytics] Correct References under 'Useful Links' in Risk Score Enablement page (#171089)\n\n## Summary\r\n\r\nGet rid of `Host/User` distinction in risk scoring and replace it with\r\n`Entity`, as per:\r\n[#7920](https://github.com/elastic/security-team/issues/7920)\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] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [x]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n- [x] Any UI touched in this PR does not create any new axe failures\r\n(run axe in browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n- [x] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n- [x] This renders correctly on smaller devices using a responsive\r\nlayout. (You can test this [in your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n- [x] This was checked for [cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n\r\n\r\n### For maintainers\r\n\r\n- [x] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by: Sergi Massaneda <sergi.massaneda@gmail.com>\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"3ec310b5192f4bac9b325d3160549800e302fe3e"}},{"branch":"8.11","label":"v8.11.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/171835","number":171835,"state":"OPEN"}]}] BACKPORT--> Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>	2023-11-30 09:30:20 -07:00
Kyle Pollich	c4b7c82eae	[8.11] [Fleet] Support integration secrets with required: false (#172078) (#172201) ... # Backport This will backport the following commits from `main` to `8.11`: - [[Fleet] Support integration secrets with `required: false` (#172078)](https://github.com/elastic/kibana/pull/172078) <!--- Backport version: 8.9.8 --> ### 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":"2023-11-28T16:52:01Z","message":"[Fleet] Support integration secrets with `required: false` (#172078)\n\n## Summary\r\n\r\nSupport secrets with `required: false` in package manifests.\r\n\r\nCloses #172061\r\n\r\n## To test\r\n\r\n1. Set up an integration in a local package registry with a variable\r\nthat has `secret: true` and `required: false`, e.g.\r\n\r\n```yml\r\n- name: secret_token\r\n type: password\r\n title: (Test) Secret Token\r\n description: |\r\n Test non-required secret\r\n show_user: true\r\n secret: true\r\n required: false\r\n```\r\n\r\n2. Create a package policy for your test package and note the optional\r\nsecret is rendered properly\r\n3. Submit the policy editor form without filling out a value for the\r\noptional secret\r\n4. Observe the request is successful\r\n5. Edit the package policy and set a value for the optional secret\r\n6. Observe that the secret creation logic works as expected\r\n\r\n## Screen recording\r\n\r\n\r\n36e271c5-29d0-49f8-91e8-abc6a7871b20","sha":"e64f475a013e1160f0938e14f8da7dcbf97a44bb","branchLabelMapping":{"^v8.12.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Fleet","backport:prev-minor","v8.12.0"],"number":172078,"url":"https://github.com/elastic/kibana/pull/172078","mergeCommit":{"message":"[Fleet] Support integration secrets with `required: false` (#172078)\n\n## Summary\r\n\r\nSupport secrets with `required: false` in package manifests.\r\n\r\nCloses #172061\r\n\r\n## To test\r\n\r\n1. Set up an integration in a local package registry with a variable\r\nthat has `secret: true` and `required: false`, e.g.\r\n\r\n```yml\r\n- name: secret_token\r\n type: password\r\n title: (Test) Secret Token\r\n description: |\r\n Test non-required secret\r\n show_user: true\r\n secret: true\r\n required: false\r\n```\r\n\r\n2. Create a package policy for your test package and note the optional\r\nsecret is rendered properly\r\n3. Submit the policy editor form without filling out a value for the\r\noptional secret\r\n4. Observe the request is successful\r\n5. Edit the package policy and set a value for the optional secret\r\n6. Observe that the secret creation logic works as expected\r\n\r\n## Screen recording\r\n\r\n\r\n36e271c5-29d0-49f8-91e8-abc6a7871b20","sha":"e64f475a013e1160f0938e14f8da7dcbf97a44bb"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.12.0","labelRegex":"^v8.12.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/172078","number":172078,"mergeCommit":{"message":"[Fleet] Support integration secrets with `required: false` (#172078)\n\n## Summary\r\n\r\nSupport secrets with `required: false` in package manifests.\r\n\r\nCloses #172061\r\n\r\n## To test\r\n\r\n1. Set up an integration in a local package registry with a variable\r\nthat has `secret: true` and `required: false`, e.g.\r\n\r\n```yml\r\n- name: secret_token\r\n type: password\r\n title: (Test) Secret Token\r\n description: |\r\n Test non-required secret\r\n show_user: true\r\n secret: true\r\n required: false\r\n```\r\n\r\n2. Create a package policy for your test package and note the optional\r\nsecret is rendered properly\r\n3. Submit the policy editor form without filling out a value for the\r\noptional secret\r\n4. Observe the request is successful\r\n5. Edit the package policy and set a value for the optional secret\r\n6. Observe that the secret creation logic works as expected\r\n\r\n## Screen recording\r\n\r\n\r\n36e271c5-29d0-49f8-91e8-abc6a7871b20","sha":"e64f475a013e1160f0938e14f8da7dcbf97a44bb"}}]}] BACKPORT--> Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>	2023-11-29 15:18:44 -05:00
Kyle Pollich	279c469047	[8.11] [Fleet] Improve UX for policy secrets (#171405) (#172098) ... # Backport This will backport the following commits from `main` to `8.11`: - [[Fleet] Improve UX for policy secrets (#171405)](https://github.com/elastic/kibana/pull/171405) <!--- Backport version: 8.9.8 --> ### 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":"2023-11-16T19:35:19Z","message":"[Fleet] Improve UX for policy secrets (#171405)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/171225\r\n\r\n- Highlights secrets during package policy creation with a distinct\r\nbackground and icon\r\n- Add tooltip + docs link for secrets where appropriate\r\n- Detect \"new secrets\" during policy upgrade and alert the user in a\r\nseparate callout\r\n\r\n## To do\r\n- [x] Fix any failing tests\r\n- [x] Add tests for \"new secrets\" detection logic\r\n\r\n## Screenshots\r\n\r\n\r\n\r\n\r\n## How to test\r\n\r\nThere's probably an easier way to do this, but this is what I did\r\n\r\n1. Clone https://github.com/elastic/package-registry and\r\nhttps://github.com/elastic/integrations\r\n2. Add the following to `config.yml` in your package-registry repo\r\n\r\n```yml\r\npackage_paths:\r\n - path/to/your/integrations/build/packages\r\n```\r\n\r\n3. Build a version of an integration with some `secrets: true` for\r\nvarious variables. I used `1password`\r\n\r\n```shell\r\ncd integrations/packages/1password\r\n# Edit `manifest.yml` or a given `data_stream/*/manifest.yml` file to change some variables to `secret: true`. Also bump the version and update `changelog.yml`\r\nelastic-package build\r\n```\r\n\r\n4. Run the local package registry e.g. \r\n\r\n```shell\r\ncd package-registry\r\ngo run . --feature-proxy-mode=true -proxy-to=https://epr.elastic.co # makes it so you can still see EPR packages in Kibana\r\n```\r\n\r\n5. Update your `kibana.dev.yml` to point at your local package registry\r\n\r\n```yml\r\nxpack.fleet.registryUrl: http://localhost:8080\r\n```\r\n\r\n6. Start Kibana and Elasticsearch and install, upgrade, etc your package\r\nin question to verify the changes\r\n\r\n---------\r\n\r\nCo-authored-by: David Kilfoyle <41695641+kilfoyle@users.noreply.github.com>","sha":"9396ef3d6bed213b681970a4914eeb558a30ed44","branchLabelMapping":{"^v8.12.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","Team:Fleet","backport:prev-minor","v8.12.0"],"number":171405,"url":"https://github.com/elastic/kibana/pull/171405","mergeCommit":{"message":"[Fleet] Improve UX for policy secrets (#171405)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/171225\r\n\r\n- Highlights secrets during package policy creation with a distinct\r\nbackground and icon\r\n- Add tooltip + docs link for secrets where appropriate\r\n- Detect \"new secrets\" during policy upgrade and alert the user in a\r\nseparate callout\r\n\r\n## To do\r\n- [x] Fix any failing tests\r\n- [x] Add tests for \"new secrets\" detection logic\r\n\r\n## Screenshots\r\n\r\n\r\n\r\n\r\n## How to test\r\n\r\nThere's probably an easier way to do this, but this is what I did\r\n\r\n1. Clone https://github.com/elastic/package-registry and\r\nhttps://github.com/elastic/integrations\r\n2. Add the following to `config.yml` in your package-registry repo\r\n\r\n```yml\r\npackage_paths:\r\n - path/to/your/integrations/build/packages\r\n```\r\n\r\n3. Build a version of an integration with some `secrets: true` for\r\nvarious variables. I used `1password`\r\n\r\n```shell\r\ncd integrations/packages/1password\r\n# Edit `manifest.yml` or a given `data_stream/*/manifest.yml` file to change some variables to `secret: true`. Also bump the version and update `changelog.yml`\r\nelastic-package build\r\n```\r\n\r\n4. Run the local package registry e.g. \r\n\r\n```shell\r\ncd package-registry\r\ngo run . --feature-proxy-mode=true -proxy-to=https://epr.elastic.co # makes it so you can still see EPR packages in Kibana\r\n```\r\n\r\n5. Update your `kibana.dev.yml` to point at your local package registry\r\n\r\n```yml\r\nxpack.fleet.registryUrl: http://localhost:8080\r\n```\r\n\r\n6. Start Kibana and Elasticsearch and install, upgrade, etc your package\r\nin question to verify the changes\r\n\r\n---------\r\n\r\nCo-authored-by: David Kilfoyle <41695641+kilfoyle@users.noreply.github.com>","sha":"9396ef3d6bed213b681970a4914eeb558a30ed44"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.12.0","labelRegex":"^v8.12.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/171405","number":171405,"mergeCommit":{"message":"[Fleet] Improve UX for policy secrets (#171405)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/171225\r\n\r\n- Highlights secrets during package policy creation with a distinct\r\nbackground and icon\r\n- Add tooltip + docs link for secrets where appropriate\r\n- Detect \"new secrets\" during policy upgrade and alert the user in a\r\nseparate callout\r\n\r\n## To do\r\n- [x] Fix any failing tests\r\n- [x] Add tests for \"new secrets\" detection logic\r\n\r\n## Screenshots\r\n\r\n\r\n\r\n\r\n## How to test\r\n\r\nThere's probably an easier way to do this, but this is what I did\r\n\r\n1. Clone https://github.com/elastic/package-registry and\r\nhttps://github.com/elastic/integrations\r\n2. Add the following to `config.yml` in your package-registry repo\r\n\r\n```yml\r\npackage_paths:\r\n - path/to/your/integrations/build/packages\r\n```\r\n\r\n3. Build a version of an integration with some `secrets: true` for\r\nvarious variables. I used `1password`\r\n\r\n```shell\r\ncd integrations/packages/1password\r\n# Edit `manifest.yml` or a given `data_stream/*/manifest.yml` file to change some variables to `secret: true`. Also bump the version and update `changelog.yml`\r\nelastic-package build\r\n```\r\n\r\n4. Run the local package registry e.g. \r\n\r\n```shell\r\ncd package-registry\r\ngo run . --feature-proxy-mode=true -proxy-to=https://epr.elastic.co # makes it so you can still see EPR packages in Kibana\r\n```\r\n\r\n5. Update your `kibana.dev.yml` to point at your local package registry\r\n\r\n```yml\r\nxpack.fleet.registryUrl: http://localhost:8080\r\n```\r\n\r\n6. Start Kibana and Elasticsearch and install, upgrade, etc your package\r\nin question to verify the changes\r\n\r\n---------\r\n\r\nCo-authored-by: David Kilfoyle <41695641+kilfoyle@users.noreply.github.com>","sha":"9396ef3d6bed213b681970a4914eeb558a30ed44"}}]}] BACKPORT--> --------- Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>	2023-11-29 12:01:08 -05:00
Stratoula Kalafateli	ddd3e8dea7	[8.11] [ES|QL] Make the dashboard SO lighter (#172130) (#172145) ... # Backport This will backport the following commits from `main` to `8.11`: - [[ES|QL] Make the dashboard SO lighter (#172130)](https://github.com/elastic/kibana/pull/172130) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Stratoula Kalafateli","email":"efstratia.kalafateli@elastic.co"},"sourceCommit":{"committedDate":"2023-11-29T10:55:21Z","message":"[ES|QL] Make the dashboard SO lighter (#172130)\n\n## Summary\r\n\r\nThis PR makes the dashboard SO lighter by removing the initialContext\r\nfrom the state. It is not needed after the navigation from Discover to\r\nDashboard and can create SO size problems as it contains a lot of\r\ninformation for the transition.","sha":"cb3fd2132f47d43e4d46b8f5b085195cb8dda806","branchLabelMapping":{"^v8.12.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Visualizations","backport:prev-minor","Feature:ES|QL","v8.12.0","v8.11.2"],"number":172130,"url":"https://github.com/elastic/kibana/pull/172130","mergeCommit":{"message":"[ES|QL] Make the dashboard SO lighter (#172130)\n\n## Summary\r\n\r\nThis PR makes the dashboard SO lighter by removing the initialContext\r\nfrom the state. It is not needed after the navigation from Discover to\r\nDashboard and can create SO size problems as it contains a lot of\r\ninformation for the transition.","sha":"cb3fd2132f47d43e4d46b8f5b085195cb8dda806"}},"sourceBranch":"main","suggestedTargetBranches":["8.11"],"targetPullRequestStates":[{"branch":"main","label":"v8.12.0","labelRegex":"^v8.12.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/172130","number":172130,"mergeCommit":{"message":"[ES|QL] Make the dashboard SO lighter (#172130)\n\n## Summary\r\n\r\nThis PR makes the dashboard SO lighter by removing the initialContext\r\nfrom the state. It is not needed after the navigation from Discover to\r\nDashboard and can create SO size problems as it contains a lot of\r\ninformation for the transition.","sha":"cb3fd2132f47d43e4d46b8f5b085195cb8dda806"}},{"branch":"8.11","label":"v8.11.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->	2023-11-29 05:26:29 -07:00
Kibana Machine	5748e277be	[8.11] Enhance plugin documentation (#146678) (#172104) ... # Backport This will backport the following commits from `main` to `8.11`: - [Enhance plugin documentation (#146678)](https://github.com/elastic/kibana/pull/146678) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Gerard Soldevila","email":"gerard.soldevila@elastic.co"},"sourceCommit":{"committedDate":"2023-11-28T19:58:46Z","message":"Enhance plugin documentation (#146678)\n\nThe PR tackles a couple of improvements for the new `'notifications'`\nplugin documentation:\n\n- Add a link to the plugin API description in the kibana-dev-docs nav\nbar.\n- Convert the README to `mdx`.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"98b2cfbbb0442898e84189291b7f5c5a725a6115","branchLabelMapping":{"^v8.12.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","Team:AppServicesSv","release_note:skip","docs","DevDocs","documentation","APIDocs","backport:prev-minor","v8.12.0"],"number":146678,"url":"https://github.com/elastic/kibana/pull/146678","mergeCommit":{"message":"Enhance plugin documentation (#146678)\n\nThe PR tackles a couple of improvements for the new `'notifications'`\nplugin documentation:\n\n- Add a link to the plugin API description in the kibana-dev-docs nav\nbar.\n- Convert the README to `mdx`.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"98b2cfbbb0442898e84189291b7f5c5a725a6115"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.12.0","labelRegex":"^v8.12.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/146678","number":146678,"mergeCommit":{"message":"Enhance plugin documentation (#146678)\n\nThe PR tackles a couple of improvements for the new `'notifications'`\nplugin documentation:\n\n- Add a link to the plugin API description in the kibana-dev-docs nav\nbar.\n- Convert the README to `mdx`.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"98b2cfbbb0442898e84189291b7f5c5a725a6115"}}]}] BACKPORT--> Co-authored-by: Gerard Soldevila <gerard.soldevila@elastic.co>	2023-11-28 14:21:04 -07:00
Kibana Machine	35393bcdc2	[8.11] [Response Ops][Alerting] Remove echoed field value from bulk error responses when indexing alerts (#172020) (#172085) ... # Backport This will backport the following commits from `main` to `8.11`: - [[Response Ops][Alerting] Remove echoed field value from bulk error responses when indexing alerts (#172020)](https://github.com/elastic/kibana/pull/172020) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Ying Mao","email":"ying.mao@elastic.co"},"sourceCommit":{"committedDate":"2023-11-28T16:25:03Z","message":"[Response Ops][Alerting] Remove echoed field value from bulk error responses when indexing alerts (#172020)\n\n## Summary\r\n\r\nWhen alerts are bulk indexed in the rule registry and the alerts client,\r\nindexing errors may be returned where the entire field value that failed\r\nto be indexed is echoed in the reason. This can cause unnecessarily\r\nverbose logging so we want to sanitize the field value.","sha":"d9ebfd9af1365bba54d5e1ac92f5e53f5fbebea8","branchLabelMapping":{"^v8.12.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Alerting","release_note:skip","Team:ResponseOps","backport:prev-minor","backport:prev-MAJOR","v8.12.0"],"number":172020,"url":"https://github.com/elastic/kibana/pull/172020","mergeCommit":{"message":"[Response Ops][Alerting] Remove echoed field value from bulk error responses when indexing alerts (#172020)\n\n## Summary\r\n\r\nWhen alerts are bulk indexed in the rule registry and the alerts client,\r\nindexing errors may be returned where the entire field value that failed\r\nto be indexed is echoed in the reason. This can cause unnecessarily\r\nverbose logging so we want to sanitize the field value.","sha":"d9ebfd9af1365bba54d5e1ac92f5e53f5fbebea8"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.12.0","labelRegex":"^v8.12.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/172020","number":172020,"mergeCommit":{"message":"[Response Ops][Alerting] Remove echoed field value from bulk error responses when indexing alerts (#172020)\n\n## Summary\r\n\r\nWhen alerts are bulk indexed in the rule registry and the alerts client,\r\nindexing errors may be returned where the entire field value that failed\r\nto be indexed is echoed in the reason. This can cause unnecessarily\r\nverbose logging so we want to sanitize the field value.","sha":"d9ebfd9af1365bba54d5e1ac92f5e53f5fbebea8"}}]}] BACKPORT--> Co-authored-by: Ying Mao <ying.mao@elastic.co>	2023-11-28 10:42:21 -07:00
Kibana Machine	5065020e52	[8.11] [Fleet] Fix package overview details title wrap (#171415) (#171421) ... # Backport This will backport the following commits from `main` to `8.11`: - [[Fleet] Fix package overview details title wrap (#171415)](https://github.com/elastic/kibana/pull/171415) <!--- 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":"2023-11-16T16:05:31Z","message":"[Fleet] Fix package overview details title wrap (#171415)","sha":"810db499c3e5d2dd9c5be23f0d1eb09016ac3905","branchLabelMapping":{"^v8.12.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:Fleet","backport:prev-minor","v8.12.0"],"number":171415,"url":"https://github.com/elastic/kibana/pull/171415","mergeCommit":{"message":"[Fleet] Fix package overview details title wrap (#171415)","sha":"810db499c3e5d2dd9c5be23f0d1eb09016ac3905"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.12.0","labelRegex":"^v8.12.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/171415","number":171415,"mergeCommit":{"message":"[Fleet] Fix package overview details title wrap (#171415)","sha":"810db499c3e5d2dd9c5be23f0d1eb09016ac3905"}}]}] BACKPORT--> Co-authored-by: Nicolas Chaulet <nicolas.chaulet@elastic.co>	2023-11-28 07:55:05 -07:00
Lisa Cawley	70e913efe1	[8.11] [OAS] Migrate connector APIs to v3.1.0 (#171464) (#171945) ... # Backport This will backport the following commits from `main` to `8.11`: - [[OAS] Migrate connector APIs to v3.1.0 (#171464)](https://github.com/elastic/kibana/pull/171464) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Lisa Cawley","email":"lcawley@elastic.co"},"sourceCommit":{"committedDate":"2023-11-24T20:51:14Z","message":"[OAS] Migrate connector APIs to v3.1.0 (#171464)","sha":"14886bf8b8a1629535e9b3ce0d6a6485b98299e5","branchLabelMapping":{"^v8.12.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","docs","Feature:Actions/ConnectorsManagement","backport:prev-minor","v8.12.0"],"number":171464,"url":"https://github.com/elastic/kibana/pull/171464","mergeCommit":{"message":"[OAS] Migrate connector APIs to v3.1.0 (#171464)","sha":"14886bf8b8a1629535e9b3ce0d6a6485b98299e5"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.12.0","labelRegex":"^v8.12.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/171464","number":171464,"mergeCommit":{"message":"[OAS] Migrate connector APIs to v3.1.0 (#171464)","sha":"14886bf8b8a1629535e9b3ce0d6a6485b98299e5"}}]}] BACKPORT-->	2023-11-28 10:26:17 +00:00
Kibana Machine	ae1f93c75e	[8.11] [Fleet] Fix agent metrics aggregation for > 10 agents (#172016) (#172029) ... # Backport This will backport the following commits from `main` to `8.11`: - [[Fleet] Fix agent metrics aggregation for > 10 agents (#172016)](https://github.com/elastic/kibana/pull/172016) <!--- 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":"2023-11-27T22:26:51Z","message":"[Fleet] Fix agent metrics aggregation for > 10 agents (#172016)\n\n## Summary\n\nTo compute agent metrics we do a term aggregation there was an error as\nwe were not specifying size it was only fetching 10 items for that\naggregation resolving in incomplete results\n\n## Release note\n\nFix agents metrics retrieval on the agent list page, that was displaying\nN/A for agent with metrics for users with more than 10 agents.\n\n## Example \n### Before \n<img width=\"557\" alt=\"Screenshot 2023-11-27 at 2 20 57 PM\"\nsrc=\"d7928238-011a-4503-87e7-a39b50a98b50\">\n\n### After\n<img width=\"588\" alt=\"Screenshot 2023-11-27 at 2 21 29 PM\"\nsrc=\"6c9c2101-9cba-421d-ae13-a9b5ad892798\">\n\n\n## Tests\n\nIt seems adding automated tests for that issue to the existing test is\nnot trivial, not sure if it really add value to test that.\n\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"2cfc72240383a909b537677b7a73bebee67eb8b9","branchLabelMapping":{"^v8.12.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","Team:Fleet","backport:prev-minor","v8.12.0"],"number":172016,"url":"https://github.com/elastic/kibana/pull/172016","mergeCommit":{"message":"[Fleet] Fix agent metrics aggregation for > 10 agents (#172016)\n\n## Summary\n\nTo compute agent metrics we do a term aggregation there was an error as\nwe were not specifying size it was only fetching 10 items for that\naggregation resolving in incomplete results\n\n## Release note\n\nFix agents metrics retrieval on the agent list page, that was displaying\nN/A for agent with metrics for users with more than 10 agents.\n\n## Example \n### Before \n<img width=\"557\" alt=\"Screenshot 2023-11-27 at 2 20 57 PM\"\nsrc=\"d7928238-011a-4503-87e7-a39b50a98b50\">\n\n### After\n<img width=\"588\" alt=\"Screenshot 2023-11-27 at 2 21 29 PM\"\nsrc=\"6c9c2101-9cba-421d-ae13-a9b5ad892798\">\n\n\n## Tests\n\nIt seems adding automated tests for that issue to the existing test is\nnot trivial, not sure if it really add value to test that.\n\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"2cfc72240383a909b537677b7a73bebee67eb8b9"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.12.0","labelRegex":"^v8.12.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/172016","number":172016,"mergeCommit":{"message":"[Fleet] Fix agent metrics aggregation for > 10 agents (#172016)\n\n## Summary\n\nTo compute agent metrics we do a term aggregation there was an error as\nwe were not specifying size it was only fetching 10 items for that\naggregation resolving in incomplete results\n\n## Release note\n\nFix agents metrics retrieval on the agent list page, that was displaying\nN/A for agent with metrics for users with more than 10 agents.\n\n## Example \n### Before \n<img width=\"557\" alt=\"Screenshot 2023-11-27 at 2 20 57 PM\"\nsrc=\"d7928238-011a-4503-87e7-a39b50a98b50\">\n\n### After\n<img width=\"588\" alt=\"Screenshot 2023-11-27 at 2 21 29 PM\"\nsrc=\"6c9c2101-9cba-421d-ae13-a9b5ad892798\">\n\n\n## Tests\n\nIt seems adding automated tests for that issue to the existing test is\nnot trivial, not sure if it really add value to test that.\n\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"2cfc72240383a909b537677b7a73bebee67eb8b9"}}]}] BACKPORT--> Co-authored-by: Nicolas Chaulet <nicolas.chaulet@elastic.co>	2023-11-27 16:54:03 -07:00
Gergő Ábrahám	75cdadff54	[Defend Workflows][8.11] Unblock fleet setup when cannot decrypt uninstall tokens (#171998)	2023-11-27 13:22:53 -07:00
Kibana Machine	ddb0513b1c	[8.11] [OAS] Migrate case APIs to v3.1.0 (#171593) (#171936) ... # Backport This will backport the following commits from `main` to `8.11`: - [[OAS] Migrate case APIs to v3.1.0 (#171593)](https://github.com/elastic/kibana/pull/171593) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Lisa Cawley","email":"lcawley@elastic.co"},"sourceCommit":{"committedDate":"2023-11-24T17:08:34Z","message":"[OAS] Migrate case APIs to v3.1.0 (#171593)","sha":"ea85f2a4796243d5856f6a369b5e96d1805fdda0","branchLabelMapping":{"^v8.12.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","docs","Feature:Cases","backport:prev-minor","v8.12.0"],"number":171593,"url":"https://github.com/elastic/kibana/pull/171593","mergeCommit":{"message":"[OAS] Migrate case APIs to v3.1.0 (#171593)","sha":"ea85f2a4796243d5856f6a369b5e96d1805fdda0"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.12.0","labelRegex":"^v8.12.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/171593","number":171593,"mergeCommit":{"message":"[OAS] Migrate case APIs to v3.1.0 (#171593)","sha":"ea85f2a4796243d5856f6a369b5e96d1805fdda0"}}]}] BACKPORT--> Co-authored-by: Lisa Cawley <lcawley@elastic.co>	2023-11-24 11:25:03 -07:00
Jan Monschke	350d069b00	[8.11] [SecuritySolution] Remove @kbn/subscription-tracking (#171801) (#171884) ... # Backport This will backport the following commits from `main` to `8.11`: - [[SecuritySolution] Remove `@kbn/subscription-tracking` (#171801)](https://github.com/elastic/kibana/pull/171801) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Jan Monschke","email":"jan.monschke@elastic.co"},"sourceCommit":{"committedDate":"2023-11-23T15:39:23Z","message":"[SecuritySolution] Remove `@kbn/subscription-tracking` (#171801)\n\n## Summary\r\n\r\nThe package data isn't needed anymore, so we can remove that package. On\r\ntop, it seems like the package was causing some issues.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"df16cd9c2cfc08bc999f436a11913df50e71ce19","branchLabelMapping":{"^v8.12.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:Threat Hunting:Investigations","backport:prev-minor","v8.12.0","v8.11.2"],"number":171801,"url":"https://github.com/elastic/kibana/pull/171801","mergeCommit":{"message":"[SecuritySolution] Remove `@kbn/subscription-tracking` (#171801)\n\n## Summary\r\n\r\nThe package data isn't needed anymore, so we can remove that package. On\r\ntop, it seems like the package was causing some issues.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"df16cd9c2cfc08bc999f436a11913df50e71ce19"}},"sourceBranch":"main","suggestedTargetBranches":["8.11"],"targetPullRequestStates":[{"branch":"main","label":"v8.12.0","labelRegex":"^v8.12.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/171801","number":171801,"mergeCommit":{"message":"[SecuritySolution] Remove `@kbn/subscription-tracking` (#171801)\n\n## Summary\r\n\r\nThe package data isn't needed anymore, so we can remove that package. On\r\ntop, it seems like the package was causing some issues.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"df16cd9c2cfc08bc999f436a11913df50e71ce19"}},{"branch":"8.11","label":"v8.11.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>	2023-11-24 06:36:26 -07:00
Sergi Massaneda	5559c9b84c	[8.11] [Security Solution] Fix observable re-rendering component (#171772) (#171849) ... # Backport This will backport the following commits from `main` to `8.11`: - [[Security Solution] Fix observable re-rendering component (#171772)](https://github.com/elastic/kibana/pull/171772) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Sergi Massaneda","email":"sergi.massaneda@elastic.co"},"sourceCommit":{"committedDate":"2023-11-23T09:59:39Z","message":"[Security Solution] Fix observable re-rendering component (#171772)\n\n## Summary\r\n\r\nThere was a \"memory-leak\" bug on the `ContractComponents` logic (Get\r\nStarted page), which was causing a React error.\r\n\r\n<img width=\"814\" alt=\"render_depth_error\"\r\nsrc=\"c6353e53-9e4a-4103-b61c-1aaf67cda590\">\r\n\r\nThe bug was caused by the `pipe` call in the `getComponent# Backport This will backport the following commits from `main` to `8.11`: - [[Security Solution] Fix observable re-rendering component (#171772)](https://github.com/elastic/kibana/pull/171772) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT function\r\nreturning a new observable every call and the `LandingPageComponent` was\r\nnot memorizing it.\r\n\r\nI changed the `pipe` call by a regular `asObservable`, and created a\r\nreusable `useContractComponents` hook to unify the implementation, which\r\nalso memorizes the observable.\r\n\r\nI leveraged the changes to the `ContractComponents` implementation to\r\nsolve another problem, allowing the stored components to render normally\r\nas a `<Component />`, receiving props if needed, instead of having to\r\nrender always as an `{element}`.\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"49d1b6daaafc39cc284bdbf597418577f06bb403","branchLabelMapping":{"^v8.12.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:Threat Hunting","Team:Threat Hunting:Explore","v8.11.0","v8.12.0"],"number":171772,"url":"https://github.com/elastic/kibana/pull/171772","mergeCommit":{"message":"[Security Solution] Fix observable re-rendering component (#171772)\n\n## Summary\r\n\r\nThere was a \"memory-leak\" bug on the `ContractComponents` logic (Get\r\nStarted page), which was causing a React error.\r\n\r\n<img width=\"814\" alt=\"render_depth_error\"\r\nsrc=\"c6353e53-9e4a-4103-b61c-1aaf67cda590\">\r\n\r\nThe bug was caused by the `pipe` call in the `getComponent# Backport This will backport the following commits from `main` to `8.11`: - [[Security Solution] Fix observable re-rendering component (#171772)](https://github.com/elastic/kibana/pull/171772) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT function\r\nreturning a new observable every call and the `LandingPageComponent` was\r\nnot memorizing it.\r\n\r\nI changed the `pipe` call by a regular `asObservable`, and created a\r\nreusable `useContractComponents` hook to unify the implementation, which\r\nalso memorizes the observable.\r\n\r\nI leveraged the changes to the `ContractComponents` implementation to\r\nsolve another problem, allowing the stored components to render normally\r\nas a `<Component />`, receiving props if needed, instead of having to\r\nrender always as an `{element}`.\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"49d1b6daaafc39cc284bdbf597418577f06bb403"}},"sourceBranch":"main","suggestedTargetBranches":["8.11"],"targetPullRequestStates":[{"branch":"8.11","label":"v8.11.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.12.0","labelRegex":"^v8.12.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/171772","number":171772,"mergeCommit":{"message":"[Security Solution] Fix observable re-rendering component (#171772)\n\n## Summary\r\n\r\nThere was a \"memory-leak\" bug on the `ContractComponents` logic (Get\r\nStarted page), which was causing a React error.\r\n\r\n<img width=\"814\" alt=\"render_depth_error\"\r\nsrc=\"c6353e53-9e4a-4103-b61c-1aaf67cda590\">\r\n\r\nThe bug was caused by the `pipe` call in the `getComponent# Backport This will backport the following commits from `main` to `8.11`: - [[Security Solution] Fix observable re-rendering component (#171772)](https://github.com/elastic/kibana/pull/171772) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT function\r\nreturning a new observable every call and the `LandingPageComponent` was\r\nnot memorizing it.\r\n\r\nI changed the `pipe` call by a regular `asObservable`, and created a\r\nreusable `useContractComponents` hook to unify the implementation, which\r\nalso memorizes the observable.\r\n\r\nI leveraged the changes to the `ContractComponents` implementation to\r\nsolve another problem, allowing the stored components to render normally\r\nas a `<Component />`, receiving props if needed, instead of having to\r\nrender always as an `{element}`.\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"49d1b6daaafc39cc284bdbf597418577f06bb403"}}]}] BACKPORT--> --------- Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>	2023-11-24 10:47:05 +00:00
Lisa Cawley	62977ff0bb	[8.11] [OAS] Migrate machine learning APIs to v3.1.0 (#171594) (#171889) ... # Backport This will backport the following commits from `main` to `8.11`: - [[OAS] Migrate machine learning APIs to v3.1.0 (#171594)](https://github.com/elastic/kibana/pull/171594) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Lisa Cawley","email":"lcawley@elastic.co"},"sourceCommit":{"committedDate":"2023-11-23T19:46:05Z","message":"[OAS] Migrate machine learning APIs to v3.1.0 (#171594)","sha":"2f258a229c702fa10a58cbcf7baec7917d64c83c","branchLabelMapping":{"^v8.12.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","docs","backport:prev-minor","v8.12.0"],"number":171594,"url":"https://github.com/elastic/kibana/pull/171594","mergeCommit":{"message":"[OAS] Migrate machine learning APIs to v3.1.0 (#171594)","sha":"2f258a229c702fa10a58cbcf7baec7917d64c83c"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.12.0","labelRegex":"^v8.12.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/171594","number":171594,"mergeCommit":{"message":"[OAS] Migrate machine learning APIs to v3.1.0 (#171594)","sha":"2f258a229c702fa10a58cbcf7baec7917d64c83c"}}]}] BACKPORT-->	2023-11-23 14:42:19 -07:00
Kibana Machine	ab76b27933	[8.11] [ML] Fixing blocked jobs polling interval (#171878) (#171885) ... # Backport This will backport the following commits from `main` to `8.11`: - [[ML] Fixing blocked jobs polling interval (#171878)](https://github.com/elastic/kibana/pull/171878) <!--- 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":"2023-11-23T17:56:19Z","message":"[ML] Fixing blocked jobs polling interval (#171878)\n\nThere is a bug with the way we check whether or not to start polling for\r\nblocked jobs. We should only start polling there isn't an existing poll\r\nrunning.\r\nThis causes the polling to run as possible and to refresh the full jobs\r\nlist on every check.\r\nNow the blocked jobs polling correctly runs at the interval of 2s and\r\nthe full jobs list is only updated when there is a change in the list of\r\nblocked jobs.\r\n\r\nPartially fixes https://github.com/elastic/kibana/issues/171626\r\n\r\nA more in-depth change as specified in the issue can be done in follow\r\nup work. It's good to get this change in for the next release just in\r\ncase we run out of time for the larger change.","sha":"e7c793e0d74f2c48c788e7daf37dfc3b7cd68c9f","branchLabelMapping":{"^v8.12.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix",":ml","Feature:Anomaly Detection","v8.12.0","v8.11.2"],"number":171878,"url":"https://github.com/elastic/kibana/pull/171878","mergeCommit":{"message":"[ML] Fixing blocked jobs polling interval (#171878)\n\nThere is a bug with the way we check whether or not to start polling for\r\nblocked jobs. We should only start polling there isn't an existing poll\r\nrunning.\r\nThis causes the polling to run as possible and to refresh the full jobs\r\nlist on every check.\r\nNow the blocked jobs polling correctly runs at the interval of 2s and\r\nthe full jobs list is only updated when there is a change in the list of\r\nblocked jobs.\r\n\r\nPartially fixes https://github.com/elastic/kibana/issues/171626\r\n\r\nA more in-depth change as specified in the issue can be done in follow\r\nup work. It's good to get this change in for the next release just in\r\ncase we run out of time for the larger change.","sha":"e7c793e0d74f2c48c788e7daf37dfc3b7cd68c9f"}},"sourceBranch":"main","suggestedTargetBranches":["8.11"],"targetPullRequestStates":[{"branch":"main","label":"v8.12.0","labelRegex":"^v8.12.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/171878","number":171878,"mergeCommit":{"message":"[ML] Fixing blocked jobs polling interval (#171878)\n\nThere is a bug with the way we check whether or not to start polling for\r\nblocked jobs. We should only start polling there isn't an existing poll\r\nrunning.\r\nThis causes the polling to run as possible and to refresh the full jobs\r\nlist on every check.\r\nNow the blocked jobs polling correctly runs at the interval of 2s and\r\nthe full jobs list is only updated when there is a change in the list of\r\nblocked jobs.\r\n\r\nPartially fixes https://github.com/elastic/kibana/issues/171626\r\n\r\nA more in-depth change as specified in the issue can be done in follow\r\nup work. It's good to get this change in for the next release just in\r\ncase we run out of time for the larger change.","sha":"e7c793e0d74f2c48c788e7daf37dfc3b7cd68c9f"}},{"branch":"8.11","label":"v8.11.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: James Gowdy <jgowdy@elastic.co>	2023-11-23 12:04:55 -07:00
Kibana Machine	1911e66972	[8.11] [Security Solution] Changes coverage overview subtechnique display to base off active filters (#170988) (#171230) ... # Backport This will backport the following commits from `main` to `8.11`: - [[Security Solution] Changes coverage overview subtechnique display to base off active filters (#170988)](https://github.com/elastic/kibana/pull/170988) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Davis Plumlee","email":"56367316+dplumlee@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-11-14T19:04:09Z","message":"[Security Solution] Changes coverage overview subtechnique display to base off active filters (#170988)","sha":"87ec1440dcc1d25938795925237ca5194ee6551e","branchLabelMapping":{"^v8.12.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","impact:medium","Team:Detections and Resp","Team: SecuritySolution","Feature:Rule Management","Team:Detection Rule Management","v8.12.0","v8.11.2"],"number":170988,"url":"https://github.com/elastic/kibana/pull/170988","mergeCommit":{"message":"[Security Solution] Changes coverage overview subtechnique display to base off active filters (#170988)","sha":"87ec1440dcc1d25938795925237ca5194ee6551e"}},"sourceBranch":"main","suggestedTargetBranches":["8.11"],"targetPullRequestStates":[{"branch":"main","label":"v8.12.0","labelRegex":"^v8.12.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/170988","number":170988,"mergeCommit":{"message":"[Security Solution] Changes coverage overview subtechnique display to base off active filters (#170988)","sha":"87ec1440dcc1d25938795925237ca5194ee6551e"}},{"branch":"8.11","label":"v8.11.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Davis Plumlee <56367316+dplumlee@users.noreply.github.com>	2023-11-23 09:19:04 -07:00
Kibana Machine	ab8d894a38	[8.11] [Serverless][Security Solution][Endpoint] Remove use of hooks to check access to.lists-* for endpoint exceptions access (#171412) (#171794) ... # Backport This will backport the following commits from `main` to `8.11`: - [[Serverless][Security Solution][Endpoint] Remove use of hooks to check access to`.lists-*` for endpoint exceptions access (#171412)](https://github.com/elastic/kibana/pull/171412) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Ash","email":"1849116+ashokaditya@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-11-22T19:10:50Z","message":"[Serverless][Security Solution][Endpoint] Remove use of hooks to check access to`.lists-*` for endpoint exceptions access (#171412)\n\n## Summary\r\n\r\nInstead of using `useListsConfig` this PR uses `useListPrivileges` to\r\nverify access to `.lists-*` index pattern.\r\n\r\nfollow up of elastic/kibana/pull/165613\r\nrelated elastic/kibana/pull/170671 (closed in favour of this)\r\nfixes elastic/kibana/issues/169268\r\n\r\n### Checklist\r\n\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\n---------\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"8c3322ed44ccfbc4e91e0e9ef31f77b79c549cb8","branchLabelMapping":{"^v8.12.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","OLM Sprint","v8.11.0","v8.12.0","v8.11.1"],"number":171412,"url":"https://github.com/elastic/kibana/pull/171412","mergeCommit":{"message":"[Serverless][Security Solution][Endpoint] Remove use of hooks to check access to`.lists-*` for endpoint exceptions access (#171412)\n\n## Summary\r\n\r\nInstead of using `useListsConfig` this PR uses `useListPrivileges` to\r\nverify access to `.lists-*` index pattern.\r\n\r\nfollow up of elastic/kibana/pull/165613\r\nrelated elastic/kibana/pull/170671 (closed in favour of this)\r\nfixes elastic/kibana/issues/169268\r\n\r\n### Checklist\r\n\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\n---------\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"8c3322ed44ccfbc4e91e0e9ef31f77b79c549cb8"}},"sourceBranch":"main","suggestedTargetBranches":["8.11"],"targetPullRequestStates":[{"branch":"8.11","label":"v8.11.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.12.0","labelRegex":"^v8.12.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/171412","number":171412,"mergeCommit":{"message":"[Serverless][Security Solution][Endpoint] Remove use of hooks to check access to`.lists-*` for endpoint exceptions access (#171412)\n\n## Summary\r\n\r\nInstead of using `useListsConfig` this PR uses `useListPrivileges` to\r\nverify access to `.lists-*` index pattern.\r\n\r\nfollow up of elastic/kibana/pull/165613\r\nrelated elastic/kibana/pull/170671 (closed in favour of this)\r\nfixes elastic/kibana/issues/169268\r\n\r\n### Checklist\r\n\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\n---------\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"8c3322ed44ccfbc4e91e0e9ef31f77b79c549cb8"}}]}] BACKPORT--> Co-authored-by: Ash <1849116+ashokaditya@users.noreply.github.com>	2023-11-23 08:34:19 -07:00
Julia Bardi	eec5208619	[8.11][Fleet] only add time_series_metric if tsdb enabled (#171712) (#171828) ... Backport https://github.com/elastic/kibana/pull/171712 to 8.11	2023-11-23 16:32:48 +01:00
Lisa Cawley	7f1b79c580	[8.11] [OAS] Migrate alerting APIs to v3.1.0 (#171587) (#171799) ... # Backport This will backport the following commits from `main` to `8.11`: - [[OAS] Migrate alerting APIs to v3.1.0 (#171587)](https://github.com/elastic/kibana/pull/171587) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Lisa Cawley","email":"lcawley@elastic.co"},"sourceCommit":{"committedDate":"2023-11-22T20:21:07Z","message":"[OAS] Migrate alerting APIs to v3.1.0 (#171587)","sha":"a50cad6f78caa607d210cd90e12ab11bc18902bd","branchLabelMapping":{"^v8.12.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Alerting","release_note:skip","Team:ResponseOps","docs","v8.12.0","v8.11.2"],"number":171587,"url":"https://github.com/elastic/kibana/pull/171587","mergeCommit":{"message":"[OAS] Migrate alerting APIs to v3.1.0 (#171587)","sha":"a50cad6f78caa607d210cd90e12ab11bc18902bd"}},"sourceBranch":"main","suggestedTargetBranches":["8.11"],"targetPullRequestStates":[{"branch":"main","label":"v8.12.0","labelRegex":"^v8.12.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/171587","number":171587,"mergeCommit":{"message":"[OAS] Migrate alerting APIs to v3.1.0 (#171587)","sha":"a50cad6f78caa607d210cd90e12ab11bc18902bd"}},{"branch":"8.11","label":"v8.11.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->	2023-11-23 09:12:31 -05:00
Tiago Costa	4951fe268a	skip flaky suite (#149777)	2023-11-23 01:41:21 +00:00
Kibana Machine	79a4a3cfdc	[8.11] [Synthetics] Refactor supress API Key error (#171114) (#171766) ... # Backport This will backport the following commits from `main` to `8.11`: - [[Synthetics] Refactor supress API Key error (#171114)](https://github.com/elastic/kibana/pull/171114) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Shahzad","email":"shahzad31comp@gmail.com"},"sourceCommit":{"committedDate":"2023-11-22T16:03:35Z","message":"[Synthetics] Refactor supress API Key error (#171114)","sha":"d5fc9b0314cc5a56fac46668728284a91ea9ee6a","branchLabelMapping":{"^v8.12.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:uptime","release_note:skip","backport:prev-minor","v8.12.0"],"number":171114,"url":"https://github.com/elastic/kibana/pull/171114","mergeCommit":{"message":"[Synthetics] Refactor supress API Key error (#171114)","sha":"d5fc9b0314cc5a56fac46668728284a91ea9ee6a"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.12.0","labelRegex":"^v8.12.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/171114","number":171114,"mergeCommit":{"message":"[Synthetics] Refactor supress API Key error (#171114)","sha":"d5fc9b0314cc5a56fac46668728284a91ea9ee6a"}}]}] BACKPORT--> Co-authored-by: Shahzad <shahzad31comp@gmail.com>	2023-11-22 12:03:28 -07:00
Kibana Machine	416cc7f8c0	[8.11] Adding user profiles tests for regular and serverless (#171554) (#171758) ... # Backport This will backport the following commits from `main` to `8.11`: - [Adding user profiles tests for regular and serverless (#171554)](https://github.com/elastic/kibana/pull/171554) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Kurt","email":"kc13greiner@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-11-22T15:43:03Z","message":"Adding user profiles tests for regular and serverless (#171554)\n\n## Summary\r\n\r\nAdding functional tests for User Profiles and Dark Mode\r\n\r\n\r\n## Flaky Test Runner for new tests\r\n\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/4034\r\n🟢","sha":"66019dfe057734f4f45035e7df101822e1bcdcc5","branchLabelMapping":{"^v8.12.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","v8.12.0"],"number":171554,"url":"https://github.com/elastic/kibana/pull/171554","mergeCommit":{"message":"Adding user profiles tests for regular and serverless (#171554)\n\n## Summary\r\n\r\nAdding functional tests for User Profiles and Dark Mode\r\n\r\n\r\n## Flaky Test Runner for new tests\r\n\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/4034\r\n🟢","sha":"66019dfe057734f4f45035e7df101822e1bcdcc5"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.12.0","labelRegex":"^v8.12.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/171554","number":171554,"mergeCommit":{"message":"Adding user profiles tests for regular and serverless (#171554)\n\n## Summary\r\n\r\nAdding functional tests for User Profiles and Dark Mode\r\n\r\n\r\n## Flaky Test Runner for new tests\r\n\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/4034\r\n🟢","sha":"66019dfe057734f4f45035e7df101822e1bcdcc5"}}]}] BACKPORT--> Co-authored-by: Kurt <kc13greiner@users.noreply.github.com>	2023-11-22 12:33:52 -05:00
Kibana Machine	36b40f0963	[8.11] [security_solution] Fix junit_transformer (#171669) (#171693) ... # Backport This will backport the following commits from `main` to `8.11`: - [[security_solution] Fix junit_transformer (#171669)](https://github.com/elastic/kibana/pull/171669) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Patryk Kopyciński","email":"contact@patrykkopycinski.com"},"sourceCommit":{"committedDate":"2023-11-21T21:50:37Z","message":"[security_solution] Fix junit_transformer (#171669)\n\n## Summary\r\n\r\nCurrently, Cypress is writing junit XML files that we are trying to map\r\nto the expected CI format, but if the job fails the broken files are\r\nstill being uploaded and passed to the Flaky Test Reporter which causes\r\nit to fail.\r\n\r\nSo the solution is to just delete the broken files before they are sent\r\nto the Flaky Tests Reporter\r\n\r\nCo-authored-by: Tiago Costa <tiago.costa@elastic.co>","sha":"043f0501874108eeb133d59ecded2d1e7a871bd6","branchLabelMapping":{"^v8.12.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Defend Workflows","backport:prev-minor","v8.12.0","v8.11.2"],"number":171669,"url":"https://github.com/elastic/kibana/pull/171669","mergeCommit":{"message":"[security_solution] Fix junit_transformer (#171669)\n\n## Summary\r\n\r\nCurrently, Cypress is writing junit XML files that we are trying to map\r\nto the expected CI format, but if the job fails the broken files are\r\nstill being uploaded and passed to the Flaky Test Reporter which causes\r\nit to fail.\r\n\r\nSo the solution is to just delete the broken files before they are sent\r\nto the Flaky Tests Reporter\r\n\r\nCo-authored-by: Tiago Costa <tiago.costa@elastic.co>","sha":"043f0501874108eeb133d59ecded2d1e7a871bd6"}},"sourceBranch":"main","suggestedTargetBranches":["8.11"],"targetPullRequestStates":[{"branch":"main","label":"v8.12.0","labelRegex":"^v8.12.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/171669","number":171669,"mergeCommit":{"message":"[security_solution] Fix junit_transformer (#171669)\n\n## Summary\r\n\r\nCurrently, Cypress is writing junit XML files that we are trying to map\r\nto the expected CI format, but if the job fails the broken files are\r\nstill being uploaded and passed to the Flaky Test Reporter which causes\r\nit to fail.\r\n\r\nSo the solution is to just delete the broken files before they are sent\r\nto the Flaky Tests Reporter\r\n\r\nCo-authored-by: Tiago Costa <tiago.costa@elastic.co>","sha":"043f0501874108eeb133d59ecded2d1e7a871bd6"}},{"branch":"8.11","label":"v8.11.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Patryk Kopyciński <contact@patrykkopycinski.com>	2023-11-21 22:11:51 +00:00
Kibana Machine	c25c3ab106	[8.11] FullStory: use debounce before updating Page Vars (#171450) (#171636) ... # Backport This will backport the following commits from `main` to `8.11`: - [FullStory: use debounce before updating Page Vars (#171450)](https://github.com/elastic/kibana/pull/171450) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Alejandro Fernández Haro","email":"alejandro.haro@elastic.co"},"sourceCommit":{"committedDate":"2023-11-21T13:46:13Z","message":"FullStory: use debounce before updating Page Vars (#171450)","sha":"55aebfdd2e2576c4d78b2e409825ba11652125ca","branchLabelMapping":{"^v8.12.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","Feature:Telemetry","release_note:skip","telemetry","backport:prev-minor","v8.12.0"],"number":171450,"url":"https://github.com/elastic/kibana/pull/171450","mergeCommit":{"message":"FullStory: use debounce before updating Page Vars (#171450)","sha":"55aebfdd2e2576c4d78b2e409825ba11652125ca"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.12.0","labelRegex":"^v8.12.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/171450","number":171450,"mergeCommit":{"message":"FullStory: use debounce before updating Page Vars (#171450)","sha":"55aebfdd2e2576c4d78b2e409825ba11652125ca"}}]}] BACKPORT--> Co-authored-by: Alejandro Fernández Haro <alejandro.haro@elastic.co>	2023-11-21 08:27:51 -07:00
Kibana Machine	a75cef46af	[8.11] [EDR Workflows] Fix Osquery cypress 11 (#171497) (#171564) ... # Backport This will backport the following commits from `main` to `8.11`: - [[EDR Workflows] Fix Osquery cypress 11 (#171497)](https://github.com/elastic/kibana/pull/171497) <!--- 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":"2023-11-20T17:02:20Z","message":"[EDR Workflows] Fix Osquery cypress 11 (#171497)","sha":"d412e5789769a415916ee6cbef46e0931f2e222e","branchLabelMapping":{"^v8.12.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["chore","release_note:skip","Team:Defend Workflows","Feature:Osquery","v8.12.0","v8.11.2"],"number":171497,"url":"https://github.com/elastic/kibana/pull/171497","mergeCommit":{"message":"[EDR Workflows] Fix Osquery cypress 11 (#171497)","sha":"d412e5789769a415916ee6cbef46e0931f2e222e"}},"sourceBranch":"main","suggestedTargetBranches":["8.11"],"targetPullRequestStates":[{"branch":"main","label":"v8.12.0","labelRegex":"^v8.12.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/171497","number":171497,"mergeCommit":{"message":"[EDR Workflows] Fix Osquery cypress 11 (#171497)","sha":"d412e5789769a415916ee6cbef46e0931f2e222e"}},{"branch":"8.11","label":"v8.11.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Tomasz Ciecierski <tomasz.ciecierski@elastic.co>	2023-11-21 03:43:49 -07:00
Kibana Machine	dbf07605ac	[8.11] Always throw error objects - never strings (#171498) (#171547) ... # Backport This will backport the following commits from `main` to `8.11`: - [Always throw error objects - never strings (#171498)](https://github.com/elastic/kibana/pull/171498) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Thomas Watson","email":"watson@elastic.co"},"sourceCommit":{"committedDate":"2023-11-20T14:23:16Z","message":"Always throw error objects - never strings (#171498)","sha":"4f9094caf3cc4781137b7cfccbe2e1858f4f39c0","branchLabelMapping":{"^v8.12.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:all-open","v8.12.0"],"number":171498,"url":"https://github.com/elastic/kibana/pull/171498","mergeCommit":{"message":"Always throw error objects - never strings (#171498)","sha":"4f9094caf3cc4781137b7cfccbe2e1858f4f39c0"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.12.0","labelRegex":"^v8.12.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/171498","number":171498,"mergeCommit":{"message":"Always throw error objects - never strings (#171498)","sha":"4f9094caf3cc4781137b7cfccbe2e1858f4f39c0"}}]}] BACKPORT--> Co-authored-by: Thomas Watson <watson@elastic.co>	2023-11-20 08:59:59 -07:00
Kibana Machine	3952ce8f28	[8.11] Fix custom branding for users without "Saved Object Management" privilege (#171308) (#171530) ... # Backport This will backport the following commits from `main` to `8.11`: - [Fix custom branding for users without "Saved Object Management" privilege (#171308)](https://github.com/elastic/kibana/pull/171308) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Anton Dosov","email":"anton.dosov@elastic.co"},"sourceCommit":{"committedDate":"2023-11-20T12:36:21Z","message":"Fix custom branding for users without \"Saved Object Management\" privilege (#171308)\n\n## Summary\r\n\r\nfix https://github.com/elastic/kibana/issues/163842\r\n\r\nCurrently, Saved Objects Management Kibana privilege ( either read or\r\nall) is needed in order for a user to see custom branding. Without it,\r\nusers with custom roles see the default branding after logging in.\r\n\r\nCustom branding is stored in the new \"global\" advanced settings\r\n(\"config-global\" saved object). Only users with Saved Objects Management\r\nprivilege had access to it. This PR adds \"config-global\" to the list of\r\nautomatically applied privileges similar to \"config\".","sha":"385fe054ffc3c7c85d0a887ff106aae6b1ec6d75","branchLabelMapping":{"^v8.12.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:SharedUX","backport:prev-minor","v8.12.0"],"number":171308,"url":"https://github.com/elastic/kibana/pull/171308","mergeCommit":{"message":"Fix custom branding for users without \"Saved Object Management\" privilege (#171308)\n\n## Summary\r\n\r\nfix https://github.com/elastic/kibana/issues/163842\r\n\r\nCurrently, Saved Objects Management Kibana privilege ( either read or\r\nall) is needed in order for a user to see custom branding. Without it,\r\nusers with custom roles see the default branding after logging in.\r\n\r\nCustom branding is stored in the new \"global\" advanced settings\r\n(\"config-global\" saved object). Only users with Saved Objects Management\r\nprivilege had access to it. This PR adds \"config-global\" to the list of\r\nautomatically applied privileges similar to \"config\".","sha":"385fe054ffc3c7c85d0a887ff106aae6b1ec6d75"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.12.0","labelRegex":"^v8.12.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/171308","number":171308,"mergeCommit":{"message":"Fix custom branding for users without \"Saved Object Management\" privilege (#171308)\n\n## Summary\r\n\r\nfix https://github.com/elastic/kibana/issues/163842\r\n\r\nCurrently, Saved Objects Management Kibana privilege ( either read or\r\nall) is needed in order for a user to see custom branding. Without it,\r\nusers with custom roles see the default branding after logging in.\r\n\r\nCustom branding is stored in the new \"global\" advanced settings\r\n(\"config-global\" saved object). Only users with Saved Objects Management\r\nprivilege had access to it. This PR adds \"config-global\" to the list of\r\nautomatically applied privileges similar to \"config\".","sha":"385fe054ffc3c7c85d0a887ff106aae6b1ec6d75"}}]}] BACKPORT--> Co-authored-by: Anton Dosov <anton.dosov@elastic.co>	2023-11-20 08:12:25 -07:00
Konrad Szwarc	0e2d46d2cf	[8.11] [EDR Workflows] Protection updates copy change (#171318) (#171499) ... # Backport This will backport the following commits from `main` to `8.11`: - [[EDR Workflows] Protection updates copy change (#171318)](https://github.com/elastic/kibana/pull/171318) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Konrad Szwarc","email":"konrad.szwarc@elastic.co"},"sourceCommit":{"committedDate":"2023-11-15T19:07:44Z","message":"[EDR Workflows] Protection updates copy change (#171318)\n\nChanged copy as per request.\r\n\r\nCloses https://github.com/elastic/security-team/issues/7968\r\n\r\n","sha":"65ebb69a9fffffd62689ef4536b939b3726e927e","branchLabelMapping":{"^v8.12.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:Defend Workflows","v8.12.0","v8.11.2"],"number":171318,"url":"https://github.com/elastic/kibana/pull/171318","mergeCommit":{"message":"[EDR Workflows] Protection updates copy change (#171318)\n\nChanged copy as per request.\r\n\r\nCloses https://github.com/elastic/security-team/issues/7968\r\n\r\n","sha":"65ebb69a9fffffd62689ef4536b939b3726e927e"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.12.0","labelRegex":"^v8.12.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/171318","number":171318,"mergeCommit":{"message":"[EDR Workflows] Protection updates copy change (#171318)\n\nChanged copy as per request.\r\n\r\nCloses https://github.com/elastic/security-team/issues/7968\r\n\r\n","sha":"65ebb69a9fffffd62689ef4536b939b3726e927e"}},{"branch":"8.11","label":"v8.11.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/171347","number":171347,"state":"OPEN"}]}] BACKPORT--> --------- Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>	2023-11-20 09:22:35 -05:00
Kibana Machine	f982ca8292	[8.11] [Security Solution] [Elastic AI Assistant] Fix Send to Timeline ESQL action changing the ESQL bar to KQL bar (#170542) (#171471) ... # Backport This will backport the following commits from `main` to `8.11`: - [[Security Solution] [Elastic AI Assistant] Fix Send to Timeline ESQL action changing the ESQL bar to KQL bar (#170542)](https://github.com/elastic/kibana/pull/170542) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Garrett Spong","email":"spong@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-11-17T01:13:14Z","message":"[Security Solution] [Elastic AI Assistant] Fix Send to Timeline ESQL action changing the ESQL bar to KQL bar (#170542)\n\n## Summary\r\n\r\nIn https://github.com/elastic/kibana/pull/169478, the `Send to Timeline`\r\naction was fixed for `ES|QL` codeblocks, however while the `ES|QL`\r\ntimeline tab was being selected, and the query string was being set\r\ncorrectly, the ESQL bar would be swapped out for the KQL bar. In the\r\ngifs below, note the right two action buttons present in the query bar.\r\n\r\nThere is one remaining bug where refreshing the page clears the ESQL\r\nquery and set the default query. @logeekal is currently investigating a\r\nfix for this issue and will push to this branch once available.\r\n\r\n#### Before\r\n<p align=\"center\">\r\n<img width=\"500\"\r\nsrc=\"fdc3b2a0-5b4b-4584-b304-c4d24de1917c\"\r\n/>\r\n</p> \r\n\r\n#### After\r\n<p align=\"center\">\r\n<img width=\"500\"\r\nsrc=\"d217b95c-2d1c-4474-ac98-180e07a86669\"\r\n/>\r\n</p> \r\n\r\n\r\n## Test instructions\r\n\r\nEither request the assistant to generate an ESQL query or just paste\r\nthis codeblock into the conversation to test the action directly from\r\nthe user message. Be sure to declare the codeblock language as `esql` or\r\ninclude one of the [string match\r\npatterns](https://github.com/elastic/kibana/pull/169478/files#diff-f70f0b96568e024e53bfbb62adcca72051f0a2e824d4ab22664eed0e149be248R38)\r\nabove the code block so the action can be recognized.\r\n\r\n\r\n````\r\nBelow is an `Elasticsearch Query Language` query:\r\n\r\n```esql\r\nFROM logs-endpoint*\r\n| WHERE event.category == \\\"process\\\"\r\n| STATS proc_count = COUNT(process.name) BY host.name\r\n| KEEP host.name, proc_count\r\n```\r\n````\r\n\r\n\r\nThen verify that the query bar is still the ESQL query bar which has the\r\n`Expand` and `ESQL Reference` buttons to the far right.\r\n\r\n---------\r\n\r\nCo-authored-by: Jatin Kathuria <jatin.kathuria@elastic.co>","sha":"52fdd7f46fc6dd56d062a1ba55dd5caeae47c8f9","branchLabelMapping":{"^v8.12.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","Team: SecuritySolution","backport:prev-minor","Feature:Elastic AI Assistant","v8.12.0","v8.11.2"],"number":170542,"url":"https://github.com/elastic/kibana/pull/170542","mergeCommit":{"message":"[Security Solution] [Elastic AI Assistant] Fix Send to Timeline ESQL action changing the ESQL bar to KQL bar (#170542)\n\n## Summary\r\n\r\nIn https://github.com/elastic/kibana/pull/169478, the `Send to Timeline`\r\naction was fixed for `ES|QL` codeblocks, however while the `ES|QL`\r\ntimeline tab was being selected, and the query string was being set\r\ncorrectly, the ESQL bar would be swapped out for the KQL bar. In the\r\ngifs below, note the right two action buttons present in the query bar.\r\n\r\nThere is one remaining bug where refreshing the page clears the ESQL\r\nquery and set the default query. @logeekal is currently investigating a\r\nfix for this issue and will push to this branch once available.\r\n\r\n#### Before\r\n<p align=\"center\">\r\n<img width=\"500\"\r\nsrc=\"fdc3b2a0-5b4b-4584-b304-c4d24de1917c\"\r\n/>\r\n</p> \r\n\r\n#### After\r\n<p align=\"center\">\r\n<img width=\"500\"\r\nsrc=\"d217b95c-2d1c-4474-ac98-180e07a86669\"\r\n/>\r\n</p> \r\n\r\n\r\n## Test instructions\r\n\r\nEither request the assistant to generate an ESQL query or just paste\r\nthis codeblock into the conversation to test the action directly from\r\nthe user message. Be sure to declare the codeblock language as `esql` or\r\ninclude one of the [string match\r\npatterns](https://github.com/elastic/kibana/pull/169478/files#diff-f70f0b96568e024e53bfbb62adcca72051f0a2e824d4ab22664eed0e149be248R38)\r\nabove the code block so the action can be recognized.\r\n\r\n\r\n````\r\nBelow is an `Elasticsearch Query Language` query:\r\n\r\n```esql\r\nFROM logs-endpoint*\r\n| WHERE event.category == \\\"process\\\"\r\n| STATS proc_count = COUNT(process.name) BY host.name\r\n| KEEP host.name, proc_count\r\n```\r\n````\r\n\r\n\r\nThen verify that the query bar is still the ESQL query bar which has the\r\n`Expand` and `ESQL Reference` buttons to the far right.\r\n\r\n---------\r\n\r\nCo-authored-by: Jatin Kathuria <jatin.kathuria@elastic.co>","sha":"52fdd7f46fc6dd56d062a1ba55dd5caeae47c8f9"}},"sourceBranch":"main","suggestedTargetBranches":["8.11"],"targetPullRequestStates":[{"branch":"main","label":"v8.12.0","labelRegex":"^v8.12.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/170542","number":170542,"mergeCommit":{"message":"[Security Solution] [Elastic AI Assistant] Fix Send to Timeline ESQL action changing the ESQL bar to KQL bar (#170542)\n\n## Summary\r\n\r\nIn https://github.com/elastic/kibana/pull/169478, the `Send to Timeline`\r\naction was fixed for `ES|QL` codeblocks, however while the `ES|QL`\r\ntimeline tab was being selected, and the query string was being set\r\ncorrectly, the ESQL bar would be swapped out for the KQL bar. In the\r\ngifs below, note the right two action buttons present in the query bar.\r\n\r\nThere is one remaining bug where refreshing the page clears the ESQL\r\nquery and set the default query. @logeekal is currently investigating a\r\nfix for this issue and will push to this branch once available.\r\n\r\n#### Before\r\n<p align=\"center\">\r\n<img width=\"500\"\r\nsrc=\"fdc3b2a0-5b4b-4584-b304-c4d24de1917c\"\r\n/>\r\n</p> \r\n\r\n#### After\r\n<p align=\"center\">\r\n<img width=\"500\"\r\nsrc=\"d217b95c-2d1c-4474-ac98-180e07a86669\"\r\n/>\r\n</p> \r\n\r\n\r\n## Test instructions\r\n\r\nEither request the assistant to generate an ESQL query or just paste\r\nthis codeblock into the conversation to test the action directly from\r\nthe user message. Be sure to declare the codeblock language as `esql` or\r\ninclude one of the [string match\r\npatterns](https://github.com/elastic/kibana/pull/169478/files#diff-f70f0b96568e024e53bfbb62adcca72051f0a2e824d4ab22664eed0e149be248R38)\r\nabove the code block so the action can be recognized.\r\n\r\n\r\n````\r\nBelow is an `Elasticsearch Query Language` query:\r\n\r\n```esql\r\nFROM logs-endpoint*\r\n| WHERE event.category == \\\"process\\\"\r\n| STATS proc_count = COUNT(process.name) BY host.name\r\n| KEEP host.name, proc_count\r\n```\r\n````\r\n\r\n\r\nThen verify that the query bar is still the ESQL query bar which has the\r\n`Expand` and `ESQL Reference` buttons to the far right.\r\n\r\n---------\r\n\r\nCo-authored-by: Jatin Kathuria <jatin.kathuria@elastic.co>","sha":"52fdd7f46fc6dd56d062a1ba55dd5caeae47c8f9"}},{"branch":"8.11","label":"v8.11.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Garrett Spong <spong@users.noreply.github.com> Co-authored-by: Jatin Kathuria <jatin.kathuria@elastic.co>	2023-11-18 10:55:54 -07:00
Kibana Machine	7d33d5a8e6	[8.11] [fix] Using max_result_window to set up MVT size request leads to not showing all results (#171344) (#171440) ... # Backport This will backport the following commits from `main` to `8.11`: - [[fix] Using max_result_window to set up MVT size request leads to not showing all results (#171344)](https://github.com/elastic/kibana/pull/171344) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Nathan Reese","email":"reese.nathan@elastic.co"},"sourceCommit":{"committedDate":"2023-11-16T19:11:13Z","message":"[fix] Using max_result_window to set up MVT size request leads to not showing all results (#171344)\n\nCloses https://github.com/elastic/kibana/issues/170272\r\n\r\nThe cause of the problem is that Maps is not setting\r\n[_mvt](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-vector-tile-api.html)\r\n`size` parameter.\r\n\r\nLets illustrate the problem with an example.\r\n* index.max_result_window is set to 20,000.\r\n* There are 15,000 hits matching the query for the tile, but because\r\n`size` is not provided, the tile returns the default size value of\r\n10,000 hits.\r\n* Tile request sets `track_total_hits` to 20,001. Tile meta returns\r\n`\"hits.total.relation\": \"eq\"` and `\"hits.total.value\": 15000`\r\nproperties, indicating that all possible hits are returned in the tile.\r\n* Maps UI does not display \"incomplete results\" even though 5000 hits\r\nare not contained in the tile.\r\n* This happens because `hits.total` properties from tile meta is used to\r\nindicate \"incomplete results\" and the returned value indicates that all\r\nresults are contained in the tile. We know this is not true because the\r\ntile actually only returned 10,000 hits and not all 15,000 matching\r\nhits. Thus, without setting `size`, the tile is not returning all of the\r\nhits indicated by `track_total_hits`.\r\n\r\n### test instructions\r\n1. install web logs sample data set\r\n2. In dev tools, run the following\r\n ```\r\n POST kibana_sample_data_logs/_doc/\r\n {\r\n \"geo\": {\r\n \"coordinates\": \"59,-106.5\"\r\n },\r\n \"@timestamp\": \"2023-08-01\"\r\n }\r\n\r\n PUT /kibana_sample_data_logs/_settings\r\n {\r\n \"index\" : {\r\n \"max_result_window\" : 20000\r\n }\r\n }\r\n ```\r\n3. Create new map\r\n4. Set time range to `1 year ago to 1 year from now` to display all web\r\nlogs data\r\n5. add documents layer. Verify point circled in image is displayed.\r\nWithout changes, this point would not be returned in the tile because\r\nthe tile would only return the first 10000 matches.\r\n<img width=\"500\" alt=\"Screenshot 2023-11-15 at 11 31 25 AM\"\r\nsrc=\"2249d571-24c4-41ad-975e-d44ee6d246ce\">","sha":"95a8d6a18f4f6e93ede4efdaaca880fc94378fb1","branchLabelMapping":{"^v8.12.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Presentation","Feature:Maps","v8.12.0","v8.11.2"],"number":171344,"url":"https://github.com/elastic/kibana/pull/171344","mergeCommit":{"message":"[fix] Using max_result_window to set up MVT size request leads to not showing all results (#171344)\n\nCloses https://github.com/elastic/kibana/issues/170272\r\n\r\nThe cause of the problem is that Maps is not setting\r\n[_mvt](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-vector-tile-api.html)\r\n`size` parameter.\r\n\r\nLets illustrate the problem with an example.\r\n* index.max_result_window is set to 20,000.\r\n* There are 15,000 hits matching the query for the tile, but because\r\n`size` is not provided, the tile returns the default size value of\r\n10,000 hits.\r\n* Tile request sets `track_total_hits` to 20,001. Tile meta returns\r\n`\"hits.total.relation\": \"eq\"` and `\"hits.total.value\": 15000`\r\nproperties, indicating that all possible hits are returned in the tile.\r\n* Maps UI does not display \"incomplete results\" even though 5000 hits\r\nare not contained in the tile.\r\n* This happens because `hits.total` properties from tile meta is used to\r\nindicate \"incomplete results\" and the returned value indicates that all\r\nresults are contained in the tile. We know this is not true because the\r\ntile actually only returned 10,000 hits and not all 15,000 matching\r\nhits. Thus, without setting `size`, the tile is not returning all of the\r\nhits indicated by `track_total_hits`.\r\n\r\n### test instructions\r\n1. install web logs sample data set\r\n2. In dev tools, run the following\r\n ```\r\n POST kibana_sample_data_logs/_doc/\r\n {\r\n \"geo\": {\r\n \"coordinates\": \"59,-106.5\"\r\n },\r\n \"@timestamp\": \"2023-08-01\"\r\n }\r\n\r\n PUT /kibana_sample_data_logs/_settings\r\n {\r\n \"index\" : {\r\n \"max_result_window\" : 20000\r\n }\r\n }\r\n ```\r\n3. Create new map\r\n4. Set time range to `1 year ago to 1 year from now` to display all web\r\nlogs data\r\n5. add documents layer. Verify point circled in image is displayed.\r\nWithout changes, this point would not be returned in the tile because\r\nthe tile would only return the first 10000 matches.\r\n<img width=\"500\" alt=\"Screenshot 2023-11-15 at 11 31 25 AM\"\r\nsrc=\"2249d571-24c4-41ad-975e-d44ee6d246ce\">","sha":"95a8d6a18f4f6e93ede4efdaaca880fc94378fb1"}},"sourceBranch":"main","suggestedTargetBranches":["8.11"],"targetPullRequestStates":[{"branch":"main","label":"v8.12.0","labelRegex":"^v8.12.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/171344","number":171344,"mergeCommit":{"message":"[fix] Using max_result_window to set up MVT size request leads to not showing all results (#171344)\n\nCloses https://github.com/elastic/kibana/issues/170272\r\n\r\nThe cause of the problem is that Maps is not setting\r\n[_mvt](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-vector-tile-api.html)\r\n`size` parameter.\r\n\r\nLets illustrate the problem with an example.\r\n* index.max_result_window is set to 20,000.\r\n* There are 15,000 hits matching the query for the tile, but because\r\n`size` is not provided, the tile returns the default size value of\r\n10,000 hits.\r\n* Tile request sets `track_total_hits` to 20,001. Tile meta returns\r\n`\"hits.total.relation\": \"eq\"` and `\"hits.total.value\": 15000`\r\nproperties, indicating that all possible hits are returned in the tile.\r\n* Maps UI does not display \"incomplete results\" even though 5000 hits\r\nare not contained in the tile.\r\n* This happens because `hits.total` properties from tile meta is used to\r\nindicate \"incomplete results\" and the returned value indicates that all\r\nresults are contained in the tile. We know this is not true because the\r\ntile actually only returned 10,000 hits and not all 15,000 matching\r\nhits. Thus, without setting `size`, the tile is not returning all of the\r\nhits indicated by `track_total_hits`.\r\n\r\n### test instructions\r\n1. install web logs sample data set\r\n2. In dev tools, run the following\r\n ```\r\n POST kibana_sample_data_logs/_doc/\r\n {\r\n \"geo\": {\r\n \"coordinates\": \"59,-106.5\"\r\n },\r\n \"@timestamp\": \"2023-08-01\"\r\n }\r\n\r\n PUT /kibana_sample_data_logs/_settings\r\n {\r\n \"index\" : {\r\n \"max_result_window\" : 20000\r\n }\r\n }\r\n ```\r\n3. Create new map\r\n4. Set time range to `1 year ago to 1 year from now` to display all web\r\nlogs data\r\n5. add documents layer. Verify point circled in image is displayed.\r\nWithout changes, this point would not be returned in the tile because\r\nthe tile would only return the first 10000 matches.\r\n<img width=\"500\" alt=\"Screenshot 2023-11-15 at 11 31 25 AM\"\r\nsrc=\"2249d571-24c4-41ad-975e-d44ee6d246ce\">","sha":"95a8d6a18f4f6e93ede4efdaaca880fc94378fb1"}},{"branch":"8.11","label":"v8.11.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Nathan Reese <reese.nathan@elastic.co>	2023-11-16 13:20:14 -07:00
Jiawei Wu	46e0cda150	[8.11] [RAM][Bug] Fix bug preventing filters from being added to conditional actions (#171048) (#171362) ... # Backport This will backport the following commits from `main` to `8.11`: - [[RAM][Bug] Fix bug preventing filters from being added to conditional actions (#171048)](https://github.com/elastic/kibana/pull/171048) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Jiawei Wu","email":"74562234+JiaweiWu@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-11-15T19:38:50Z","message":"[RAM][Bug] Fix bug preventing filters from being added to conditional actions (#171048)\n\n## Summary\r\nResolves: https://github.com/elastic/kibana/issues/171036\r\n\r\nFixes a bug where the schema name for the conditional action filter\r\n`$state` was incorrectly name. This prevented the user from adding\r\nfilters to conditional actions as the schema validation would reject the\r\nrequest.\r\n\r\n### To verify the fix:\r\n\r\n1. Create a rule\r\n2. Add a conditional action\r\n3. Assert that filters can be added to the rule\r\n4. Rule is saved\r\n5. Repeat 1 - 4 but this time, update the rule. \r\n\r\n### Checklist\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"fbb232815b85961ac09b6abbe369eb7b3760752d","branchLabelMapping":{"^v8.12.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:ResponseOps","Feature:Alerting/RulesManagement","v8.12.0","v8.11.1","v8.10.5"],"number":171048,"url":"https://github.com/elastic/kibana/pull/171048","mergeCommit":{"message":"[RAM][Bug] Fix bug preventing filters from being added to conditional actions (#171048)\n\n## Summary\r\nResolves: https://github.com/elastic/kibana/issues/171036\r\n\r\nFixes a bug where the schema name for the conditional action filter\r\n`$state` was incorrectly name. This prevented the user from adding\r\nfilters to conditional actions as the schema validation would reject the\r\nrequest.\r\n\r\n### To verify the fix:\r\n\r\n1. Create a rule\r\n2. Add a conditional action\r\n3. Assert that filters can be added to the rule\r\n4. Rule is saved\r\n5. Repeat 1 - 4 but this time, update the rule. \r\n\r\n### Checklist\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"fbb232815b85961ac09b6abbe369eb7b3760752d"}},"sourceBranch":"main","suggestedTargetBranches":["8.11","8.10"],"targetPullRequestStates":[{"branch":"main","label":"v8.12.0","labelRegex":"^v8.12.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/171048","number":171048,"mergeCommit":{"message":"[RAM][Bug] Fix bug preventing filters from being added to conditional actions (#171048)\n\n## Summary\r\nResolves: https://github.com/elastic/kibana/issues/171036\r\n\r\nFixes a bug where the schema name for the conditional action filter\r\n`$state` was incorrectly name. This prevented the user from adding\r\nfilters to conditional actions as the schema validation would reject the\r\nrequest.\r\n\r\n### To verify the fix:\r\n\r\n1. Create a rule\r\n2. Add a conditional action\r\n3. Assert that filters can be added to the rule\r\n4. Rule is saved\r\n5. Repeat 1 - 4 but this time, update the rule. \r\n\r\n### Checklist\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"fbb232815b85961ac09b6abbe369eb7b3760752d"}},{"branch":"8.11","label":"v8.11.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.10","label":"v8.10.5","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->	2023-11-16 08:34:39 -05:00
Kibana Machine	09f036502f	[8.11] [EDR Workflows] Osquery Package Policy test fix (#171305) (#171325) ... # Backport This will backport the following commits from `main` to `8.11`: - [[EDR Workflows] Osquery Package Policy test fix (#171305)](https://github.com/elastic/kibana/pull/171305) <!--- 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":"2023-11-15T16:13:19Z","message":"[EDR Workflows] Osquery Package Policy test fix (#171305)","sha":"1ecb6ba073c79f80f03fc285335099b2ce714e52","branchLabelMapping":{"^v8.12.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["chore","release_note:skip","Team:Defend Workflows","v8.12.0","v8.11.2"],"number":171305,"url":"https://github.com/elastic/kibana/pull/171305","mergeCommit":{"message":"[EDR Workflows] Osquery Package Policy test fix (#171305)","sha":"1ecb6ba073c79f80f03fc285335099b2ce714e52"}},"sourceBranch":"main","suggestedTargetBranches":["8.11"],"targetPullRequestStates":[{"branch":"main","label":"v8.12.0","labelRegex":"^v8.12.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/171305","number":171305,"mergeCommit":{"message":"[EDR Workflows] Osquery Package Policy test fix (#171305)","sha":"1ecb6ba073c79f80f03fc285335099b2ce714e52"}},{"branch":"8.11","label":"v8.11.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Tomasz Ciecierski <tomasz.ciecierski@elastic.co>	2023-11-15 11:51:50 -07:00
Kibana Machine	5dbb0c4a3d	[8.11] [Synthetics] Advanced fields broken for icmp monitors (#171161) (#171335) ... # Backport This will backport the following commits from `main` to `8.11`: - [[Synthetics] Advanced fields broken for icmp monitors (#171161)](https://github.com/elastic/kibana/pull/171161) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Shahzad","email":"shahzad31comp@gmail.com"},"sourceCommit":{"committedDate":"2023-11-15T17:12:15Z","message":"[Synthetics] Advanced fields broken for icmp monitors (#171161)","sha":"b356231d02f65afded09f1c9a44bf0218738e1ac","branchLabelMapping":{"^v8.12.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:uptime","backport:prev-minor","v8.12.0"],"number":171161,"url":"https://github.com/elastic/kibana/pull/171161","mergeCommit":{"message":"[Synthetics] Advanced fields broken for icmp monitors (#171161)","sha":"b356231d02f65afded09f1c9a44bf0218738e1ac"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.12.0","labelRegex":"^v8.12.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/171161","number":171161,"mergeCommit":{"message":"[Synthetics] Advanced fields broken for icmp monitors (#171161)","sha":"b356231d02f65afded09f1c9a44bf0218738e1ac"}}]}] BACKPORT--> Co-authored-by: Shahzad <shahzad31comp@gmail.com>	2023-11-15 11:31:14 -07:00
Kibana Machine	8d16b463c4	[8.11] action oauth : quieter logs (#171210) (#171244) ... # Backport This will backport the following commits from `main` to `8.11`: - [action oauth : quieter logs (#171210)](https://github.com/elastic/kibana/pull/171210) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Pierre Gayvallet","email":"pierre.gayvallet@elastic.co"},"sourceCommit":{"committedDate":"2023-11-14T21:19:38Z","message":"action oauth : quieter logs (#171210)\n\n## Summary\r\n\r\nRemove unnecessary details from warning log when fetching an oauth token\r\nthrows an error.","sha":"6ebad69948c9a50b7d6c1c9d790d9e89dc71ba21","branchLabelMapping":{"^v8.12.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","backport:prev-MAJOR","v8.12.0"],"number":171210,"url":"https://github.com/elastic/kibana/pull/171210","mergeCommit":{"message":"action oauth : quieter logs (#171210)\n\n## Summary\r\n\r\nRemove unnecessary details from warning log when fetching an oauth token\r\nthrows an error.","sha":"6ebad69948c9a50b7d6c1c9d790d9e89dc71ba21"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.12.0","labelRegex":"^v8.12.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/171210","number":171210,"mergeCommit":{"message":"action oauth : quieter logs (#171210)\n\n## Summary\r\n\r\nRemove unnecessary details from warning log when fetching an oauth token\r\nthrows an error.","sha":"6ebad69948c9a50b7d6c1c9d790d9e89dc71ba21"}}]}] BACKPORT--> Co-authored-by: Pierre Gayvallet <pierre.gayvallet@elastic.co>	2023-11-14 15:32:15 -07:00
Kibana Machine	124d2bfb57	[8.11] [Cases] Disabling editing ESQL visualizations (#171191) (#171215) ... # Backport This will backport the following commits from `main` to `8.11`: - [[Cases] Disabling editing ESQL visualizations (#171191)](https://github.com/elastic/kibana/pull/171191) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Christos Nasikas","email":"christos.nasikas@elastic.co"},"sourceCommit":{"committedDate":"2023-11-14T16:20:22Z","message":"[Cases] Disabling editing ESQL visualizations (#171191)\n\n## Summary\r\n\r\nThis PR disables editing an ESQL visualization from within Cases.\r\n\r\nFixes: https://github.com/elastic/kibana/issues/171154\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\n### For maintainers\r\n\r\n- [x] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"b7bdb58e7c8a9321bf86d0f24d35435feb8aac6d","branchLabelMapping":{"^v8.12.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","Feature:Cases","backport:prev-minor","Feature:ES|QL","v8.12.0","v8.11.2"],"number":171191,"url":"https://github.com/elastic/kibana/pull/171191","mergeCommit":{"message":"[Cases] Disabling editing ESQL visualizations (#171191)\n\n## Summary\r\n\r\nThis PR disables editing an ESQL visualization from within Cases.\r\n\r\nFixes: https://github.com/elastic/kibana/issues/171154\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\n### For maintainers\r\n\r\n- [x] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"b7bdb58e7c8a9321bf86d0f24d35435feb8aac6d"}},"sourceBranch":"main","suggestedTargetBranches":["8.11"],"targetPullRequestStates":[{"branch":"main","label":"v8.12.0","labelRegex":"^v8.12.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/171191","number":171191,"mergeCommit":{"message":"[Cases] Disabling editing ESQL visualizations (#171191)\n\n## Summary\r\n\r\nThis PR disables editing an ESQL visualization from within Cases.\r\n\r\nFixes: https://github.com/elastic/kibana/issues/171154\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\n### For maintainers\r\n\r\n- [x] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"b7bdb58e7c8a9321bf86d0f24d35435feb8aac6d"}},{"branch":"8.11","label":"v8.11.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Christos Nasikas <christos.nasikas@elastic.co>	2023-11-14 10:43:01 -07:00
Kibana Machine	005e1899fd	[8.11] Fix the custom threshold document link (#171125) (#171214) ... # Backport This will backport the following commits from `main` to `8.11`: - [Fix the custom threshold document link (#171125)](https://github.com/elastic/kibana/pull/171125) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Maryam Saeidi","email":"maryam.saeidi@elastic.co"},"sourceCommit":{"committedDate":"2023-11-14T15:26:47Z","message":"Fix the custom threshold document link (#171125)\n\n## Summary\r\n\r\nFix the custom threshold document link.\r\n\r\n<img\r\nsrc=\"bcbfddb6-3526-4682-b93f-936996d2636b\"\r\nwidth=500 />","sha":"ad79926b778f0a8889d708e145d733a8efcf1d33","branchLabelMapping":{"^v8.12.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","backport:prev-minor","v8.12.0"],"number":171125,"url":"https://github.com/elastic/kibana/pull/171125","mergeCommit":{"message":"Fix the custom threshold document link (#171125)\n\n## Summary\r\n\r\nFix the custom threshold document link.\r\n\r\n<img\r\nsrc=\"bcbfddb6-3526-4682-b93f-936996d2636b\"\r\nwidth=500 />","sha":"ad79926b778f0a8889d708e145d733a8efcf1d33"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.12.0","labelRegex":"^v8.12.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/171125","number":171125,"mergeCommit":{"message":"Fix the custom threshold document link (#171125)\n\n## Summary\r\n\r\nFix the custom threshold document link.\r\n\r\n<img\r\nsrc=\"bcbfddb6-3526-4682-b93f-936996d2636b\"\r\nwidth=500 />","sha":"ad79926b778f0a8889d708e145d733a8efcf1d33"}}]}] BACKPORT--> Co-authored-by: Maryam Saeidi <maryam.saeidi@elastic.co>	2023-11-14 09:42:44 -07:00
Ash	fab4c97b47	[8.11] [Security Solution][Endpoint][Cypress] Update endpoint cypress config to include videos (#170499) (#170841) ... # Backport This will backport the following commits from `main` to `8.11`: - [[Security Solution][Endpoint][Cypress] Update endpoint cypress config to include videos (#170499)](https://github.com/elastic/kibana/pull/170499) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Ash","email":"1849116+ashokaditya@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-11-06T16:04:42Z","message":"[Security Solution][Endpoint][Cypress] Update endpoint cypress config to include videos (#170499)\n\n## Summary\r\n\r\nAdds videos to failed cypress tests for debugging.","sha":"1c2521705a1ece1ebe87740a4c99c27b254630f9","branchLabelMapping":{"^v8.12.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Defend Workflows","OLM Sprint","v8.11.0","v8.12.0"],"number":170499,"url":"https://github.com/elastic/kibana/pull/170499","mergeCommit":{"message":"[Security Solution][Endpoint][Cypress] Update endpoint cypress config to include videos (#170499)\n\n## Summary\r\n\r\nAdds videos to failed cypress tests for debugging.","sha":"1c2521705a1ece1ebe87740a4c99c27b254630f9"}},"sourceBranch":"main","suggestedTargetBranches":["8.11"],"targetPullRequestStates":[{"branch":"8.11","label":"v8.11.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.12.0","labelRegex":"^v8.12.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/170499","number":170499,"mergeCommit":{"message":"[Security Solution][Endpoint][Cypress] Update endpoint cypress config to include videos (#170499)\n\n## Summary\r\n\r\nAdds videos to failed cypress tests for debugging.","sha":"1c2521705a1ece1ebe87740a4c99c27b254630f9"}}]}] BACKPORT--> Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>	2023-11-14 16:09:54 +01:00