mirror of
https://github.com/elastic/kibana.git
synced 2025-04-21 08:19:33 -04:00
759 commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
Tiago Costa
|
9621d8dd51
|
[8.16] chore(NA): upgrade to webpack 5 (#191106) (#211152)
# Backport This will backport the following commits from `main` to `8.16`: - [chore(NA): upgrade to webpack 5 (#191106)](https://github.com/elastic/kibana/pull/191106) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Tiago Costa","email":"tiago.costa@elastic.co"},"sourceCommit":{"committedDate":"2025-02-14T03:01:36Z","message":"chore(NA): upgrade to webpack 5 (#191106)\n\n### Summary\r\n\r\n- Closes #89741\r\n\r\nThis PR contains the resulting work of a massive effort that ports our\r\non top bundler abstraction (called @kbn/optimizer) from Webpack v4 into\r\nWebpack v5. It's essential in terms of long term maintenance since v4\r\nwas not receiving updates any longer but will also unblock some new\r\nfeatures that could be beneficial for our future DevEx endeavours.\r\n\r\nNext you can find a small list of all the accomplished tasks on this\r\njourney.\r\n\r\n### Completed Tasks\r\n- [x] Upgrade dependencies to match the ones on webpack v5\r\n- [x] Fix null-loader usages\r\n- [x] Fix raw-loader usages\r\n- [x] Fix file-loader usages\r\n- [x] Fix url-loader usages\r\n- [x] Fix `@kbn/optimizer-webpack-helpers` to support webpack v5 \r\n- [x] Adopt previous webpack v4 polyfill-all strategy with\r\nnode-polyfill-webpack-plugin\r\n- [x] Fix theme-loader on @kbn/optimizer\r\n- [x] Migrate configurations and ad-hoc loader options on all webpack\r\nconfigs from v4 to v5\r\n- [x] Fix @kbn/test jest resolver for file-loader cases\r\n- [x] Migrate public-path loader on UiSharedDeps\r\n- [x] Fix all usages of webpack-merge\r\n- [x] Migrate BundleRemoteModule\r\n- [x] Migrate BundleRemotesPlugin\r\n- [x] Correctly migrate PopulateBundleCachePlugin\r\n- [x] Correctly migrate BundleMetricsPlugin\r\n- [x] Check if the profiling plugins still work (--profile flag)\r\n- [x] Recover if possible the previous webpack v4 cacheGroup chunks\r\nrename to something like `data.plugin.chunk.0.js`\r\n- [x] Run `/ci` and make sure we get our first green CI, otherwise work\r\non the errors until we do\r\n- [x] Profile and solve bottlenecks until we get a cold build\r\nperformance similar to the one we had on webpack v4 (`node\r\nscripts/build_kibana_platform_plugins --no-cache`).\r\n- [x] OpenSSL Legacy Warnings: try to remove `--openssl-legacy-provider\r\n` flags\r\n- [x] Add Webpack to Renovate config\r\n- [x] Explore removing `NodePolyfillPlugin`\r\n([here](https://www.npmjs.com/package/node-polyfill-webpack-plugin)) and\r\nadd each polyfill needed individually per each webpack config to check\r\nif we get smaller bundles. If we do it's better to go with the case by\r\ncase need approach instead of deploying a bunch of polyfills with\r\nNodePolyfillPlugin. As another alternative, create a custom smaller\r\nplugin with only the union of all needed polyfills.\r\n- [x] Evaluate if we want to touch the resolutions on mainFields and\r\nconditionNames\r\n- [x] Understand why `@import 'src/core/public/mixins'` does not work\r\nanymore (not a problem, we should use relative paths anyway but we want\r\nto track why it changed from v4 to v5)\r\n- [x] BUG: Child compilers are having errors hidden and/or changed from\r\nerror to warning\r\n- [x] Fix license check for\r\n[Artistic-2.0](https://spdx.org/licenses/Artistic-2.0.html) is the\r\nlicense for\r\n[domain-browser](https://github.com/bevry/domain-browser?tab=License-1-ov-file).\r\nThis package is a dependency of\r\n[NodePolyfillPlugin](https://www.npmjs.com/package/node-polyfill-webpack-plugin).\r\nArtistic 2.0 license is [classified as\r\nyellow](https://github.com/elastic/open-source/blob/main/elastic-product-policy.md#yellow-list)\r\nand should only be used for dev dependencies.\r\n- [x] Make sure `resourceQuery: { not: /raw/ }` is not necessary on\r\nother webpack configs like storybook one\r\n- [x] Find what is being wrongly removed by usedExports optimization;\r\nhint: I believe it is identifying a lot of exports inside the sync entry\r\nof plugins as unused exports and removing them. Then `__kbnBootstrap__`\r\ncan't be found\r\n- [x] Rebalance @kbn/optimizer pickMaxWorkerCount\r\n- [x] Re-open the issue to fix sass-warnings\r\n[#190345](https://github.com/elastic/kibana/issues/190345) or downgrade\r\nsass-loader to v10\r\n- [x] Remove previous esm no parse rules\r\n- [x] Confirm esm support is working\r\n- [x] Confirm console override is needed\r\n- [x] Confirm react prod builds on ui shared deps for distributable\r\n- [x] Remove customization for\r\n[xyflow](https://github.com/xyflow/xyflow) from webpack configs\r\n- [x] Clean all the code\r\n- [x] Make sure collected metrics from stats are still aligned with what\r\nwe were collecting before; also verify if the modules used for optimizer\r\ncaches etc are well generated (@kbn/node-libs-browser)\r\n- [x] Fix watch performance\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Brad White <brad.white@elastic.co>","sha":"203bc284781cc830049b3f7948c8fcafa8b7d9a1","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["chore","Team:Operations","release_note:skip","Team:Fleet","v9.0.0","backport:all-open","ci:build-webpack-bundle-analyzer","Team:obs-ux-infra_services","v9.1.0"],"title":"chore(NA): upgrade to webpack 5","number":191106,"url":"https://github.com/elastic/kibana/pull/191106","mergeCommit":{"message":"chore(NA): upgrade to webpack 5 (#191106)\n\n### Summary\r\n\r\n- Closes #89741\r\n\r\nThis PR contains the resulting work of a massive effort that ports our\r\non top bundler abstraction (called @kbn/optimizer) from Webpack v4 into\r\nWebpack v5. It's essential in terms of long term maintenance since v4\r\nwas not receiving updates any longer but will also unblock some new\r\nfeatures that could be beneficial for our future DevEx endeavours.\r\n\r\nNext you can find a small list of all the accomplished tasks on this\r\njourney.\r\n\r\n### Completed Tasks\r\n- [x] Upgrade dependencies to match the ones on webpack v5\r\n- [x] Fix null-loader usages\r\n- [x] Fix raw-loader usages\r\n- [x] Fix file-loader usages\r\n- [x] Fix url-loader usages\r\n- [x] Fix `@kbn/optimizer-webpack-helpers` to support webpack v5 \r\n- [x] Adopt previous webpack v4 polyfill-all strategy with\r\nnode-polyfill-webpack-plugin\r\n- [x] Fix theme-loader on @kbn/optimizer\r\n- [x] Migrate configurations and ad-hoc loader options on all webpack\r\nconfigs from v4 to v5\r\n- [x] Fix @kbn/test jest resolver for file-loader cases\r\n- [x] Migrate public-path loader on UiSharedDeps\r\n- [x] Fix all usages of webpack-merge\r\n- [x] Migrate BundleRemoteModule\r\n- [x] Migrate BundleRemotesPlugin\r\n- [x] Correctly migrate PopulateBundleCachePlugin\r\n- [x] Correctly migrate BundleMetricsPlugin\r\n- [x] Check if the profiling plugins still work (--profile flag)\r\n- [x] Recover if possible the previous webpack v4 cacheGroup chunks\r\nrename to something like `data.plugin.chunk.0.js`\r\n- [x] Run `/ci` and make sure we get our first green CI, otherwise work\r\non the errors until we do\r\n- [x] Profile and solve bottlenecks until we get a cold build\r\nperformance similar to the one we had on webpack v4 (`node\r\nscripts/build_kibana_platform_plugins --no-cache`).\r\n- [x] OpenSSL Legacy Warnings: try to remove `--openssl-legacy-provider\r\n` flags\r\n- [x] Add Webpack to Renovate config\r\n- [x] Explore removing `NodePolyfillPlugin`\r\n([here](https://www.npmjs.com/package/node-polyfill-webpack-plugin)) and\r\nadd each polyfill needed individually per each webpack config to check\r\nif we get smaller bundles. If we do it's better to go with the case by\r\ncase need approach instead of deploying a bunch of polyfills with\r\nNodePolyfillPlugin. As another alternative, create a custom smaller\r\nplugin with only the union of all needed polyfills.\r\n- [x] Evaluate if we want to touch the resolutions on mainFields and\r\nconditionNames\r\n- [x] Understand why `@import 'src/core/public/mixins'` does not work\r\nanymore (not a problem, we should use relative paths anyway but we want\r\nto track why it changed from v4 to v5)\r\n- [x] BUG: Child compilers are having errors hidden and/or changed from\r\nerror to warning\r\n- [x] Fix license check for\r\n[Artistic-2.0](https://spdx.org/licenses/Artistic-2.0.html) is the\r\nlicense for\r\n[domain-browser](https://github.com/bevry/domain-browser?tab=License-1-ov-file).\r\nThis package is a dependency of\r\n[NodePolyfillPlugin](https://www.npmjs.com/package/node-polyfill-webpack-plugin).\r\nArtistic 2.0 license is [classified as\r\nyellow](https://github.com/elastic/open-source/blob/main/elastic-product-policy.md#yellow-list)\r\nand should only be used for dev dependencies.\r\n- [x] Make sure `resourceQuery: { not: /raw/ }` is not necessary on\r\nother webpack configs like storybook one\r\n- [x] Find what is being wrongly removed by usedExports optimization;\r\nhint: I believe it is identifying a lot of exports inside the sync entry\r\nof plugins as unused exports and removing them. Then `__kbnBootstrap__`\r\ncan't be found\r\n- [x] Rebalance @kbn/optimizer pickMaxWorkerCount\r\n- [x] Re-open the issue to fix sass-warnings\r\n[#190345](https://github.com/elastic/kibana/issues/190345) or downgrade\r\nsass-loader to v10\r\n- [x] Remove previous esm no parse rules\r\n- [x] Confirm esm support is working\r\n- [x] Confirm console override is needed\r\n- [x] Confirm react prod builds on ui shared deps for distributable\r\n- [x] Remove customization for\r\n[xyflow](https://github.com/xyflow/xyflow) from webpack configs\r\n- [x] Clean all the code\r\n- [x] Make sure collected metrics from stats are still aligned with what\r\nwe were collecting before; also verify if the modules used for optimizer\r\ncaches etc are well generated (@kbn/node-libs-browser)\r\n- [x] Fix watch performance\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Brad White <brad.white@elastic.co>","sha":"203bc284781cc830049b3f7948c8fcafa8b7d9a1"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/211145","number":211145,"state":"OPEN"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/191106","number":191106,"mergeCommit":{"message":"chore(NA): upgrade to webpack 5 (#191106)\n\n### Summary\r\n\r\n- Closes #89741\r\n\r\nThis PR contains the resulting work of a massive effort that ports our\r\non top bundler abstraction (called @kbn/optimizer) from Webpack v4 into\r\nWebpack v5. It's essential in terms of long term maintenance since v4\r\nwas not receiving updates any longer but will also unblock some new\r\nfeatures that could be beneficial for our future DevEx endeavours.\r\n\r\nNext you can find a small list of all the accomplished tasks on this\r\njourney.\r\n\r\n### Completed Tasks\r\n- [x] Upgrade dependencies to match the ones on webpack v5\r\n- [x] Fix null-loader usages\r\n- [x] Fix raw-loader usages\r\n- [x] Fix file-loader usages\r\n- [x] Fix url-loader usages\r\n- [x] Fix `@kbn/optimizer-webpack-helpers` to support webpack v5 \r\n- [x] Adopt previous webpack v4 polyfill-all strategy with\r\nnode-polyfill-webpack-plugin\r\n- [x] Fix theme-loader on @kbn/optimizer\r\n- [x] Migrate configurations and ad-hoc loader options on all webpack\r\nconfigs from v4 to v5\r\n- [x] Fix @kbn/test jest resolver for file-loader cases\r\n- [x] Migrate public-path loader on UiSharedDeps\r\n- [x] Fix all usages of webpack-merge\r\n- [x] Migrate BundleRemoteModule\r\n- [x] Migrate BundleRemotesPlugin\r\n- [x] Correctly migrate PopulateBundleCachePlugin\r\n- [x] Correctly migrate BundleMetricsPlugin\r\n- [x] Check if the profiling plugins still work (--profile flag)\r\n- [x] Recover if possible the previous webpack v4 cacheGroup chunks\r\nrename to something like `data.plugin.chunk.0.js`\r\n- [x] Run `/ci` and make sure we get our first green CI, otherwise work\r\non the errors until we do\r\n- [x] Profile and solve bottlenecks until we get a cold build\r\nperformance similar to the one we had on webpack v4 (`node\r\nscripts/build_kibana_platform_plugins --no-cache`).\r\n- [x] OpenSSL Legacy Warnings: try to remove `--openssl-legacy-provider\r\n` flags\r\n- [x] Add Webpack to Renovate config\r\n- [x] Explore removing `NodePolyfillPlugin`\r\n([here](https://www.npmjs.com/package/node-polyfill-webpack-plugin)) and\r\nadd each polyfill needed individually per each webpack config to check\r\nif we get smaller bundles. If we do it's better to go with the case by\r\ncase need approach instead of deploying a bunch of polyfills with\r\nNodePolyfillPlugin. As another alternative, create a custom smaller\r\nplugin with only the union of all needed polyfills.\r\n- [x] Evaluate if we want to touch the resolutions on mainFields and\r\nconditionNames\r\n- [x] Understand why `@import 'src/core/public/mixins'` does not work\r\nanymore (not a problem, we should use relative paths anyway but we want\r\nto track why it changed from v4 to v5)\r\n- [x] BUG: Child compilers are having errors hidden and/or changed from\r\nerror to warning\r\n- [x] Fix license check for\r\n[Artistic-2.0](https://spdx.org/licenses/Artistic-2.0.html) is the\r\nlicense for\r\n[domain-browser](https://github.com/bevry/domain-browser?tab=License-1-ov-file).\r\nThis package is a dependency of\r\n[NodePolyfillPlugin](https://www.npmjs.com/package/node-polyfill-webpack-plugin).\r\nArtistic 2.0 license is [classified as\r\nyellow](https://github.com/elastic/open-source/blob/main/elastic-product-policy.md#yellow-list)\r\nand should only be used for dev dependencies.\r\n- [x] Make sure `resourceQuery: { not: /raw/ }` is not necessary on\r\nother webpack configs like storybook one\r\n- [x] Find what is being wrongly removed by usedExports optimization;\r\nhint: I believe it is identifying a lot of exports inside the sync entry\r\nof plugins as unused exports and removing them. Then `__kbnBootstrap__`\r\ncan't be found\r\n- [x] Rebalance @kbn/optimizer pickMaxWorkerCount\r\n- [x] Re-open the issue to fix sass-warnings\r\n[#190345](https://github.com/elastic/kibana/issues/190345) or downgrade\r\nsass-loader to v10\r\n- [x] Remove previous esm no parse rules\r\n- [x] Confirm esm support is working\r\n- [x] Confirm console override is needed\r\n- [x] Confirm react prod builds on ui shared deps for distributable\r\n- [x] Remove customization for\r\n[xyflow](https://github.com/xyflow/xyflow) from webpack configs\r\n- [x] Clean all the code\r\n- [x] Make sure collected metrics from stats are still aligned with what\r\nwe were collecting before; also verify if the modules used for optimizer\r\ncaches etc are well generated (@kbn/node-libs-browser)\r\n- [x] Fix watch performance\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Brad White <brad.white@elastic.co>","sha":"203bc284781cc830049b3f7948c8fcafa8b7d9a1"}},{"url":"https://github.com/elastic/kibana/pull/211146","number":211146,"branch":"8.x","state":"OPEN"},{"url":"https://github.com/elastic/kibana/pull/211147","number":211147,"branch":"8.18","state":"OPEN"},{"url":"https://github.com/elastic/kibana/pull/211148","number":211148,"branch":"8.17","state":"OPEN"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
Kibana Machine
|
020e9f51c5
|
[8.16] [Security Solution] [KB Management] Fix sorting by name in the kb entries table (#209141) (#210524)
# Backport This will backport the following commits from `main` to `8.16`: - [[Security Solution] [KB Management] Fix sorting by name in the kb entries table (#209141)](https://github.com/elastic/kibana/pull/209141) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Kenneth Kreindler","email":"42113355+KDKHD@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-11T10:18:02Z","message":"[Security Solution] [KB Management] Fix sorting by name in the kb entries table (#209141)\n\nFixes https://github.com/elastic/kibana/issues/199253\r\n\r\n## Summary\r\n\r\nFixes the issue where KB entries in knowledge base management were not\r\nsorting correctly by name. Previously, entries with names starting with\r\nuppercase letters appeared before those with lowercase names, instead of\r\nfollowing a case-insensitive alphabetical order. This update ensures\r\nproper sorting regardless of letter case.\r\n\r\nBefore:\r\n<img width=\"3120\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/1657fce4-abba-4672-aaa8-8c5c6c660c98\"\r\n/>\r\n\r\n\r\nAfter:\r\n<img width=\"3120\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/10d1f3fc-f6db-4b5b-b67b-8b8ae7250dd4\"\r\n/>\r\n\r\n\r\n\r\nHow to test:\r\n- See instructions in the issue. Create uppercase and lowercase KB\r\nentries (e.g. A,a,b,B,c,C. Create the entries in that order).\r\n- Reorder the table based on name and check the ordering makes sense.\r\n\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\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/src/platform/packages/shared/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] 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 was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\r\n- [x] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n### Identify risks\r\n\r\nDoes this PR introduce any risks? For example, consider risks like hard\r\nto test bugs, performance regression, potential of data loss.\r\n\r\nDescribe the risk, its severity, and mitigation for each identified\r\nrisk. Invite stakeholders and evaluate how to proceed before merging.\r\n\r\n- [ ] [See some risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\r\n- [ ] ...\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"a1356ffb9f10b0958553ddab2b7d8332fc495f43","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-major","Team:Security Generative AI","v9.1.0"],"title":"[Security Solution] [KB Management] Fix sorting by name in the kb entries table","number":209141,"url":"https://github.com/elastic/kibana/pull/209141","mergeCommit":{"message":"[Security Solution] [KB Management] Fix sorting by name in the kb entries table (#209141)\n\nFixes https://github.com/elastic/kibana/issues/199253\r\n\r\n## Summary\r\n\r\nFixes the issue where KB entries in knowledge base management were not\r\nsorting correctly by name. Previously, entries with names starting with\r\nuppercase letters appeared before those with lowercase names, instead of\r\nfollowing a case-insensitive alphabetical order. This update ensures\r\nproper sorting regardless of letter case.\r\n\r\nBefore:\r\n<img width=\"3120\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/1657fce4-abba-4672-aaa8-8c5c6c660c98\"\r\n/>\r\n\r\n\r\nAfter:\r\n<img width=\"3120\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/10d1f3fc-f6db-4b5b-b67b-8b8ae7250dd4\"\r\n/>\r\n\r\n\r\n\r\nHow to test:\r\n- See instructions in the issue. Create uppercase and lowercase KB\r\nentries (e.g. A,a,b,B,c,C. Create the entries in that order).\r\n- Reorder the table based on name and check the ordering makes sense.\r\n\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\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/src/platform/packages/shared/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] 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 was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\r\n- [x] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n### Identify risks\r\n\r\nDoes this PR introduce any risks? For example, consider risks like hard\r\nto test bugs, performance regression, potential of data loss.\r\n\r\nDescribe the risk, its severity, and mitigation for each identified\r\nrisk. Invite stakeholders and evaluate how to proceed before merging.\r\n\r\n- [ ] [See some risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\r\n- [ ] ...\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"a1356ffb9f10b0958553ddab2b7d8332fc495f43"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/209141","number":209141,"mergeCommit":{"message":"[Security Solution] [KB Management] Fix sorting by name in the kb entries table (#209141)\n\nFixes https://github.com/elastic/kibana/issues/199253\r\n\r\n## Summary\r\n\r\nFixes the issue where KB entries in knowledge base management were not\r\nsorting correctly by name. Previously, entries with names starting with\r\nuppercase letters appeared before those with lowercase names, instead of\r\nfollowing a case-insensitive alphabetical order. This update ensures\r\nproper sorting regardless of letter case.\r\n\r\nBefore:\r\n<img width=\"3120\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/1657fce4-abba-4672-aaa8-8c5c6c660c98\"\r\n/>\r\n\r\n\r\nAfter:\r\n<img width=\"3120\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/10d1f3fc-f6db-4b5b-b67b-8b8ae7250dd4\"\r\n/>\r\n\r\n\r\n\r\nHow to test:\r\n- See instructions in the issue. Create uppercase and lowercase KB\r\nentries (e.g. A,a,b,B,c,C. Create the entries in that order).\r\n- Reorder the table based on name and check the ordering makes sense.\r\n\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\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/src/platform/packages/shared/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] 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 was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\r\n- [x] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n### Identify risks\r\n\r\nDoes this PR introduce any risks? For example, consider risks like hard\r\nto test bugs, performance regression, potential of data loss.\r\n\r\nDescribe the risk, its severity, and mitigation for each identified\r\nrisk. Invite stakeholders and evaluate how to proceed before merging.\r\n\r\n- [ ] [See some risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\r\n- [ ] ...\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"a1356ffb9f10b0958553ddab2b7d8332fc495f43"}}]}] BACKPORT--> --------- Co-authored-by: Kenneth Kreindler <42113355+KDKHD@users.noreply.github.com> |
||
|
Kibana Machine
|
310514fd16
|
[8.16] [Security GenAI] "Select a Connector" popup does not show up after the user selects any connector and then cancels it from Endpoint Insights. (#208907) (#208969) (#208989)
# Backport This will backport the following commits from `main` to `8.16`: - [[Security GenAI] "Select a Connector" popup does not show up after the user selects any connector and then cancels it from Endpoint Insights. (#208907) (#208969)](https://github.com/elastic/kibana/pull/208969) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Ievgen Sorokopud","email":"ievgen.sorokopud@elastic.co"},"sourceCommit":{"committedDate":"2025-01-30T16:53:36Z","message":"[Security GenAI] \"Select a Connector\" popup does not show up after the user selects any connector and then cancels it from Endpoint Insights. (#208907) (#208969)\n\n## Summary\r\n\r\nBUG: https://github.com/elastic/kibana/issues/208907\r\n\r\nThis PR fixes the issue where user cannot select a different connector\r\ntype after mistakenly selecting a wrong one.\r\n\r\n### Steps to reproduce without required endpoint installation:\r\n\r\n1. Make sure there are no connectors\r\n2. Open \"AI Assistant\" on one of the security solution pages\r\n3. Press \"(+) Add connector\" button\r\n4. Connector type selection modal is visible\r\n5. Select \"Amazon Bedrock\" type (or any other connector type)\r\n6. Cancel the modal\r\n7. Press \"(+) Add connector\" button again\r\n\r\n**ISSUE**: previously selected connector type is being displayed and\r\nthere is no way to switch between types\r\n**EXPECTED**: we should show connector type selection modal once\r\nprevious one was closed\r\n\r\n### Issue recording\r\n\r\n\r\nhttps://github.com/user-attachments/assets/48052bf1-4e00-43b7-a63e-f8a7969b9dbf\r\n\r\n### Fixed state recording\r\n\r\n\r\nhttps://github.com/user-attachments/assets/48be1cc4-0326-43a1-bd57-bb82fc1f19eb","sha":"b28036a2e0f13358b4da614761d32667612ac03a","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","Team: SecuritySolution","backport:prev-major","Team:Security Generative AI"],"title":"[Security GenAI] \"Select a Connector\" popup does not show up after the user selects any connector and then cancels it from Endpoint Insights. (#208907)","number":208969,"url":"https://github.com/elastic/kibana/pull/208969","mergeCommit":{"message":"[Security GenAI] \"Select a Connector\" popup does not show up after the user selects any connector and then cancels it from Endpoint Insights. (#208907) (#208969)\n\n## Summary\r\n\r\nBUG: https://github.com/elastic/kibana/issues/208907\r\n\r\nThis PR fixes the issue where user cannot select a different connector\r\ntype after mistakenly selecting a wrong one.\r\n\r\n### Steps to reproduce without required endpoint installation:\r\n\r\n1. Make sure there are no connectors\r\n2. Open \"AI Assistant\" on one of the security solution pages\r\n3. Press \"(+) Add connector\" button\r\n4. Connector type selection modal is visible\r\n5. Select \"Amazon Bedrock\" type (or any other connector type)\r\n6. Cancel the modal\r\n7. Press \"(+) Add connector\" button again\r\n\r\n**ISSUE**: previously selected connector type is being displayed and\r\nthere is no way to switch between types\r\n**EXPECTED**: we should show connector type selection modal once\r\nprevious one was closed\r\n\r\n### Issue recording\r\n\r\n\r\nhttps://github.com/user-attachments/assets/48052bf1-4e00-43b7-a63e-f8a7969b9dbf\r\n\r\n### Fixed state recording\r\n\r\n\r\nhttps://github.com/user-attachments/assets/48be1cc4-0326-43a1-bd57-bb82fc1f19eb","sha":"b28036a2e0f13358b4da614761d32667612ac03a"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/208969","number":208969,"mergeCommit":{"message":"[Security GenAI] \"Select a Connector\" popup does not show up after the user selects any connector and then cancels it from Endpoint Insights. (#208907) (#208969)\n\n## Summary\r\n\r\nBUG: https://github.com/elastic/kibana/issues/208907\r\n\r\nThis PR fixes the issue where user cannot select a different connector\r\ntype after mistakenly selecting a wrong one.\r\n\r\n### Steps to reproduce without required endpoint installation:\r\n\r\n1. Make sure there are no connectors\r\n2. Open \"AI Assistant\" on one of the security solution pages\r\n3. Press \"(+) Add connector\" button\r\n4. Connector type selection modal is visible\r\n5. Select \"Amazon Bedrock\" type (or any other connector type)\r\n6. Cancel the modal\r\n7. Press \"(+) Add connector\" button again\r\n\r\n**ISSUE**: previously selected connector type is being displayed and\r\nthere is no way to switch between types\r\n**EXPECTED**: we should show connector type selection modal once\r\nprevious one was closed\r\n\r\n### Issue recording\r\n\r\n\r\nhttps://github.com/user-attachments/assets/48052bf1-4e00-43b7-a63e-f8a7969b9dbf\r\n\r\n### Fixed state recording\r\n\r\n\r\nhttps://github.com/user-attachments/assets/48be1cc4-0326-43a1-bd57-bb82fc1f19eb","sha":"b28036a2e0f13358b4da614761d32667612ac03a"}}]}] BACKPORT--> Co-authored-by: Ievgen Sorokopud <ievgen.sorokopud@elastic.co> |
||
|
Kibana Machine
|
ea8f4acba1
|
[8.16] [Lens] add an accessible label to range slider (#205308) (#208306)
# Backport This will backport the following commits from `main` to `8.16`: - [[Lens] add an accessible label to range slider (#205308)](https://github.com/elastic/kibana/pull/205308) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Marta Bondyra","email":"4283304+mbondyra@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-01-25T22:11:46Z","message":"[Lens] add an accessible label to range slider (#205308)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/182765 (with the solution\r\nsuggested by @1Copenut)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"ed5728302a3063af325ea862f64c019bd67cbb5e","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Visualizations","Feature:Lens","v9.0.0","backport:prev-major"],"title":"[Lens] add an accessible label to range slider","number":205308,"url":"https://github.com/elastic/kibana/pull/205308","mergeCommit":{"message":"[Lens] add an accessible label to range slider (#205308)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/182765 (with the solution\r\nsuggested by @1Copenut)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"ed5728302a3063af325ea862f64c019bd67cbb5e"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/205308","number":205308,"mergeCommit":{"message":"[Lens] add an accessible label to range slider (#205308)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/182765 (with the solution\r\nsuggested by @1Copenut)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"ed5728302a3063af325ea862f64c019bd67cbb5e"}}]}] BACKPORT--> Co-authored-by: Marta Bondyra <4283304+mbondyra@users.noreply.github.com> |
||
Kenneth Kreindler
|
56aebad97e
|
[8.16] [Security Assistant] Move security AI assistant button into global nav bar (#203060) (#205886)
# Backport This will backport the following commits from `main` to `8.16`: - [[Security Assistant] Move security AI assistant button into global nav bar (#203060)](https://github.com/elastic/kibana/pull/203060) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Kenneth Kreindler","email":"42113355+KDKHD@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-01-08T10:03:54Z","message":"[Security Assistant] Move security AI assistant button into global nav bar (#203060)\n\n## Summary\r\n\r\nMore changes are needed within the observability and search solution to\r\nclose the issue fully.\r\n\r\nSummarise your PR. If it involves visual changes include a screenshot or\r\ngif.\r\n\r\nMove the security AI assistant button from the solution header bar into\r\nthe global nav bar. This is part of the AI assistant unification\r\ninitiative.\r\n\r\n### How to Test\r\n- Start kibana\r\n- Go to one of the security solution pages (e.g. attack discovery)\r\n- AI assistant button should be in the global nav bar. Clicking it opens\r\nthe assistant.\r\n\r\n- The button can also be tested for security serverless deployment. It\r\nshould look like the screenshot bellow.\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [x] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] This was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\r\n- [x] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n### Identify risks\r\n\r\nDoes this PR introduce any risks? For example, consider risks like hard\r\nto test bugs, performance regression, potential of data loss.\r\n\r\nDescribe the risk, its severity, and mitigation for each identified\r\nrisk. Invite stakeholders and evaluate how to proceed before merging.\r\n\r\n- [ ] [See some risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\r\n- [ ] ...\r\n\r\nClassic:\r\n\r\n (#203581)
# Backport This will backport the following commits from `main` to `8.16`: - [[Security Assistant] Fix animation border color of security AI assistant (#202319)](https://github.com/elastic/kibana/pull/202319) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Kenneth Kreindler","email":"42113355+KDKHD@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-12-10T13:43:13Z","message":"[Security Assistant] Fix animation border color of security AI assistant (#202319)\n\n## Summary\r\n\r\n**Resolves: https://github.com/elastic/kibana/issues/186135**\r\n\r\nChanges:\r\n- Update border color of animated border of the security AI assistance\r\nicon from `euiColorPrimary` to `euiBorderColor`.\r\n\r\nOld border color:\r\n<img width=\"182\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/a41a7859-3f9a-488c-bd4f-2ed25a52a481\">\r\n\r\nNew border color:\r\n<img width=\"169\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/c7e1fa13-adb0-4014-950f-ae643e4e1d6d\">\r\n<img width=\"347\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/8fba05e2-2a5b-48b2-b367-a58162cdaa9e\">\r\n\r\nNew animated:\r\n\r\n\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n### Identify risks\r\n\r\nDoes this PR introduce any risks? For example, consider risks like hard\r\nto test bugs, performance regression, potential of data loss.\r\n\r\nNo\r\n\r\nDescribe the risk, its severity, and mitigation for each identified\r\nrisk. Invite stakeholders and evaluate how to proceed before merging.\r\n\r\n- [X] [See some risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"2818a7cc5a94880964017e9ff80dcd546f5357f7","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","v9.0.0","backport:prev-major","Feature:Security Assistant","Team:Security Generative AI","v8.18.0"],"title":"[Security Assistant] Fix animation border color of security AI assistant","number":202319,"url":"https://github.com/elastic/kibana/pull/202319","mergeCommit":{"message":"[Security Assistant] Fix animation border color of security AI assistant (#202319)\n\n## Summary\r\n\r\n**Resolves: https://github.com/elastic/kibana/issues/186135**\r\n\r\nChanges:\r\n- Update border color of animated border of the security AI assistance\r\nicon from `euiColorPrimary` to `euiBorderColor`.\r\n\r\nOld border color:\r\n<img width=\"182\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/a41a7859-3f9a-488c-bd4f-2ed25a52a481\">\r\n\r\nNew border color:\r\n<img width=\"169\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/c7e1fa13-adb0-4014-950f-ae643e4e1d6d\">\r\n<img width=\"347\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/8fba05e2-2a5b-48b2-b367-a58162cdaa9e\">\r\n\r\nNew animated:\r\n\r\n\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n### Identify risks\r\n\r\nDoes this PR introduce any risks? For example, consider risks like hard\r\nto test bugs, performance regression, potential of data loss.\r\n\r\nNo\r\n\r\nDescribe the risk, its severity, and mitigation for each identified\r\nrisk. Invite stakeholders and evaluate how to proceed before merging.\r\n\r\n- [X] [See some risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"2818a7cc5a94880964017e9ff80dcd546f5357f7"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202319","number":202319,"mergeCommit":{"message":"[Security Assistant] Fix animation border color of security AI assistant (#202319)\n\n## Summary\r\n\r\n**Resolves: https://github.com/elastic/kibana/issues/186135**\r\n\r\nChanges:\r\n- Update border color of animated border of the security AI assistance\r\nicon from `euiColorPrimary` to `euiBorderColor`.\r\n\r\nOld border color:\r\n<img width=\"182\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/a41a7859-3f9a-488c-bd4f-2ed25a52a481\">\r\n\r\nNew border color:\r\n<img width=\"169\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/c7e1fa13-adb0-4014-950f-ae643e4e1d6d\">\r\n<img width=\"347\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/8fba05e2-2a5b-48b2-b367-a58162cdaa9e\">\r\n\r\nNew animated:\r\n\r\n\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n### Identify risks\r\n\r\nDoes this PR introduce any risks? For example, consider risks like hard\r\nto test bugs, performance regression, potential of data loss.\r\n\r\nNo\r\n\r\nDescribe the risk, its severity, and mitigation for each identified\r\nrisk. Invite stakeholders and evaluate how to proceed before merging.\r\n\r\n- [X] [See some risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"2818a7cc5a94880964017e9ff80dcd546f5357f7"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: Kenneth Kreindler <42113355+KDKHD@users.noreply.github.com> Co-authored-by: Kenneth Kreindler <kenneth.kreindler@elastic.co> |
||
|
Kibana Machine
|
c6ebceb178
|
[8.16] [Security Solution] AI Assistant: LLM Connector model chooser bug. New chat does not use connector's model (#199303) (#204014) (#204306)
# Backport This will backport the following commits from `main` to `8.16`: - [[Security Solution] AI Assistant: LLM Connector model chooser bug. New chat does not use connector's model (#199303) (#204014)](https://github.com/elastic/kibana/pull/204014) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Ievgen Sorokopud","email":"ievgen.sorokopud@elastic.co"},"sourceCommit":{"committedDate":"2024-12-14T08:54:54Z","message":"[Security Solution] AI Assistant: LLM Connector model chooser bug. New chat does not use connector's model (#199303) (#204014)\n\n## Summary\r\n\r\nThe PR fixes [this bug](https://github.com/elastic/kibana/issues/199303)\r\n\r\nThe issue happens with some of the locally setup LLMs (like\r\n[Ollama](https://github.com/ollama/ollama)) which requires the correct\r\n`model` to be passed as part of the [chat completions\r\nAPI](https://github.com/ollama/ollama/blob/main/docs/api.md#generate-a-chat-completion).\r\n\r\nWe had a bug in our code when on new conversation creation we would not\r\npass all the connectors configuration and only `connectorId` and\r\n`actionTypeId` would be passed. Here is the old code implementation:\r\n\r\n```\r\nconst newConversation = await createConversation({\r\n title: NEW_CHAT,\r\n ...(currentConversation?.apiConfig != null &&\r\n currentConversation?.apiConfig?.actionTypeId != null\r\n ? {\r\n apiConfig: {\r\n connectorId: currentConversation.apiConfig.connectorId,\r\n actionTypeId: currentConversation.apiConfig.actionTypeId,\r\n ...(newSystemPrompt?.id != null ? { defaultSystemPromptId: newSystemPrompt.id } : {}),\r\n },\r\n }\r\n : {}),\r\n});\r\n```\r\n\r\nand thus the new conversation would not have the complete connector\r\nconfiguration which would cause to use default model (`gpt-4o`) as a\r\nmodel we pass to the LLM.\r\n\r\nAlso, I updated the default body that we use on the Test connector page,\r\nto make sure that we send a model parameter to the LLM in case of `Open\r\nAI > Other (OpenAI Compatible Service)` kind of connectors.\r\n\r\n### Testing notes\r\n\r\nSteps to reproduce:\r\n1. Install\r\n[Ollama](https://github.com/ollama/ollama?tab=readme-ov-file#ollama)\r\nlocally\r\n2. Setup an OpenAI connector using Other (OpenAI Compatible Service)\r\nprovider\r\n3. Open AI Assistant and select created Ollama connector to chat\r\n4. Create a \"New Chat\"\r\n5. The Ollama connector should be selected\r\n6. Send a message to LLM (for example \"hello world\")\r\n\r\nExpected: there should be no errors saying `ActionsClientChatOpenAI: an\r\nerror occurred while running the action - Unexpected API Error: - 404\r\nmodel \"gpt-4o\" not found, try pulling it first`","sha":"7e4e8592f45ceca822c4f34d18e9f047cfe3cde0","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","Team: SecuritySolution","Team:Security Generative AI","backport:version","v8.18.0","v8.16.3","v8.17.1"],"title":"[Security Solution] AI Assistant: LLM Connector model chooser bug. New chat does not use connector's model (#199303)","number":204014,"url":"https://github.com/elastic/kibana/pull/204014","mergeCommit":{"message":"[Security Solution] AI Assistant: LLM Connector model chooser bug. New chat does not use connector's model (#199303) (#204014)\n\n## Summary\r\n\r\nThe PR fixes [this bug](https://github.com/elastic/kibana/issues/199303)\r\n\r\nThe issue happens with some of the locally setup LLMs (like\r\n[Ollama](https://github.com/ollama/ollama)) which requires the correct\r\n`model` to be passed as part of the [chat completions\r\nAPI](https://github.com/ollama/ollama/blob/main/docs/api.md#generate-a-chat-completion).\r\n\r\nWe had a bug in our code when on new conversation creation we would not\r\npass all the connectors configuration and only `connectorId` and\r\n`actionTypeId` would be passed. Here is the old code implementation:\r\n\r\n```\r\nconst newConversation = await createConversation({\r\n title: NEW_CHAT,\r\n ...(currentConversation?.apiConfig != null &&\r\n currentConversation?.apiConfig?.actionTypeId != null\r\n ? {\r\n apiConfig: {\r\n connectorId: currentConversation.apiConfig.connectorId,\r\n actionTypeId: currentConversation.apiConfig.actionTypeId,\r\n ...(newSystemPrompt?.id != null ? { defaultSystemPromptId: newSystemPrompt.id } : {}),\r\n },\r\n }\r\n : {}),\r\n});\r\n```\r\n\r\nand thus the new conversation would not have the complete connector\r\nconfiguration which would cause to use default model (`gpt-4o`) as a\r\nmodel we pass to the LLM.\r\n\r\nAlso, I updated the default body that we use on the Test connector page,\r\nto make sure that we send a model parameter to the LLM in case of `Open\r\nAI > Other (OpenAI Compatible Service)` kind of connectors.\r\n\r\n### Testing notes\r\n\r\nSteps to reproduce:\r\n1. Install\r\n[Ollama](https://github.com/ollama/ollama?tab=readme-ov-file#ollama)\r\nlocally\r\n2. Setup an OpenAI connector using Other (OpenAI Compatible Service)\r\nprovider\r\n3. Open AI Assistant and select created Ollama connector to chat\r\n4. Create a \"New Chat\"\r\n5. The Ollama connector should be selected\r\n6. Send a message to LLM (for example \"hello world\")\r\n\r\nExpected: there should be no errors saying `ActionsClientChatOpenAI: an\r\nerror occurred while running the action - Unexpected API Error: - 404\r\nmodel \"gpt-4o\" not found, try pulling it first`","sha":"7e4e8592f45ceca822c4f34d18e9f047cfe3cde0"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.16","8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/204014","number":204014,"mergeCommit":{"message":"[Security Solution] AI Assistant: LLM Connector model chooser bug. New chat does not use connector's model (#199303) (#204014)\n\n## Summary\r\n\r\nThe PR fixes [this bug](https://github.com/elastic/kibana/issues/199303)\r\n\r\nThe issue happens with some of the locally setup LLMs (like\r\n[Ollama](https://github.com/ollama/ollama)) which requires the correct\r\n`model` to be passed as part of the [chat completions\r\nAPI](https://github.com/ollama/ollama/blob/main/docs/api.md#generate-a-chat-completion).\r\n\r\nWe had a bug in our code when on new conversation creation we would not\r\npass all the connectors configuration and only `connectorId` and\r\n`actionTypeId` would be passed. Here is the old code implementation:\r\n\r\n```\r\nconst newConversation = await createConversation({\r\n title: NEW_CHAT,\r\n ...(currentConversation?.apiConfig != null &&\r\n currentConversation?.apiConfig?.actionTypeId != null\r\n ? {\r\n apiConfig: {\r\n connectorId: currentConversation.apiConfig.connectorId,\r\n actionTypeId: currentConversation.apiConfig.actionTypeId,\r\n ...(newSystemPrompt?.id != null ? { defaultSystemPromptId: newSystemPrompt.id } : {}),\r\n },\r\n }\r\n : {}),\r\n});\r\n```\r\n\r\nand thus the new conversation would not have the complete connector\r\nconfiguration which would cause to use default model (`gpt-4o`) as a\r\nmodel we pass to the LLM.\r\n\r\nAlso, I updated the default body that we use on the Test connector page,\r\nto make sure that we send a model parameter to the LLM in case of `Open\r\nAI > Other (OpenAI Compatible Service)` kind of connectors.\r\n\r\n### Testing notes\r\n\r\nSteps to reproduce:\r\n1. Install\r\n[Ollama](https://github.com/ollama/ollama?tab=readme-ov-file#ollama)\r\nlocally\r\n2. Setup an OpenAI connector using Other (OpenAI Compatible Service)\r\nprovider\r\n3. Open AI Assistant and select created Ollama connector to chat\r\n4. Create a \"New Chat\"\r\n5. The Ollama connector should be selected\r\n6. Send a message to LLM (for example \"hello world\")\r\n\r\nExpected: there should be no errors saying `ActionsClientChatOpenAI: an\r\nerror occurred while running the action - Unexpected API Error: - 404\r\nmodel \"gpt-4o\" not found, try pulling it first`","sha":"7e4e8592f45ceca822c4f34d18e9f047cfe3cde0"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Ievgen Sorokopud <ievgen.sorokopud@elastic.co> |
||
Devin W. Hurley
|
d2dd29eb85
|
[8.16] [Security Solution] Fixes exception item comment validation on newline chars \n (#202063) (#203709)
# Backport This will backport the following commits from `main` to `8.16`: - [[Security Solution] Fixes exception item comment validation on newline chars `\n` (#202063)](https://github.com/elastic/kibana/pull/202063) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Devin W. Hurley","email":"devin.hurley@elastic.co"},"sourceCommit":{"committedDate":"2024-12-10T22:19:32Z","message":"[Security Solution] Fixes exception item comment validation on newline chars `\\n` (#202063)\n\n## Summary\r\n\r\nFixes: https://github.com/elastic/kibana/issues/201820\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"35aeac104359eae81a233d0b8a9acaa97119d006","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","review","release_note:fix","v9.0.0","Team:Detections and Resp","Feature:Rule Exceptions","backport:version","v8.18.0","v8.16.2","v8.17.1"],"number":202063,"url":"https://github.com/elastic/kibana/pull/202063","mergeCommit":{"message":"[Security Solution] Fixes exception item comment validation on newline chars `\\n` (#202063)\n\n## Summary\r\n\r\nFixes: https://github.com/elastic/kibana/issues/201820\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"35aeac104359eae81a233d0b8a9acaa97119d006"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.16","8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202063","number":202063,"mergeCommit":{"message":"[Security Solution] Fixes exception item comment validation on newline chars `\\n` (#202063)\n\n## Summary\r\n\r\nFixes: https://github.com/elastic/kibana/issues/201820\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"35aeac104359eae81a233d0b8a9acaa97119d006"}},{"branch":"8.x","label":"v8.18.0","labelRegex":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
43f84bb5c9
|
[8.16] [SLOs] Added $state into filters schema !! (#202887) (#203055)
# Backport This will backport the following commits from `main` to `8.16`: - [[SLOs] Added $state into filters schema !! (#202887)](https://github.com/elastic/kibana/pull/202887) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Shahzad","email":"shahzad31comp@gmail.com"},"sourceCommit":{"committedDate":"2024-12-05T09:12:48Z","message":"[SLOs] Added $state into filters schema !! (#202887)\n\n## Summary\r\n\r\nfixes https://github.com/elastic/kibana/issues/202999\r\n\r\nAdded $state into filters schema !!","sha":"51e63eeaccd9998d473ef62d11d530697a836e7f","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-major"],"title":"[SLOs] Added $state into filters schema !!","number":202887,"url":"https://github.com/elastic/kibana/pull/202887","mergeCommit":{"message":"[SLOs] Added $state into filters schema !! (#202887)\n\n## Summary\r\n\r\nfixes https://github.com/elastic/kibana/issues/202999\r\n\r\nAdded $state into filters schema !!","sha":"51e63eeaccd9998d473ef62d11d530697a836e7f"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202887","number":202887,"mergeCommit":{"message":"[SLOs] Added $state into filters schema !! (#202887)\n\n## Summary\r\n\r\nfixes https://github.com/elastic/kibana/issues/202999\r\n\r\nAdded $state into filters schema !!","sha":"51e63eeaccd9998d473ef62d11d530697a836e7f"}}]}] BACKPORT--> Co-authored-by: Shahzad <shahzad31comp@gmail.com> |
||
|
Kibana Machine
|
f8edfb029b
|
[8.16] [Security solution] Fix gemini streaming (#201299) (#201372) | ||
Karen Grigoryan
|
b900fa0cab
|
[8.16] [Security Solution][Data Quality Dashboard][Serverless] add start/end time support for latest_results (#199248) (#200635)
# Backport This will backport the following commits from `main` to `8.16`: - [[Security Solution][Data Quality Dashboard][Serverless] add start/end time support for latest_results (#199248)](https://github.com/elastic/kibana/pull/199248) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Karen Grigoryan","email":"karen.grigoryan@elastic.co"},"sourceCommit":{"committedDate":"2024-11-07T17:42:31Z","message":"[Security Solution][Data Quality Dashboard][Serverless] add start/end time support for latest_results (#199248)\n\naddresses #191053\r\n\r\n- Introduce `defaultStartTime` and `defaultEndTime` props across data\r\nquality context and panels for fetching latest_results and align them\r\nwith serverless default time range of last week\r\n- Update hooks to handle new time parameters and include them in storage\r\nresults queries.\r\n- Modify server-side helpers and routes to process and filter indices\r\nbased on the provided time range.\r\n- Update related tests to accommodate the new time parameters.","sha":"1df04aef8d5859507c85a2ad37594075e9054b70","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Threat Hunting","Team:Threat Hunting:Explore","backport:prev-minor","ci:cloud-deploy","ci:project-deploy-security","v8.17.0"],"number":199248,"url":"https://github.com/elastic/kibana/pull/199248","mergeCommit":{"message":"[Security Solution][Data Quality Dashboard][Serverless] add start/end time support for latest_results (#199248)\n\naddresses #191053\r\n\r\n- Introduce `defaultStartTime` and `defaultEndTime` props across data\r\nquality context and panels for fetching latest_results and align them\r\nwith serverless default time range of last week\r\n- Update hooks to handle new time parameters and include them in storage\r\nresults queries.\r\n- Modify server-side helpers and routes to process and filter indices\r\nbased on the provided time range.\r\n- Update related tests to accommodate the new time parameters.","sha":"1df04aef8d5859507c85a2ad37594075e9054b70"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/199248","number":199248,"mergeCommit":{"message":"[Security Solution][Data Quality Dashboard][Serverless] add start/end time support for latest_results (#199248)\n\naddresses #191053\r\n\r\n- Introduce `defaultStartTime` and `defaultEndTime` props across data\r\nquality context and panels for fetching latest_results and align them\r\nwith serverless default time range of last week\r\n- Update hooks to handle new time parameters and include them in storage\r\nresults queries.\r\n- Modify server-side helpers and routes to process and filter indices\r\nbased on the provided time range.\r\n- Update related tests to accommodate the new time parameters.","sha":"1df04aef8d5859507c85a2ad37594075e9054b70"}},{"branch":"8.x","label":"v8.17.0","labelRegex":"^v8.17.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/199385","number":199385,"state":"MERGED","mergeCommit":{"sha":"de09e3af76d4bd1ce029830bd866e20b46e3aa9e","message":"[8.x] [Security Solution][Data Quality Dashboard][Serverless] add start/end time support for latest_results (#199248) (#199385)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[Security Solution][Data Quality Dashboard][Serverless] add start/end\ntime support for latest_results\n(#199248)](https://github.com/elastic/kibana/pull/199248)\n\n<!--- Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Karen\nGrigoryan\",\"email\":\"karen.grigoryan@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2024-11-07T17:42:31Z\",\"message\":\"[Security\nSolution][Data Quality Dashboard][Serverless] add start/end time support\nfor latest_results (#199248)\\n\\naddresses #191053\\r\\n\\r\\n- Introduce\n`defaultStartTime` and `defaultEndTime` props across data\\r\\nquality\ncontext and panels for fetching latest_results and align them\\r\\nwith\nserverless default time range of last week\\r\\n- Update hooks to handle\nnew time parameters and include them in storage\\r\\nresults queries.\\r\\n-\nModify server-side helpers and routes to process and filter\nindices\\r\\nbased on the provided time range.\\r\\n- Update related tests\nto accommodate the new time\nparameters.\",\"sha\":\"1df04aef8d5859507c85a2ad37594075e9054b70\",\"branchLabelMapping\":{\"^v9.0.0$\":\"main\",\"^v8.17.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"release_note:skip\",\"v9.0.0\",\"Team:Threat\nHunting\",\"Team:Threat\nHunting:Explore\",\"backport:prev-minor\",\"ci:cloud-deploy\",\"ci:project-deploy-security\"],\"title\":\"[Security\nSolution][Data Quality Dashboard][Serverless] add start/end time support\nfor\nlatest_results\",\"number\":199248,\"url\":\"https://github.com/elastic/kibana/pull/199248\",\"mergeCommit\":{\"message\":\"[Security\nSolution][Data Quality Dashboard][Serverless] add start/end time support\nfor latest_results (#199248)\\n\\naddresses #191053\\r\\n\\r\\n- Introduce\n`defaultStartTime` and `defaultEndTime` props across data\\r\\nquality\ncontext and panels for fetching latest_results and align them\\r\\nwith\nserverless default time range of last week\\r\\n- Update hooks to handle\nnew time parameters and include them in storage\\r\\nresults queries.\\r\\n-\nModify server-side helpers and routes to process and filter\nindices\\r\\nbased on the provided time range.\\r\\n- Update related tests\nto accommodate the new time\nparameters.\",\"sha\":\"1df04aef8d5859507c85a2ad37594075e9054b70\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[],\"targetPullRequestStates\":[{\"branch\":\"main\",\"label\":\"v9.0.0\",\"branchLabelMappingKey\":\"^v9.0.0$\",\"isSourceBranch\":true,\"state\":\"MERGED\",\"url\":\"https://github.com/elastic/kibana/pull/199248\",\"number\":199248,\"mergeCommit\":{\"message\":\"[Security\nSolution][Data Quality Dashboard][Serverless] add start/end time support\nfor latest_results (#199248)\\n\\naddresses #191053\\r\\n\\r\\n- Introduce\n`defaultStartTime` and `defaultEndTime` props across data\\r\\nquality\ncontext and panels for fetching latest_results and align them\\r\\nwith\nserverless default time range of last week\\r\\n- Update hooks to handle\nnew time parameters and include them in storage\\r\\nresults queries.\\r\\n-\nModify server-side helpers and routes to process and filter\nindices\\r\\nbased on the provided time range.\\r\\n- Update related tests\nto accommodate the new time\nparameters.\",\"sha\":\"1df04aef8d5859507c85a2ad37594075e9054b70\"}}]}]\nBACKPORT-->\n\nCo-authored-by: Karen Grigoryan <karen.grigoryan@elastic.co>"}}]}] BACKPORT--> |
||
|
Karen Grigoryan
|
8869d3dce4
|
[8.16] [Security Solution][Data Quality Dashboard] fix pattern state reset on ilm phase filter change (#198549) (#200618)
# Backport This will backport the following commits from `main` to `8.16`: - [[Security Solution][Data Quality Dashboard] fix pattern state reset on ilm phase filter change (#198549)](https://github.com/elastic/kibana/pull/198549) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Karen Grigoryan","email":"karen.grigoryan@elastic.co"},"sourceCommit":{"committedDate":"2024-11-04T15:09:12Z","message":"[Security Solution][Data Quality Dashboard] fix pattern state reset on ilm phase filter change (#198549)\n\naddresses #196523\r\n\r\n- Fixes ilm phase change propagation on patterns.\r\n- Adds missing tests for useResultsRollup functionality\r\n\r\n## UI changes\r\n\r\n### Before\r\n\r\nhttps://github.com/user-attachments/assets/78a1d809-6a9a-4bfc-88a9-079f829a2017\r\n\r\n### After\r\n\r\nhttps://github.com/user-attachments/assets/f689fcc9-e1c6-4ccf-a7ca-8f13e9507ba4","sha":"ddf55ea3a79ad7439dc02cb1f93291b1bc95c3b9","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Threat Hunting","Team:Threat Hunting:Explore","backport:prev-minor","ci:cloud-deploy","ci:project-deploy-security","v8.17.0"],"number":198549,"url":"https://github.com/elastic/kibana/pull/198549","mergeCommit":{"message":"[Security Solution][Data Quality Dashboard] fix pattern state reset on ilm phase filter change (#198549)\n\naddresses #196523\r\n\r\n- Fixes ilm phase change propagation on patterns.\r\n- Adds missing tests for useResultsRollup functionality\r\n\r\n## UI changes\r\n\r\n### Before\r\n\r\nhttps://github.com/user-attachments/assets/78a1d809-6a9a-4bfc-88a9-079f829a2017\r\n\r\n### After\r\n\r\nhttps://github.com/user-attachments/assets/f689fcc9-e1c6-4ccf-a7ca-8f13e9507ba4","sha":"ddf55ea3a79ad7439dc02cb1f93291b1bc95c3b9"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/198549","number":198549,"mergeCommit":{"message":"[Security Solution][Data Quality Dashboard] fix pattern state reset on ilm phase filter change (#198549)\n\naddresses #196523\r\n\r\n- Fixes ilm phase change propagation on patterns.\r\n- Adds missing tests for useResultsRollup functionality\r\n\r\n## UI changes\r\n\r\n### Before\r\n\r\nhttps://github.com/user-attachments/assets/78a1d809-6a9a-4bfc-88a9-079f829a2017\r\n\r\n### After\r\n\r\nhttps://github.com/user-attachments/assets/f689fcc9-e1c6-4ccf-a7ca-8f13e9507ba4","sha":"ddf55ea3a79ad7439dc02cb1f93291b1bc95c3b9"}},{"branch":"8.x","label":"v8.17.0","labelRegex":"^v8.17.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/198806","number":198806,"state":"MERGED","mergeCommit":{"sha":"fa0bddaac166c1bd17989a54b183677203f1812b","message":"[8.x] [Security Solution][Data Quality Dashboard] fix pattern state reset on ilm phase filter change (#198549) (#198806)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[Security Solution][Data Quality Dashboard] fix pattern state reset\non ilm phase filter change\n(#198549)](https://github.com/elastic/kibana/pull/198549)\n\n<!--- Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Karen\nGrigoryan\",\"email\":\"karen.grigoryan@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2024-11-04T15:09:12Z\",\"message\":\"[Security\nSolution][Data Quality Dashboard] fix pattern state reset on ilm phase\nfilter change (#198549)\\n\\naddresses #196523\\r\\n\\r\\n- Fixes ilm phase\nchange propagation on patterns.\\r\\n- Adds missing tests for\nuseResultsRollup functionality\\r\\n\\r\\n## UI changes\\r\\n\\r\\n###\nBefore\\r\\n\\r\\n |
||
|
Karen Grigoryan
|
d23bd9913b
|
[8.16] [Security Solution][Data Quality Dashboard] fix tests and potential tests timing out on ci (#196591) (#200549)
# Backport This will backport the following commits from `main` to `8.16`: - [[Security Solution][Data Quality Dashboard] fix tests and potential tests timing out on ci (#196591)](https://github.com/elastic/kibana/pull/196591) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Karen Grigoryan","email":"karen.grigoryan@elastic.co"},"sourceCommit":{"committedDate":"2024-11-01T18:59:41Z","message":"[Security Solution][Data Quality Dashboard] fix tests and potential tests timing out on ci (#196591)\n\naddresses #196216\r\n\r\nRemoving accessibility selectors to ensure 10x speed of tests with\r\ndata-test-subj locators.","sha":"b5a705e54cd9c657064cc67f8cf1b72f4324d3ab","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Threat Hunting","Team:Threat Hunting:Explore","backport:prev-minor","v8.17.0"],"number":196591,"url":"https://github.com/elastic/kibana/pull/196591","mergeCommit":{"message":"[Security Solution][Data Quality Dashboard] fix tests and potential tests timing out on ci (#196591)\n\naddresses #196216\r\n\r\nRemoving accessibility selectors to ensure 10x speed of tests with\r\ndata-test-subj locators.","sha":"b5a705e54cd9c657064cc67f8cf1b72f4324d3ab"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/196591","number":196591,"mergeCommit":{"message":"[Security Solution][Data Quality Dashboard] fix tests and potential tests timing out on ci (#196591)\n\naddresses #196216\r\n\r\nRemoving accessibility selectors to ensure 10x speed of tests with\r\ndata-test-subj locators.","sha":"b5a705e54cd9c657064cc67f8cf1b72f4324d3ab"}},{"branch":"8.x","label":"v8.17.0","labelRegex":"^v8.17.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/198717","number":198717,"state":"MERGED","mergeCommit":{"sha":"273a1eef0fb2f3c717f9fff8be2097892b8b8b90","message":"[8.x] [Security Solution][Data Quality Dashboard] fix tests and potential tests timing out on ci (#196591) (#198717)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[Security Solution][Data Quality Dashboard] fix tests and potential\ntests timing out on ci\n(#196591)](https://github.com/elastic/kibana/pull/196591)\n\n<!--- Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Karen\nGrigoryan\",\"email\":\"karen.grigoryan@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2024-11-01T18:59:41Z\",\"message\":\"[Security\nSolution][Data Quality Dashboard] fix tests and potential tests timing\nout on ci (#196591)\\n\\naddresses #196216\\r\\n\\r\\nRemoving accessibility\nselectors to ensure 10x speed of tests with\\r\\ndata-test-subj\nlocators.\",\"sha\":\"b5a705e54cd9c657064cc67f8cf1b72f4324d3ab\",\"branchLabelMapping\":{\"^v9.0.0$\":\"main\",\"^v8.17.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"release_note:skip\",\"v9.0.0\",\"Team:Threat\nHunting\",\"Team:Threat\nHunting:Explore\",\"backport:prev-minor\"],\"title\":\"[Security\nSolution][Data Quality Dashboard] fix tests and potential tests timing\nout on\nci\",\"number\":196591,\"url\":\"https://github.com/elastic/kibana/pull/196591\",\"mergeCommit\":{\"message\":\"[Security\nSolution][Data Quality Dashboard] fix tests and potential tests timing\nout on ci (#196591)\\n\\naddresses #196216\\r\\n\\r\\nRemoving accessibility\nselectors to ensure 10x speed of tests with\\r\\ndata-test-subj\nlocators.\",\"sha\":\"b5a705e54cd9c657064cc67f8cf1b72f4324d3ab\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[],\"targetPullRequestStates\":[{\"branch\":\"main\",\"label\":\"v9.0.0\",\"branchLabelMappingKey\":\"^v9.0.0$\",\"isSourceBranch\":true,\"state\":\"MERGED\",\"url\":\"https://github.com/elastic/kibana/pull/196591\",\"number\":196591,\"mergeCommit\":{\"message\":\"[Security\nSolution][Data Quality Dashboard] fix tests and potential tests timing\nout on ci (#196591)\\n\\naddresses #196216\\r\\n\\r\\nRemoving accessibility\nselectors to ensure 10x speed of tests with\\r\\ndata-test-subj\nlocators.\",\"sha\":\"b5a705e54cd9c657064cc67f8cf1b72f4324d3ab\"}}]}]\nBACKPORT-->\n\nCo-authored-by: Karen Grigoryan <karen.grigoryan@elastic.co>"}}]}] BACKPORT--> |
||
Andrew Macri
|
58dd0876a4
|
[8.16] [Security Solution] [Attack discovery] Additional Attack discovery tests (#199659) (#200066)
# Backport This will backport the following commits from `main` to `8.16`: - [[Security Solution] [Attack discovery] Additional Attack discovery tests (#199659)](https://github.com/elastic/kibana/pull/199659) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Andrew Macri","email":"andrew.macri@elastic.co"},"sourceCommit":{"committedDate":"2024-11-13T17:37:54Z","message":"[Security Solution] [Attack discovery] Additional Attack discovery tests (#199659)\n\n### [Security Solution] [Attack discovery] Additional Attack discovery tests\r\n\r\nThis PR adds additional unit test coverage to Attack discovery.","sha":"53d4580a8959a9e4b166df4e4a4cc83de61f7928","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team: SecuritySolution","Team:Security Generative AI","backport:version","v8.17.0","v8.16.1"],"number":199659,"url":"https://github.com/elastic/kibana/pull/199659","mergeCommit":{"message":"[Security Solution] [Attack discovery] Additional Attack discovery tests (#199659)\n\n### [Security Solution] [Attack discovery] Additional Attack discovery tests\r\n\r\nThis PR adds additional unit test coverage to Attack discovery.","sha":"53d4580a8959a9e4b166df4e4a4cc83de61f7928"}},"sourceBranch":"main","suggestedTargetBranches":["8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/199659","number":199659,"mergeCommit":{"message":"[Security Solution] [Attack discovery] Additional Attack discovery tests (#199659)\n\n### [Security Solution] [Attack discovery] Additional Attack discovery tests\r\n\r\nThis PR adds additional unit test coverage to Attack discovery.","sha":"53d4580a8959a9e4b166df4e4a4cc83de61f7928"}},{"branch":"8.x","label":"v8.17.0","labelRegex":"^v8.17.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/200061","number":200061,"state":"OPEN"},{"branch":"8.16","label":"v8.16.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
e1acc72d92
|
[8.16] [Security solution] Knowledge base entry telemetry (#199225) (#199723)
# Backport This will backport the following commits from `main` to `8.16`: - [[Security solution] Knowledge base entry telemetry (#199225)](https://github.com/elastic/kibana/pull/199225) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Steph Milovic","email":"stephanie.milovic@elastic.co"},"sourceCommit":{"committedDate":"2024-11-12T00:10:07Z","message":"[Security solution] Knowledge base entry telemetry (#199225)","sha":"1127bf491d78b7ce2319a13257dbf0b1e84226e8","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["WIP","release_note:skip","v9.0.0","Team: SecuritySolution","Team:Security Generative AI","backport:version","v8.17.0","v8.16.1"],"title":"[Security solution] Knowledge base entry telemetry","number":199225,"url":"https://github.com/elastic/kibana/pull/199225","mergeCommit":{"message":"[Security solution] Knowledge base entry telemetry (#199225)","sha":"1127bf491d78b7ce2319a13257dbf0b1e84226e8"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/199225","number":199225,"mergeCommit":{"message":"[Security solution] Knowledge base entry telemetry (#199225)","sha":"1127bf491d78b7ce2319a13257dbf0b1e84226e8"}},{"branch":"8.x","label":"v8.17.0","branchLabelMappingKey":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Steph Milovic <stephanie.milovic@elastic.co> |
||
|
Kibana Machine
|
c9292405ee
|
[8.16] [Cloud Security] Fixes SVG flickering and adding insight telemetry (#198812) (#199141)
# Backport This will backport the following commits from `main` to `8.16`: - [[Cloud Security] Fixes SVG flickering and adding insight telemetry (#198812)](https://github.com/elastic/kibana/pull/198812) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Jordan","email":"51442161+JordanSh@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-11-06T13:52:30Z","message":"[Cloud Security] Fixes SVG flickering and adding insight telemetry (#198812)","sha":"de46e7f0739eb14138655e204d4be77d8e24ff37","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Cloud Security","backport:prev-minor","v8.16.0","backport:version","v8.17.0"],"title":"[Cloud Security] Fixes SVG flickering and adding insight telemetry","number":198812,"url":"https://github.com/elastic/kibana/pull/198812","mergeCommit":{"message":"[Cloud Security] Fixes SVG flickering and adding insight telemetry (#198812)","sha":"de46e7f0739eb14138655e204d4be77d8e24ff37"}},"sourceBranch":"main","suggestedTargetBranches":["8.16","8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/198812","number":198812,"mergeCommit":{"message":"[Cloud Security] Fixes SVG flickering and adding insight telemetry (#198812)","sha":"de46e7f0739eb14138655e204d4be77d8e24ff37"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.17.0","branchLabelMappingKey":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Jordan <51442161+JordanSh@users.noreply.github.com> |
||
|
Kibana Machine
|
9b18b75f33
|
[8.16] [Security Solution][Bug] Incorrect message as Duplicate entry? shown on creating New Knowledge Base index. (#198892) (#199045) (#199062)
# Backport This will backport the following commits from `main` to `8.16`: - [[Security Solution][Bug] Incorrect message as Duplicate entry? shown on creating New Knowledge Base index. (#198892) (#199045)](https://github.com/elastic/kibana/pull/199045) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Ievgen Sorokopud","email":"ievgen.sorokopud@elastic.co"},"sourceCommit":{"committedDate":"2024-11-05T21:57:30Z","message":"[Security Solution][Bug] Incorrect message as Duplicate entry? shown on creating New Knowledge Base index. (#198892) (#199045)\n\n## Summary\r\n\r\nBUG: https://github.com/elastic/kibana/issues/198892\r\n\r\nThis PR fixes the BUG where we would show `Duplicate entry?`\r\nconfirmation modal on new document creation. This happens because the\r\nstate is not being reset properly on flyout close and we use previous\r\nvalues in the new entry creation flow.\r\n\r\n### To test\r\n\r\n1. Create a global entry (document or index)\r\n2. Edit the entry from 1\r\n3. Switch global to private\r\n4. Save entry => This will trigger `Duplicate entry?` confirmation modal\r\n(save it)\r\n5. Press `New > Index/Document`\r\n6. Fill out required fields\r\n7. Press `Save` button\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"8ebe78857b11a20f4be5cdfbeb6b38897f270f19","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team: SecuritySolution","Team:Security Generative AI","v8.16.0","backport:version","v8.17.0"],"title":"[Security Solution][Bug] Incorrect message as Duplicate entry? shown on creating New Knowledge Base index. (#198892)","number":199045,"url":"https://github.com/elastic/kibana/pull/199045","mergeCommit":{"message":"[Security Solution][Bug] Incorrect message as Duplicate entry? shown on creating New Knowledge Base index. (#198892) (#199045)\n\n## Summary\r\n\r\nBUG: https://github.com/elastic/kibana/issues/198892\r\n\r\nThis PR fixes the BUG where we would show `Duplicate entry?`\r\nconfirmation modal on new document creation. This happens because the\r\nstate is not being reset properly on flyout close and we use previous\r\nvalues in the new entry creation flow.\r\n\r\n### To test\r\n\r\n1. Create a global entry (document or index)\r\n2. Edit the entry from 1\r\n3. Switch global to private\r\n4. Save entry => This will trigger `Duplicate entry?` confirmation modal\r\n(save it)\r\n5. Press `New > Index/Document`\r\n6. Fill out required fields\r\n7. Press `Save` button\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"8ebe78857b11a20f4be5cdfbeb6b38897f270f19"}},"sourceBranch":"main","suggestedTargetBranches":["8.16","8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/199045","number":199045,"mergeCommit":{"message":"[Security Solution][Bug] Incorrect message as Duplicate entry? shown on creating New Knowledge Base index. (#198892) (#199045)\n\n## Summary\r\n\r\nBUG: https://github.com/elastic/kibana/issues/198892\r\n\r\nThis PR fixes the BUG where we would show `Duplicate entry?`\r\nconfirmation modal on new document creation. This happens because the\r\nstate is not being reset properly on flyout close and we use previous\r\nvalues in the new entry creation flow.\r\n\r\n### To test\r\n\r\n1. Create a global entry (document or index)\r\n2. Edit the entry from 1\r\n3. Switch global to private\r\n4. Save entry => This will trigger `Duplicate entry?` confirmation modal\r\n(save it)\r\n5. Press `New > Index/Document`\r\n6. Fill out required fields\r\n7. Press `Save` button\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"8ebe78857b11a20f4be5cdfbeb6b38897f270f19"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.17.0","branchLabelMappingKey":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Ievgen Sorokopud <ievgen.sorokopud@elastic.co> |
||
|
Kibana Machine
|
563c7f1193
|
[8.16] [Security GenAI][BUG] Knowledge Base: Show only indices with `semantic_text` fields (#198707) (#198906)
# Backport This will backport the following commits from `main` to `8.16`: - [[Security GenAI][BUG] Knowledge Base: Show only indices with `semantic_text` fields (#198707)](https://github.com/elastic/kibana/pull/198707) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Ievgen Sorokopud","email":"ievgen.sorokopud@elastic.co"},"sourceCommit":{"committedDate":"2024-11-05T10:12:33Z","message":"[Security GenAI][BUG] Knowledge Base: Show only indices with `semantic_text` fields (#198707)\n\n## Summary\r\n\r\nThis is a fix the next issue:\r\n\r\n> Index input should only list indices with semantic_text fields, not\r\nall indices.\r\n\r\n### Current behaviour\r\n\r\nWe show all available indices\r\n\r\n<img width=\"1311\" alt=\"Screenshot 2024-11-01 at 18 14 36\"\r\nsrc=\"https://github.com/user-attachments/assets/cf9d08fd-a809-4530-b653-d12b8e643e45\">\r\n\r\n### Behaviour after the fix\r\n\r\nWe show only indices with `semantic_text` fields\r\n\r\n<img width=\"1311\" alt=\"Screenshot 2024-11-01 at 18 08 29\"\r\nsrc=\"https://github.com/user-attachments/assets/864b5552-aece-4cc6-848a-8f73f88f55dc\">\r\n\r\n### Testing notes\r\n\r\nCreate some indices with `semantic_text` fields. For example, you can do\r\nthat via uploading and indexing a PDF file:\r\n\r\n1. Navigate to Integrations page\r\n2. Select \"Upload a file\"\r\n3. Select and upload a PDF file\r\n4. Press Import button\r\n5. Switch to Advanced tab\r\n6. Fill in \"Index name\"\r\n7. Add additional field > Add semantic text field > Fill in form\r\n * Field: `attachment.content`\r\n * Copy to field: `content`\r\n * Inference endpoint: `elser_model_2`\r\n8. Press Add button\r\n9. Press Import button\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"b122722d886b66431108a33d0eac2447a63da179","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team: SecuritySolution","Team:Security Generative AI","backport:version","v8.17.0","v8.16.1"],"title":"[Security GenAI][BUG] Knowledge Base: Show only indices with `semantic_text` fields","number":198707,"url":"https://github.com/elastic/kibana/pull/198707","mergeCommit":{"message":"[Security GenAI][BUG] Knowledge Base: Show only indices with `semantic_text` fields (#198707)\n\n## Summary\r\n\r\nThis is a fix the next issue:\r\n\r\n> Index input should only list indices with semantic_text fields, not\r\nall indices.\r\n\r\n### Current behaviour\r\n\r\nWe show all available indices\r\n\r\n<img width=\"1311\" alt=\"Screenshot 2024-11-01 at 18 14 36\"\r\nsrc=\"https://github.com/user-attachments/assets/cf9d08fd-a809-4530-b653-d12b8e643e45\">\r\n\r\n### Behaviour after the fix\r\n\r\nWe show only indices with `semantic_text` fields\r\n\r\n<img width=\"1311\" alt=\"Screenshot 2024-11-01 at 18 08 29\"\r\nsrc=\"https://github.com/user-attachments/assets/864b5552-aece-4cc6-848a-8f73f88f55dc\">\r\n\r\n### Testing notes\r\n\r\nCreate some indices with `semantic_text` fields. For example, you can do\r\nthat via uploading and indexing a PDF file:\r\n\r\n1. Navigate to Integrations page\r\n2. Select \"Upload a file\"\r\n3. Select and upload a PDF file\r\n4. Press Import button\r\n5. Switch to Advanced tab\r\n6. Fill in \"Index name\"\r\n7. Add additional field > Add semantic text field > Fill in form\r\n * Field: `attachment.content`\r\n * Copy to field: `content`\r\n * Inference endpoint: `elser_model_2`\r\n8. Press Add button\r\n9. Press Import button\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"b122722d886b66431108a33d0eac2447a63da179"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/198707","number":198707,"mergeCommit":{"message":"[Security GenAI][BUG] Knowledge Base: Show only indices with `semantic_text` fields (#198707)\n\n## Summary\r\n\r\nThis is a fix the next issue:\r\n\r\n> Index input should only list indices with semantic_text fields, not\r\nall indices.\r\n\r\n### Current behaviour\r\n\r\nWe show all available indices\r\n\r\n<img width=\"1311\" alt=\"Screenshot 2024-11-01 at 18 14 36\"\r\nsrc=\"https://github.com/user-attachments/assets/cf9d08fd-a809-4530-b653-d12b8e643e45\">\r\n\r\n### Behaviour after the fix\r\n\r\nWe show only indices with `semantic_text` fields\r\n\r\n<img width=\"1311\" alt=\"Screenshot 2024-11-01 at 18 08 29\"\r\nsrc=\"https://github.com/user-attachments/assets/864b5552-aece-4cc6-848a-8f73f88f55dc\">\r\n\r\n### Testing notes\r\n\r\nCreate some indices with `semantic_text` fields. For example, you can do\r\nthat via uploading and indexing a PDF file:\r\n\r\n1. Navigate to Integrations page\r\n2. Select \"Upload a file\"\r\n3. Select and upload a PDF file\r\n4. Press Import button\r\n5. Switch to Advanced tab\r\n6. Fill in \"Index name\"\r\n7. Add additional field > Add semantic text field > Fill in form\r\n * Field: `attachment.content`\r\n * Copy to field: `content`\r\n * Inference endpoint: `elser_model_2`\r\n8. Press Add button\r\n9. Press Import button\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"b122722d886b66431108a33d0eac2447a63da179"}},{"branch":"8.x","label":"v8.17.0","branchLabelMappingKey":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Ievgen Sorokopud <ievgen.sorokopud@elastic.co> |
||
|
Kibana Machine
|
cecf31daf0
|
[8.16] [Security GenAI] Fix and un-skip Knowledge Base Integration Tests (#198861) (#198889)
# Backport This will backport the following commits from `main` to `8.16`: - [[Security GenAI] Fix and un-skip Knowledge Base Integration Tests (#198861)](https://github.com/elastic/kibana/pull/198861) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Ievgen Sorokopud","email":"ievgen.sorokopud@elastic.co"},"sourceCommit":{"committedDate":"2024-11-05T07:40:59Z","message":"[Security GenAI] Fix and un-skip Knowledge Base Integration Tests (#198861)\n\n## Summary\r\n\r\nThis is a followup to https://github.com/elastic/kibana/pull/198178\r\nwhere we skipped KB integration tests. We enable it with this PR.\r\n\r\nSince it takes a lot of time to setup all Security Labs docs, the idea\r\nis to skip installing those docs when it is not needed. For these tests\r\nwe need to make sure that inference endpoint is setup correctly - labs\r\ndocs are not required in this case.\r\n\r\ncc @stephmilovic","sha":"69c1e5a7dda2708773dfeed2314b0ef74f4537ee","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team: SecuritySolution","Team:Security Generative AI","backport:version","v8.17.0","v8.16.1"],"title":"[Security GenAI] Fix and un-skip Knowledge Base Integration Tests","number":198861,"url":"https://github.com/elastic/kibana/pull/198861","mergeCommit":{"message":"[Security GenAI] Fix and un-skip Knowledge Base Integration Tests (#198861)\n\n## Summary\r\n\r\nThis is a followup to https://github.com/elastic/kibana/pull/198178\r\nwhere we skipped KB integration tests. We enable it with this PR.\r\n\r\nSince it takes a lot of time to setup all Security Labs docs, the idea\r\nis to skip installing those docs when it is not needed. For these tests\r\nwe need to make sure that inference endpoint is setup correctly - labs\r\ndocs are not required in this case.\r\n\r\ncc @stephmilovic","sha":"69c1e5a7dda2708773dfeed2314b0ef74f4537ee"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/198861","number":198861,"mergeCommit":{"message":"[Security GenAI] Fix and un-skip Knowledge Base Integration Tests (#198861)\n\n## Summary\r\n\r\nThis is a followup to https://github.com/elastic/kibana/pull/198178\r\nwhere we skipped KB integration tests. We enable it with this PR.\r\n\r\nSince it takes a lot of time to setup all Security Labs docs, the idea\r\nis to skip installing those docs when it is not needed. For these tests\r\nwe need to make sure that inference endpoint is setup correctly - labs\r\ndocs are not required in this case.\r\n\r\ncc @stephmilovic","sha":"69c1e5a7dda2708773dfeed2314b0ef74f4537ee"}},{"branch":"8.x","label":"v8.17.0","branchLabelMappingKey":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Ievgen Sorokopud <ievgen.sorokopud@elastic.co> |
||
|
Kibana Machine
|
ebe9f29b59
|
[8.16] fix(slo): Override transform _id to ensure uniqness (#198610) (#198699)
# Backport This will backport the following commits from `main` to `8.16`: - [fix(slo): Override transform _id to ensure uniqness (#198610)](https://github.com/elastic/kibana/pull/198610) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Kevin Delemme","email":"kevin.delemme@elastic.co"},"sourceCommit":{"committedDate":"2024-11-01T15:36:41Z","message":"fix(slo): Override transform _id to ensure uniqness (#198610)","sha":"98db4d6f75f05eba1682e0e903bf2d9c909b37f2","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","v9.0.0","backport:prev-minor","ci:project-deploy-observability","Team:obs-ux-management","v8.16.0"],"title":"fix(slo): Override transform _id to ensure uniqness","number":198610,"url":"https://github.com/elastic/kibana/pull/198610","mergeCommit":{"message":"fix(slo): Override transform _id to ensure uniqness (#198610)","sha":"98db4d6f75f05eba1682e0e903bf2d9c909b37f2"}},"sourceBranch":"main","suggestedTargetBranches":["8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/198610","number":198610,"mergeCommit":{"message":"fix(slo): Override transform _id to ensure uniqness (#198610)","sha":"98db4d6f75f05eba1682e0e903bf2d9c909b37f2"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Kevin Delemme <kevin.delemme@elastic.co> |
||
Tiago Vila Verde
|
931579bab9
|
[8.16] Backport: [eem] rename fields to snake case #195895 (#198501)
Backporting https://github.com/elastic/kibana/pull/195895 into 8.16. --------- Co-authored-by: Kevin Lacabane <kevin.lacabane@elastic.co> |
||
|
Tiago Vila Verde
|
90cff86879
|
[8.16] [EEM] Replace hashed ID with human readable ID (#193652) (#198494)
# Backport
This will backport the following commits from `main` to `8.16`:
- [EEM] Replace hashed ID with human readable ID (#193652) (
|
||
|
Kibana Machine
|
6014038100
|
[8.16] [Security solution] `assistantKnowledgeBaseByDefault` flag defaults to `true` (#198178) (#198458)
# Backport This will backport the following commits from `main` to `8.16`: - [[Security solution] `assistantKnowledgeBaseByDefault` flag defaults to `true` (#198178)](https://github.com/elastic/kibana/pull/198178) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Steph Milovic","email":"stephanie.milovic@elastic.co"},"sourceCommit":{"committedDate":"2024-10-31T02:36:14Z","message":"[Security solution] `assistantKnowledgeBaseByDefault` flag defaults to `true` (#198178)","sha":"88225fff07c416a6939c415d8ac65e473a3ffd0e","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team: SecuritySolution","Team:Security Generative AI","v8.16.0","backport:version","v8.17.0"],"title":"[Security solution] `assistantKnowledgeBaseByDefault` flag defaults to `true`","number":198178,"url":"https://github.com/elastic/kibana/pull/198178","mergeCommit":{"message":"[Security solution] `assistantKnowledgeBaseByDefault` flag defaults to `true` (#198178)","sha":"88225fff07c416a6939c415d8ac65e473a3ffd0e"}},"sourceBranch":"main","suggestedTargetBranches":["8.16","8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/198178","number":198178,"mergeCommit":{"message":"[Security solution] `assistantKnowledgeBaseByDefault` flag defaults to `true` (#198178)","sha":"88225fff07c416a6939c415d8ac65e473a3ffd0e"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.17.0","branchLabelMappingKey":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Steph Milovic <stephanie.milovic@elastic.co> |
||
Steph Milovic
|
f02d1303b5
|
[8.16] [Security AI Assistant] Fixed license issue for Knowledge Base resources initialization (#198239) (#198451)
# Backport This will backport the following commits from `main` to `8.16`: - [[Security AI Assistant] Fixed license issue for Knowledge Base resources initialization (#198239)](https://github.com/elastic/kibana/pull/198239) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Yuliia Naumenko","email":"jo.naumenko@gmail.com"},"sourceCommit":{"committedDate":"2024-10-30T21:13:33Z","message":"[Security AI Assistant] Fixed license issue for Knowledge Base resources initialization (#198239)","sha":"ed81e4334f4d5608517dacdba28d46dfea966be0","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","v9.0.0","v8.16.0","backport:version","v8.17.0","v8.15.4"],"number":198239,"url":"https://github.com/elastic/kibana/pull/198239","mergeCommit":{"message":"[Security AI Assistant] Fixed license issue for Knowledge Base resources initialization (#198239)","sha":"ed81e4334f4d5608517dacdba28d46dfea966be0"}},"sourceBranch":"main","suggestedTargetBranches":["8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/198239","number":198239,"mergeCommit":{"message":"[Security AI Assistant] Fixed license issue for Knowledge Base resources initialization (#198239)","sha":"ed81e4334f4d5608517dacdba28d46dfea966be0"}},{"branch":"8.16","label":"v8.16.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.17.0","labelRegex":"^v8.17.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/198447","number":198447,"state":"OPEN"},{"branch":"8.15","label":"v8.15.4","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/198449","number":198449,"state":"OPEN"}]}] BACKPORT--> Co-authored-by: Yuliia Naumenko <jo.naumenko@gmail.com> |
||
Patryk Kopyciński
|
2064a2c310
|
[8.16] [Security Assistant] Knowledge base switch to use semantic_text (#197007) (#198439)
# Backport This will backport the following commits from `main` to `8.16`: - [[Security Assistant] Knowledge base switch to use `semantic_text` (#197007)](https://github.com/elastic/kibana/pull/197007) <!--- Backport version: 8.9.8 --> ### 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":"2024-10-30T19:20:45Z","message":"[Security Assistant] Knowledge base switch to use `semantic_text` (#197007)\n\n## Summary\n\n- `text_expansion` is deprecated, use `semantic_text` instead\n- fix KB index entry form field options \n- explicitly create inference endpoint on KB setup if\n`assistantKnowledgeBaseByDefault` is true\n- when upgrade from v1 update KB ingest pipeline and remove unnecessary\nprocessor, but keep the pipeline for the backward compatibility\n- switch to use `doc` update for KB entries due to the limitations od\n`semantic_text`\nhttps://www.elastic.co/guide/en/elasticsearch/reference/current/semantic-text.html#update-script\n- split loading Security labs content into smaller chunks\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Pedro Jaramillo <pedro.jaramillo@elastic.co>","sha":"a8c54f2ea4f482285eda15c72c56da35d76a6719","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","v9.0.0","Feature:Security Assistant","ci:project-deploy-security","Team:Security Generative AI","v8.16.0","backport:version","v8.17.0"],"number":197007,"url":"https://github.com/elastic/kibana/pull/197007","mergeCommit":{"message":"[Security Assistant] Knowledge base switch to use `semantic_text` (#197007)\n\n## Summary\n\n- `text_expansion` is deprecated, use `semantic_text` instead\n- fix KB index entry form field options \n- explicitly create inference endpoint on KB setup if\n`assistantKnowledgeBaseByDefault` is true\n- when upgrade from v1 update KB ingest pipeline and remove unnecessary\nprocessor, but keep the pipeline for the backward compatibility\n- switch to use `doc` update for KB entries due to the limitations od\n`semantic_text`\nhttps://www.elastic.co/guide/en/elasticsearch/reference/current/semantic-text.html#update-script\n- split loading Security labs content into smaller chunks\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Pedro Jaramillo <pedro.jaramillo@elastic.co>","sha":"a8c54f2ea4f482285eda15c72c56da35d76a6719"}},"sourceBranch":"main","suggestedTargetBranches":["8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/197007","number":197007,"mergeCommit":{"message":"[Security Assistant] Knowledge base switch to use `semantic_text` (#197007)\n\n## Summary\n\n- `text_expansion` is deprecated, use `semantic_text` instead\n- fix KB index entry form field options \n- explicitly create inference endpoint on KB setup if\n`assistantKnowledgeBaseByDefault` is true\n- when upgrade from v1 update KB ingest pipeline and remove unnecessary\nprocessor, but keep the pipeline for the backward compatibility\n- switch to use `doc` update for KB entries due to the limitations od\n`semantic_text`\nhttps://www.elastic.co/guide/en/elasticsearch/reference/current/semantic-text.html#update-script\n- split loading Security labs content into smaller chunks\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Pedro Jaramillo <pedro.jaramillo@elastic.co>","sha":"a8c54f2ea4f482285eda15c72c56da35d76a6719"}},{"branch":"8.16","label":"v8.16.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.17.0","labelRegex":"^v8.17.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/198437","number":198437,"state":"OPEN"}]}] BACKPORT--> |
||
|
Kibana Machine
|
07ea8ebd81
|
[8.16] [AI Assistant] Add scopes telemetry to AI Assistant events (#197983) (#198359)
# Backport This will backport the following commits from `main` to `8.16`: - [[AI Assistant] Add scopes telemetry to AI Assistant events (#197983)](https://github.com/elastic/kibana/pull/197983) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Sander Philipse","email":"94373878+sphilipse@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-10-30T14:04:23Z","message":"[AI Assistant] Add scopes telemetry to AI Assistant events (#197983)\n\n## Summary\r\n\r\nThis adds telemetry to the Observability and Search assistant to judge\r\nwhether it's search or observability.","sha":"74cf0e4e2bd386ae38a6b8c537545acbd1707022","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Search","Team:Obs AI Assistant","ci:project-deploy-observability","v8.16.0","backport:version","v8.17.0"],"title":"[AI Assistant] Add scopes telemetry to AI Assistant events","number":197983,"url":"https://github.com/elastic/kibana/pull/197983","mergeCommit":{"message":"[AI Assistant] Add scopes telemetry to AI Assistant events (#197983)\n\n## Summary\r\n\r\nThis adds telemetry to the Observability and Search assistant to judge\r\nwhether it's search or observability.","sha":"74cf0e4e2bd386ae38a6b8c537545acbd1707022"}},"sourceBranch":"main","suggestedTargetBranches":["8.16","8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/197983","number":197983,"mergeCommit":{"message":"[AI Assistant] Add scopes telemetry to AI Assistant events (#197983)\n\n## Summary\r\n\r\nThis adds telemetry to the Observability and Search assistant to judge\r\nwhether it's search or observability.","sha":"74cf0e4e2bd386ae38a6b8c537545acbd1707022"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.17.0","branchLabelMappingKey":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Sander Philipse <94373878+sphilipse@users.noreply.github.com> |
||
Sander Philipse
|
bd29318087
|
[8.16] [AI Assistant] Add assistant to Serverless Search (#196832) (#198301)
# Backport
This will backport the following commits from `main` to `8.16`:
- [AI Assistant] Add assistant to Serverless Search (#196832) (
|
||
|
Kibana Machine
|
115ab7a082
|
[8.16] [Cloud Security] add vulnerabilties data set to filter for links from CNVM dashboard (#197648) (#198139)
# Backport This will backport the following commits from `main` to `8.16`: - [[Cloud Security] add vulnerabilties data set to filter for links from CNVM dashboard (#197648)](https://github.com/elastic/kibana/pull/197648) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Maxim Kholod","email":"maxim.kholod@elastic.co"},"sourceCommit":{"committedDate":"2024-10-29T10:53:23Z","message":"[Cloud Security] add vulnerabilties data set to filter for links from CNVM dashboard (#197648)\n\n## Summary\r\n\r\n- fixes https://github.com/elastic/security-team/issues/10915","sha":"b4ed7a1945f5ea5b76be36833cdf11e28641cf8f","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Cloud Security","backport:prev-minor","v8.16.0","backport:version","v8.17.0"],"title":"[Cloud Security] add vulnerabilties data set to filter for links from CNVM dashboard","number":197648,"url":"https://github.com/elastic/kibana/pull/197648","mergeCommit":{"message":"[Cloud Security] add vulnerabilties data set to filter for links from CNVM dashboard (#197648)\n\n## Summary\r\n\r\n- fixes https://github.com/elastic/security-team/issues/10915","sha":"b4ed7a1945f5ea5b76be36833cdf11e28641cf8f"}},"sourceBranch":"main","suggestedTargetBranches":["8.16","8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/197648","number":197648,"mergeCommit":{"message":"[Cloud Security] add vulnerabilties data set to filter for links from CNVM dashboard (#197648)\n\n## Summary\r\n\r\n- fixes https://github.com/elastic/security-team/issues/10915","sha":"b4ed7a1945f5ea5b76be36833cdf11e28641cf8f"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.17.0","branchLabelMappingKey":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Maxim Kholod <maxim.kholod@elastic.co> |
||
|
Kibana Machine
|
45b0eada97
|
[8.16] [Security solution] Knowledge base tour video update (#198158) (#198228)
# Backport This will backport the following commits from `main` to `8.16`: - [[Security solution] Knowledge base tour video update (#198158)](https://github.com/elastic/kibana/pull/198158) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Steph Milovic","email":"stephanie.milovic@elastic.co"},"sourceCommit":{"committedDate":"2024-10-29T23:17:24Z","message":"[Security solution] Knowledge base tour video update (#198158)","sha":"a098aaaac798d5158deccb21b00e60e41ea71d54","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","💝community","v9.0.0","Team: SecuritySolution","Team:Security Generative AI","v8.16.0","backport:version","v8.17.0"],"title":"[Security solution] Knowledge base tour video update","number":198158,"url":"https://github.com/elastic/kibana/pull/198158","mergeCommit":{"message":"[Security solution] Knowledge base tour video update (#198158)","sha":"a098aaaac798d5158deccb21b00e60e41ea71d54"}},"sourceBranch":"main","suggestedTargetBranches":["8.16","8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/198158","number":198158,"mergeCommit":{"message":"[Security solution] Knowledge base tour video update (#198158)","sha":"a098aaaac798d5158deccb21b00e60e41ea71d54"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.17.0","branchLabelMappingKey":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Steph Milovic <stephanie.milovic@elastic.co> |
||
|
Kibana Machine
|
dedfdecbaf
|
[8.16] [AI Assistant] Set scope and rename to Observability and Search (#196322) (#197608)
# Backport This will backport the following commits from `main` to `8.16`: - [[AI Assistant] Set scope and rename to Observability and Search (#196322)](https://github.com/elastic/kibana/pull/196322) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Sander Philipse","email":"94373878+sphilipse@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-10-24T11:13:43Z","message":"[AI Assistant] Set scope and rename to Observability and Search (#196322)\n\n## Summary\r\n\r\nThis renames the Observability AI Assistant in some places to AI\r\nAssistant for Observability and Search. It also makes the scope\r\nmulti-valued on both sides.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"26ec293f07a990930c4caf9765d79882723dbfa6","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Search","Team:Obs AI Assistant","ci:project-deploy-observability","Team:obs-ux-infra_services","apm:review","v8.16.0","backport:version","v8.17.0"],"title":"[AI Assistant] Set scope and rename to Observability and Search","number":196322,"url":"https://github.com/elastic/kibana/pull/196322","mergeCommit":{"message":"[AI Assistant] Set scope and rename to Observability and Search (#196322)\n\n## Summary\r\n\r\nThis renames the Observability AI Assistant in some places to AI\r\nAssistant for Observability and Search. It also makes the scope\r\nmulti-valued on both sides.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"26ec293f07a990930c4caf9765d79882723dbfa6"}},"sourceBranch":"main","suggestedTargetBranches":["8.16","8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/196322","number":196322,"mergeCommit":{"message":"[AI Assistant] Set scope and rename to Observability and Search (#196322)\n\n## Summary\r\n\r\nThis renames the Observability AI Assistant in some places to AI\r\nAssistant for Observability and Search. It also makes the scope\r\nmulti-valued on both sides.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"26ec293f07a990930c4caf9765d79882723dbfa6"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.17.0","branchLabelMappingKey":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Sander Philipse <94373878+sphilipse@users.noreply.github.com> |
||
Lisa Cawley
|
f5e7c9b963
|
[8.16] [OpenAPI][DOCS] Add descriptions, examples, responses for role APIs (#195527) (#197890)
# Backport This will backport the following commits from `main` to `8.16`: - [[OpenAPI][DOCS] Add descriptions, examples, responses for role APIs (#195527)](https://github.com/elastic/kibana/pull/195527) <!--- 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":"2024-10-25T17:13:57Z","message":"[OpenAPI][DOCS] Add descriptions, examples, responses for role APIs (#195527)\n\nCo-authored-by: Elena Shostak <165678770+elena-shostak@users.noreply.github.com>","sha":"02fab7248d5b4e537030252df81bef55d04d0595","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Security","release_note:skip","Feature:Security/Authorization","v9.0.0","docs","v8.16.0","backport:version","v8.17.0"],"number":195527,"url":"https://github.com/elastic/kibana/pull/195527","mergeCommit":{"message":"[OpenAPI][DOCS] Add descriptions, examples, responses for role APIs (#195527)\n\nCo-authored-by: Elena Shostak <165678770+elena-shostak@users.noreply.github.com>","sha":"02fab7248d5b4e537030252df81bef55d04d0595"}},"sourceBranch":"main","suggestedTargetBranches":["8.16","8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/195527","number":195527,"mergeCommit":{"message":"[OpenAPI][DOCS] Add descriptions, examples, responses for role APIs (#195527)\n\nCo-authored-by: Elena Shostak <165678770+elena-shostak@users.noreply.github.com>","sha":"02fab7248d5b4e537030252df81bef55d04d0595"}},{"branch":"8.16","label":"v8.16.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.17.0","labelRegex":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
Kibana Machine
|
495308d7b6
|
[8.16] [Cloud Security] exclude unknown findings from compliance score calculation (#197829) (#198004)
# Backport This will backport the following commits from `main` to `8.16`: - [[Cloud Security] exclude unknown findings from compliance score calculation (#197829)](https://github.com/elastic/kibana/pull/197829) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Maxim Kholod","email":"maxim.kholod@elastic.co"},"sourceCommit":{"committedDate":"2024-10-28T14:09:47Z","message":"[Cloud Security] exclude unknown findings from compliance score calculation (#197829)\n\n## Summary\r\n\r\nFindings from 3rd party date can have `result.evaluation: unknown`. This\r\nleads to incorrect posture/compliance score in our flows. This PR\r\nremoves these findings from the score calculation and graphical\r\nrepresentation. properly introducing `unknown` in the compliance score\r\nUX flows will be solved separately\r\n\r\n- fixes https://github.com/elastic/security-team/issues/10913\r\n\r\n### Screenshots\r\n\r\n<img width=\"1473\" alt=\"Screenshot 2024-10-25 at 14 19 03\"\r\nsrc=\"https://github.com/user-attachments/assets/c69e45b0-7da1-4eb8-b83a-f895e7b7c3a4\">\r\n\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [x] 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- [x] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\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- [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- [ ] 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)","sha":"3791a9bc6a7347bc4f0b4d9c754cc629204a05fd","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Cloud Security","backport:prev-minor","v8.16.0","backport:version","v8.17.0"],"title":"[Cloud Security] exclude unknown findings from compliance score calculation","number":197829,"url":"https://github.com/elastic/kibana/pull/197829","mergeCommit":{"message":"[Cloud Security] exclude unknown findings from compliance score calculation (#197829)\n\n## Summary\r\n\r\nFindings from 3rd party date can have `result.evaluation: unknown`. This\r\nleads to incorrect posture/compliance score in our flows. This PR\r\nremoves these findings from the score calculation and graphical\r\nrepresentation. properly introducing `unknown` in the compliance score\r\nUX flows will be solved separately\r\n\r\n- fixes https://github.com/elastic/security-team/issues/10913\r\n\r\n### Screenshots\r\n\r\n<img width=\"1473\" alt=\"Screenshot 2024-10-25 at 14 19 03\"\r\nsrc=\"https://github.com/user-attachments/assets/c69e45b0-7da1-4eb8-b83a-f895e7b7c3a4\">\r\n\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [x] 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- [x] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\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- [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- [ ] 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)","sha":"3791a9bc6a7347bc4f0b4d9c754cc629204a05fd"}},"sourceBranch":"main","suggestedTargetBranches":["8.16","8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/197829","number":197829,"mergeCommit":{"message":"[Cloud Security] exclude unknown findings from compliance score calculation (#197829)\n\n## Summary\r\n\r\nFindings from 3rd party date can have `result.evaluation: unknown`. This\r\nleads to incorrect posture/compliance score in our flows. This PR\r\nremoves these findings from the score calculation and graphical\r\nrepresentation. properly introducing `unknown` in the compliance score\r\nUX flows will be solved separately\r\n\r\n- fixes https://github.com/elastic/security-team/issues/10913\r\n\r\n### Screenshots\r\n\r\n<img width=\"1473\" alt=\"Screenshot 2024-10-25 at 14 19 03\"\r\nsrc=\"https://github.com/user-attachments/assets/c69e45b0-7da1-4eb8-b83a-f895e7b7c3a4\">\r\n\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [x] 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- [x] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\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- [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- [ ] 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)","sha":"3791a9bc6a7347bc4f0b4d9c754cc629204a05fd"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.17.0","branchLabelMappingKey":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Maxim Kholod <maxim.kholod@elastic.co> |
||
Philippe Oberti
|
9604402862
|
[8.16] [Security Solution][Notes] - fix createdBy filter for notes management page (#197706) (#197911)
# Backport This will backport the following commits from `main` to `8.16`: - [[Security Solution][Notes] - fix createdBy filter for notes management page (#197706)](https://github.com/elastic/kibana/pull/197706) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Philippe Oberti","email":"philippe.oberti@elastic.co"},"sourceCommit":{"committedDate":"2024-10-25T20:37:23Z","message":"[Security Solution][Notes] - fix createdBy filter for notes management page (#197706)","sha":"1065bbf03ca0583935d9b482939823e6b46c3c52","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["backport","release_note:skip","v9.0.0","Team:Threat Hunting:Investigations","v8.16.0"],"number":197706,"url":"https://github.com/elastic/kibana/pull/197706","mergeCommit":{"message":"[Security Solution][Notes] - fix createdBy filter for notes management page (#197706)","sha":"1065bbf03ca0583935d9b482939823e6b46c3c52"}},"sourceBranch":"main","suggestedTargetBranches":["8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/197706","number":197706,"mergeCommit":{"message":"[Security Solution][Notes] - fix createdBy filter for notes management page (#197706)","sha":"1065bbf03ca0583935d9b482939823e6b46c3c52"}},{"branch":"8.16","label":"v8.16.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
Kibana Machine
|
7f52ae8d6a
|
[8.16] [Cloud Security] Clicking on Contextual Flyout popout Icon now opens page in new tab (#196763) (#197934)
# Backport This will backport the following commits from `main` to `8.16`: - [[Cloud Security] Clicking on Contextual Flyout popout Icon now opens page in new tab (#196763)](https://github.com/elastic/kibana/pull/196763) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Rickyanto Ang","email":"rickyangwyn@gmail.com"},"sourceCommit":{"committedDate":"2024-10-27T16:47:01Z","message":"[Cloud Security] Clicking on Contextual Flyout popout Icon now opens page in new tab (#196763)\n\n## Summary\r\n\r\nCurrently when user clicks on Popout icon on Misconfiguration or\r\nVulnerabilities Contextual flyout, user gets redirected to Findings page\r\nbut in the same tab. Popout Icon implies that it should navigate user to\r\nother page on separate Tabs as such the current behaviour is not right.\r\n\r\nThis PR addresses that issue\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"37a4691ab6b33886b20126b54120f37002f26125","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Cloud Security","backport:prev-minor","v8.16.0"],"title":"[Cloud Security] Clicking on Contextual Flyout popout Icon now opens page in new tab","number":196763,"url":"https://github.com/elastic/kibana/pull/196763","mergeCommit":{"message":"[Cloud Security] Clicking on Contextual Flyout popout Icon now opens page in new tab (#196763)\n\n## Summary\r\n\r\nCurrently when user clicks on Popout icon on Misconfiguration or\r\nVulnerabilities Contextual flyout, user gets redirected to Findings page\r\nbut in the same tab. Popout Icon implies that it should navigate user to\r\nother page on separate Tabs as such the current behaviour is not right.\r\n\r\nThis PR addresses that issue\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"37a4691ab6b33886b20126b54120f37002f26125"}},"sourceBranch":"main","suggestedTargetBranches":["8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/196763","number":196763,"mergeCommit":{"message":"[Cloud Security] Clicking on Contextual Flyout popout Icon now opens page in new tab (#196763)\n\n## Summary\r\n\r\nCurrently when user clicks on Popout icon on Misconfiguration or\r\nVulnerabilities Contextual flyout, user gets redirected to Findings page\r\nbut in the same tab. Popout Icon implies that it should navigate user to\r\nother page on separate Tabs as such the current behaviour is not right.\r\n\r\nThis PR addresses that issue\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"37a4691ab6b33886b20126b54120f37002f26125"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Rickyanto Ang <rickyangwyn@gmail.com> |
||
|
Kibana Machine
|
f25e599d25
|
[8.16] [Security GenAI] When a "global" Knowledge Base entry is updated to "private", a duplicate "private" entry gets created and the global entry remains unchanged (#197157) (#197516) (#197918)
# Backport This will backport the following commits from `main` to `8.16`: - [[Security GenAI] When a "global" Knowledge Base entry is updated to "private", a duplicate "private" entry gets created and the global entry remains unchanged (#197157) (#197516)](https://github.com/elastic/kibana/pull/197516) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Ievgen Sorokopud","email":"ievgen.sorokopud@elastic.co"},"sourceCommit":{"committedDate":"2024-10-25T22:45:32Z","message":"[Security GenAI] When a \"global\" Knowledge Base entry is updated to \"private\", a duplicate \"private\" entry gets created and the global entry remains unchanged (#197157) (#197516)\n\n## Summary\r\n\r\nOriginal ticket describing the BUG:\r\nhttps://github.com/elastic/kibana/issues/197157\r\n\r\nThese changes fix two issues:\r\n1. Updating an entry from Global to Private duplicates it. After\r\ndiscussing with the team we decided that this is an expected behaviour\r\nand we would add a modal dialog which warns users about it. See more\r\ndetails here\r\nhttps://github.com/elastic/kibana/issues/197157#issuecomment-2432592394\r\n2. Editing Private entry and switching the sharing option twice from\r\nPrivate => Global => Private causes the issue where we would treat\r\nselected entry as a new one and thus calling \"create entry\" instead of\r\n\"update\".\r\n\r\n### Steps to reproduce second issue:\r\n\r\n* Edit private entry\r\n* Update entry's name\r\n* Switch sharing option to Global\r\n* Switch sharing option back to Private\r\n* Save the entry\r\n\r\n**Current behaviour**: a new private entry is created\r\n**Expected behaviour**: existing private entry is updated\r\n\r\n### Screen recording of the fixed first issue\r\n\r\n\r\nhttps://github.com/user-attachments/assets/e11e14bd-c557-401e-a23f-e01ac7aedf30\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\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","sha":"d17fc09034d69f15748ddb0a49eae78959401c5a","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team: SecuritySolution","backport:prev-minor","Team:Security Generative AI","v8.16.0"],"title":"[Security GenAI] When a \"global\" Knowledge Base entry is updated to \"private\", a duplicate \"private\" entry gets created and the global entry remains unchanged (#197157)","number":197516,"url":"https://github.com/elastic/kibana/pull/197516","mergeCommit":{"message":"[Security GenAI] When a \"global\" Knowledge Base entry is updated to \"private\", a duplicate \"private\" entry gets created and the global entry remains unchanged (#197157) (#197516)\n\n## Summary\r\n\r\nOriginal ticket describing the BUG:\r\nhttps://github.com/elastic/kibana/issues/197157\r\n\r\nThese changes fix two issues:\r\n1. Updating an entry from Global to Private duplicates it. After\r\ndiscussing with the team we decided that this is an expected behaviour\r\nand we would add a modal dialog which warns users about it. See more\r\ndetails here\r\nhttps://github.com/elastic/kibana/issues/197157#issuecomment-2432592394\r\n2. Editing Private entry and switching the sharing option twice from\r\nPrivate => Global => Private causes the issue where we would treat\r\nselected entry as a new one and thus calling \"create entry\" instead of\r\n\"update\".\r\n\r\n### Steps to reproduce second issue:\r\n\r\n* Edit private entry\r\n* Update entry's name\r\n* Switch sharing option to Global\r\n* Switch sharing option back to Private\r\n* Save the entry\r\n\r\n**Current behaviour**: a new private entry is created\r\n**Expected behaviour**: existing private entry is updated\r\n\r\n### Screen recording of the fixed first issue\r\n\r\n\r\nhttps://github.com/user-attachments/assets/e11e14bd-c557-401e-a23f-e01ac7aedf30\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\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","sha":"d17fc09034d69f15748ddb0a49eae78959401c5a"}},"sourceBranch":"main","suggestedTargetBranches":["8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/197516","number":197516,"mergeCommit":{"message":"[Security GenAI] When a \"global\" Knowledge Base entry is updated to \"private\", a duplicate \"private\" entry gets created and the global entry remains unchanged (#197157) (#197516)\n\n## Summary\r\n\r\nOriginal ticket describing the BUG:\r\nhttps://github.com/elastic/kibana/issues/197157\r\n\r\nThese changes fix two issues:\r\n1. Updating an entry from Global to Private duplicates it. After\r\ndiscussing with the team we decided that this is an expected behaviour\r\nand we would add a modal dialog which warns users about it. See more\r\ndetails here\r\nhttps://github.com/elastic/kibana/issues/197157#issuecomment-2432592394\r\n2. Editing Private entry and switching the sharing option twice from\r\nPrivate => Global => Private causes the issue where we would treat\r\nselected entry as a new one and thus calling \"create entry\" instead of\r\n\"update\".\r\n\r\n### Steps to reproduce second issue:\r\n\r\n* Edit private entry\r\n* Update entry's name\r\n* Switch sharing option to Global\r\n* Switch sharing option back to Private\r\n* Save the entry\r\n\r\n**Current behaviour**: a new private entry is created\r\n**Expected behaviour**: existing private entry is updated\r\n\r\n### Screen recording of the fixed first issue\r\n\r\n\r\nhttps://github.com/user-attachments/assets/e11e14bd-c557-401e-a23f-e01ac7aedf30\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\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","sha":"d17fc09034d69f15748ddb0a49eae78959401c5a"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Ievgen Sorokopud <ievgen.sorokopud@elastic.co> |
||
|
Kibana Machine
|
b33a0c4a5a
|
[8.16] [Security GenAI] When indices referenced in KB index entries are deleted from OUTSIDE the AI Assistant KB UI, there is not indication to the user (#197156) (#197722) (#197894)
# Backport This will backport the following commits from `main` to `8.16`: - [[Security GenAI] When indices referenced in KB index entries are deleted from OUTSIDE the AI Assistant KB UI, there is not indication to the user (#197156) (#197722)](https://github.com/elastic/kibana/pull/197722) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Ievgen Sorokopud","email":"ievgen.sorokopud@elastic.co"},"sourceCommit":{"committedDate":"2024-10-25T19:17:57Z","message":"[Security GenAI] When indices referenced in KB index entries are deleted from OUTSIDE the AI Assistant KB UI, there is not indication to the user (#197156) (#197722)\n\n## Summary\r\n\r\nBug https://github.com/elastic/kibana/issues/197156\r\n\r\nThis is a UI part of the bug that warns a user about missing indices\r\nused in knowledge base entries.\r\n\r\n### To test\r\n\r\n1. Add an index entry that uses existing index\r\n2. Remove that index\r\n3. Go back to knowledge base entries page\r\n4. You should see warning icon next to the name of the index entry which\r\nuses removed index. Also, when you edit that entry you will see `Index\r\ndoesn't exist` error next to the `Index` field in the flyout\r\n\r\n<img width=\"1458\" alt=\"Screenshot 2024-10-24 at 19 54 36\"\r\nsrc=\"https://github.com/user-attachments/assets/7d4468f9-fada-4416-9480-99bfca3de220\">\r\n\r\n<img width=\"615\" alt=\"Screenshot 2024-10-24 at 19 54 52\"\r\nsrc=\"https://github.com/user-attachments/assets/fd9bbe80-0a3c-40b8-909a-93f8082e69eb\">\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] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"a1d755a675b05269f167d160f4c0c28a83d5e4d5","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team: SecuritySolution","backport:prev-minor","Team:Security Generative AI","v8.16.0"],"title":"[Security GenAI] When indices referenced in KB index entries are deleted from OUTSIDE the AI Assistant KB UI, there is not indication to the user (#197156)","number":197722,"url":"https://github.com/elastic/kibana/pull/197722","mergeCommit":{"message":"[Security GenAI] When indices referenced in KB index entries are deleted from OUTSIDE the AI Assistant KB UI, there is not indication to the user (#197156) (#197722)\n\n## Summary\r\n\r\nBug https://github.com/elastic/kibana/issues/197156\r\n\r\nThis is a UI part of the bug that warns a user about missing indices\r\nused in knowledge base entries.\r\n\r\n### To test\r\n\r\n1. Add an index entry that uses existing index\r\n2. Remove that index\r\n3. Go back to knowledge base entries page\r\n4. You should see warning icon next to the name of the index entry which\r\nuses removed index. Also, when you edit that entry you will see `Index\r\ndoesn't exist` error next to the `Index` field in the flyout\r\n\r\n<img width=\"1458\" alt=\"Screenshot 2024-10-24 at 19 54 36\"\r\nsrc=\"https://github.com/user-attachments/assets/7d4468f9-fada-4416-9480-99bfca3de220\">\r\n\r\n<img width=\"615\" alt=\"Screenshot 2024-10-24 at 19 54 52\"\r\nsrc=\"https://github.com/user-attachments/assets/fd9bbe80-0a3c-40b8-909a-93f8082e69eb\">\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] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"a1d755a675b05269f167d160f4c0c28a83d5e4d5"}},"sourceBranch":"main","suggestedTargetBranches":["8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/197722","number":197722,"mergeCommit":{"message":"[Security GenAI] When indices referenced in KB index entries are deleted from OUTSIDE the AI Assistant KB UI, there is not indication to the user (#197156) (#197722)\n\n## Summary\r\n\r\nBug https://github.com/elastic/kibana/issues/197156\r\n\r\nThis is a UI part of the bug that warns a user about missing indices\r\nused in knowledge base entries.\r\n\r\n### To test\r\n\r\n1. Add an index entry that uses existing index\r\n2. Remove that index\r\n3. Go back to knowledge base entries page\r\n4. You should see warning icon next to the name of the index entry which\r\nuses removed index. Also, when you edit that entry you will see `Index\r\ndoesn't exist` error next to the `Index` field in the flyout\r\n\r\n<img width=\"1458\" alt=\"Screenshot 2024-10-24 at 19 54 36\"\r\nsrc=\"https://github.com/user-attachments/assets/7d4468f9-fada-4416-9480-99bfca3de220\">\r\n\r\n<img width=\"615\" alt=\"Screenshot 2024-10-24 at 19 54 52\"\r\nsrc=\"https://github.com/user-attachments/assets/fd9bbe80-0a3c-40b8-909a-93f8082e69eb\">\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] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"a1d755a675b05269f167d160f4c0c28a83d5e4d5"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Ievgen Sorokopud <ievgen.sorokopud@elastic.co> |
||
|
Steph Milovic
|
95635d3244
|
[8.16] [Security Assistant] Revert open AI Assistant settings in new tab (#197725) (#197857)
# Backport This will backport the following commits from `main` to `8.16`: - [[Security Assistant] Revert open AI Assistant settings in new tab (#197725)](https://github.com/elastic/kibana/pull/197725) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Steph Milovic","email":"stephanie.milovic@elastic.co"},"sourceCommit":{"committedDate":"2024-10-24T22:44:45Z","message":"[Security Assistant] Revert open AI Assistant settings in new tab (#197725)","sha":"d2aa00708309fdf85deb03870f65960ec78161cf","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team: SecuritySolution","Team:Security Generative AI","v8.16.0","backport:version","v8.17.0"],"number":197725,"url":"https://github.com/elastic/kibana/pull/197725","mergeCommit":{"message":"[Security Assistant] Revert open AI Assistant settings in new tab (#197725)","sha":"d2aa00708309fdf85deb03870f65960ec78161cf"}},"sourceBranch":"main","suggestedTargetBranches":["8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/197725","number":197725,"mergeCommit":{"message":"[Security Assistant] Revert open AI Assistant settings in new tab (#197725)","sha":"d2aa00708309fdf85deb03870f65960ec78161cf"}},{"branch":"8.16","label":"v8.16.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.17.0","labelRegex":"^v8.17.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/197746","number":197746,"state":"MERGED","mergeCommit":{"sha":"67abfdc08366f041b0de3542deb5ac80fd2eed29","message":"[8.x] [Security Assistant] Revert open AI Assistant settings in new tab (#197725) (#197746)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[Security Assistant] Revert open AI Assistant settings in new tab\n(#197725)](https://github.com/elastic/kibana/pull/197725)\n\n<!--- Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Steph\nMilovic\",\"email\":\"stephanie.milovic@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2024-10-24T22:44:45Z\",\"message\":\"[Security\nAssistant] Revert open AI Assistant settings in new tab\n(#197725)\",\"sha\":\"d2aa00708309fdf85deb03870f65960ec78161cf\",\"branchLabelMapping\":{\"^v9.0.0$\":\"main\",\"^v8.17.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"release_note:skip\",\"v9.0.0\",\"Team:\nSecuritySolution\",\"backport:prev-minor\",\"Team:Security Generative\nAI\"],\"title\":\"[Security Assistant] Revert open AI Assistant settings in\nnew\ntab\",\"number\":197725,\"url\":\"https://github.com/elastic/kibana/pull/197725\",\"mergeCommit\":{\"message\":\"[Security\nAssistant] Revert open AI Assistant settings in new tab\n(#197725)\",\"sha\":\"d2aa00708309fdf85deb03870f65960ec78161cf\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[],\"targetPullRequestStates\":[{\"branch\":\"main\",\"label\":\"v9.0.0\",\"branchLabelMappingKey\":\"^v9.0.0$\",\"isSourceBranch\":true,\"state\":\"MERGED\",\"url\":\"https://github.com/elastic/kibana/pull/197725\",\"number\":197725,\"mergeCommit\":{\"message\":\"[Security\nAssistant] Revert open AI Assistant settings in new tab\n(#197725)\",\"sha\":\"d2aa00708309fdf85deb03870f65960ec78161cf\"}}]}]\nBACKPORT-->\n\nCo-authored-by: Steph Milovic <stephanie.milovic@elastic.co>"}}]}] BACKPORT--> |
||
|
Kibana Machine
|
bf6acbd2e7
|
[8.16] [Cloud Security] add sideEffects: false to shared csp packages (#197486) (#197766)
# Backport This will backport the following commits from `main` to `8.16`: - [[Cloud Security] add sideEffects: false to shared csp packages (#197486)](https://github.com/elastic/kibana/pull/197486) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Maxim Kholod","email":"maxim.kholod@elastic.co"},"sourceCommit":{"committedDate":"2024-10-25T07:36:21Z","message":"[Cloud Security] add sideEffects: false to shared csp packages (#197486)\n\n## Summary\r\n\r\nadd `sideEffects: false` to shared packages for better tree shaking, see\r\n[docs](https://webpack.js.org/guides/tree-shaking/#mark-the-file-as-side-effect-free)\r\nand [related\r\ndiscussion](https://elastic.slack.com/archives/C5TQ33ND8/p1724317421954709?thread_ts=1724314732.061379&cid=C5TQ33ND8)","sha":"12ad7153535238dc4a68de4cbb98e27305efc956","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Cloud Security","backport:prev-minor","v8.16.0","v8.17.0"],"title":"[Cloud Security] add sideEffects: false to shared csp packages","number":197486,"url":"https://github.com/elastic/kibana/pull/197486","mergeCommit":{"message":"[Cloud Security] add sideEffects: false to shared csp packages (#197486)\n\n## Summary\r\n\r\nadd `sideEffects: false` to shared packages for better tree shaking, see\r\n[docs](https://webpack.js.org/guides/tree-shaking/#mark-the-file-as-side-effect-free)\r\nand [related\r\ndiscussion](https://elastic.slack.com/archives/C5TQ33ND8/p1724317421954709?thread_ts=1724314732.061379&cid=C5TQ33ND8)","sha":"12ad7153535238dc4a68de4cbb98e27305efc956"}},"sourceBranch":"main","suggestedTargetBranches":["8.16","8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/197486","number":197486,"mergeCommit":{"message":"[Cloud Security] add sideEffects: false to shared csp packages (#197486)\n\n## Summary\r\n\r\nadd `sideEffects: false` to shared packages for better tree shaking, see\r\n[docs](https://webpack.js.org/guides/tree-shaking/#mark-the-file-as-side-effect-free)\r\nand [related\r\ndiscussion](https://elastic.slack.com/archives/C5TQ33ND8/p1724317421954709?thread_ts=1724314732.061379&cid=C5TQ33ND8)","sha":"12ad7153535238dc4a68de4cbb98e27305efc956"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.17.0","branchLabelMappingKey":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Maxim Kholod <maxim.kholod@elastic.co> |
||
|
Kibana Machine
|
9bd2c8accd
|
[8.16] [Security Assistant] Fix Security Assistant settings link behavior and adjust initial settings tab (#197323) (#197748)
# Backport This will backport the following commits from `main` to `8.16`: - [[Security Assistant] Fix Security Assistant settings link behavior and adjust initial settings tab (#197323)](https://github.com/elastic/kibana/pull/197323) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Steph Milovic","email":"stephanie.milovic@elastic.co"},"sourceCommit":{"committedDate":"2024-10-23T16:06:47Z","message":"[Security Assistant] Fix Security Assistant settings link behavior and adjust initial settings tab (#197323)","sha":"a6dc47ddeb15d6c7b91e1abaaf83fba3eee2fef2","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team: SecuritySolution","Team:Security Generative AI","v8.16.0","backport:version","v8.17.0"],"title":"[Security Assistant] Fix Security Assistant settings link behavior and adjust initial settings tab","number":197323,"url":"https://github.com/elastic/kibana/pull/197323","mergeCommit":{"message":"[Security Assistant] Fix Security Assistant settings link behavior and adjust initial settings tab (#197323)","sha":"a6dc47ddeb15d6c7b91e1abaaf83fba3eee2fef2"}},"sourceBranch":"main","suggestedTargetBranches":["8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/197323","number":197323,"mergeCommit":{"message":"[Security Assistant] Fix Security Assistant settings link behavior and adjust initial settings tab (#197323)","sha":"a6dc47ddeb15d6c7b91e1abaaf83fba3eee2fef2"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.17.0","branchLabelMappingKey":"^v8.17.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/197493","number":197493,"state":"MERGED","mergeCommit":{"sha":"942827df09a03a7356f66e98753a3e356e644371","message":"[8.x] [Security Assistant] Fix Security Assistant settings link behavior and adjust initial settings tab (#197323) (#197493)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[Security Assistant] Fix Security Assistant settings link behavior\nand adjust initial settings tab\n(#197323)](https://github.com/elastic/kibana/pull/197323)\n\n<!--- Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Steph\nMilovic\",\"email\":\"stephanie.milovic@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2024-10-23T16:06:47Z\",\"message\":\"[Security\nAssistant] Fix Security Assistant settings link behavior and adjust\ninitial settings tab\n(#197323)\",\"sha\":\"a6dc47ddeb15d6c7b91e1abaaf83fba3eee2fef2\",\"branchLabelMapping\":{\"^v9.0.0$\":\"main\",\"^v8.17.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"release_note:skip\",\"v9.0.0\",\"Team:\nSecuritySolution\",\"backport:prev-minor\",\"Team:Security Generative\nAI\"],\"title\":\"[Security Assistant] Fix Security Assistant settings link\nbehavior and adjust initial settings\ntab\",\"number\":197323,\"url\":\"https://github.com/elastic/kibana/pull/197323\",\"mergeCommit\":{\"message\":\"[Security\nAssistant] Fix Security Assistant settings link behavior and adjust\ninitial settings tab\n(#197323)\",\"sha\":\"a6dc47ddeb15d6c7b91e1abaaf83fba3eee2fef2\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[],\"targetPullRequestStates\":[{\"branch\":\"main\",\"label\":\"v9.0.0\",\"branchLabelMappingKey\":\"^v9.0.0$\",\"isSourceBranch\":true,\"state\":\"MERGED\",\"url\":\"https://github.com/elastic/kibana/pull/197323\",\"number\":197323,\"mergeCommit\":{\"message\":\"[Security\nAssistant] Fix Security Assistant settings link behavior and adjust\ninitial settings tab\n(#197323)\",\"sha\":\"a6dc47ddeb15d6c7b91e1abaaf83fba3eee2fef2\"}}]}]\nBACKPORT-->\n\nCo-authored-by: Steph Milovic <stephanie.milovic@elastic.co>"}}]}] BACKPORT--> Co-authored-by: Steph Milovic <stephanie.milovic@elastic.co> |
||
|
Kibana Machine
|
59220e984f
|
[8.16] [Security assistant] Conversation pagination patch MIN (#197305) (#197557)
# Backport This will backport the following commits from `main` to `8.16`: - [[Security assistant] Conversation pagination patch MIN (#197305)](https://github.com/elastic/kibana/pull/197305) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Steph Milovic","email":"stephanie.milovic@elastic.co"},"sourceCommit":{"committedDate":"2024-10-24T02:25:17Z","message":"[Security assistant] Conversation pagination patch MIN (#197305)","sha":"de876fbd1b7a216565eb24b75b8453ee16a4641a","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","Team: SecuritySolution","backport:prev-major","Team:Security Generative AI","v8.16.0","v8.17.0","v8.15.4"],"title":"[Security assistant] Conversation pagination patch MIN","number":197305,"url":"https://github.com/elastic/kibana/pull/197305","mergeCommit":{"message":"[Security assistant] Conversation pagination patch MIN (#197305)","sha":"de876fbd1b7a216565eb24b75b8453ee16a4641a"}},"sourceBranch":"main","suggestedTargetBranches":["8.16","8.x","8.15"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/197305","number":197305,"mergeCommit":{"message":"[Security assistant] Conversation pagination patch MIN (#197305)","sha":"de876fbd1b7a216565eb24b75b8453ee16a4641a"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.17.0","branchLabelMappingKey":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.15","label":"v8.15.4","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Steph Milovic <stephanie.milovic@elastic.co> |
||
|
Kibana Machine
|
a8d1c24dab
|
[8.16] [Security Solution] Repurpose attack discover tour into knowledge base tour (#196615) (#197535)
# Backport This will backport the following commits from `main` to `8.16`: - [[Security Solution] Repurpose attack discover tour into knowledge base tour (#196615)](https://github.com/elastic/kibana/pull/196615) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Steph Milovic","email":"stephanie.milovic@elastic.co"},"sourceCommit":{"committedDate":"2024-10-23T21:02:35Z","message":"[Security Solution] Repurpose attack discover tour into knowledge base tour (#196615)","sha":"fa9bb19f14648bbe34493481df0b32838d0e5734","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team: SecuritySolution","backport:prev-minor","Team:Security Generative AI","v8.16.0"],"title":"[Security Solution] Repurpose attack discover tour into knowledge base tour","number":196615,"url":"https://github.com/elastic/kibana/pull/196615","mergeCommit":{"message":"[Security Solution] Repurpose attack discover tour into knowledge base tour (#196615)","sha":"fa9bb19f14648bbe34493481df0b32838d0e5734"}},"sourceBranch":"main","suggestedTargetBranches":["8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/196615","number":196615,"mergeCommit":{"message":"[Security Solution] Repurpose attack discover tour into knowledge base tour (#196615)","sha":"fa9bb19f14648bbe34493481df0b32838d0e5734"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Steph Milovic <stephanie.milovic@elastic.co> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> |
||
|
Kibana Machine
|
f9dee7cb67
|
[8.16] Add watsonx icon for inference endpoints management page (#197116) (#197275)
# Backport This will backport the following commits from `main` to `8.16`: - [Add watsonx icon for inference endpoints management page (#197116)](https://github.com/elastic/kibana/pull/197116) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Saikat Sarkar","email":"132922331+saikatsarkar056@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-10-22T15:10:40Z","message":"Add watsonx icon for inference endpoints management page (#197116)\n\nThis PR adds IBM Watsonx ai support for the Inference Endpoints\r\nManagement UI.\r\n\r\n<img width=\"1249\" alt=\"Screenshot 2024-10-21 at 12 22 09 PM\"\r\nsrc=\"https://github.com/user-attachments/assets/58516bef-4800-4198-91bf-c428d878d787\">","sha":"8e1fcc126ac1b5b012b5730d51ca1ba6304020d5","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:EnterpriseSearch","backport:prev-minor","v8.16.0"],"title":"Add watsonx icon for inference endpoints management page","number":197116,"url":"https://github.com/elastic/kibana/pull/197116","mergeCommit":{"message":"Add watsonx icon for inference endpoints management page (#197116)\n\nThis PR adds IBM Watsonx ai support for the Inference Endpoints\r\nManagement UI.\r\n\r\n<img width=\"1249\" alt=\"Screenshot 2024-10-21 at 12 22 09 PM\"\r\nsrc=\"https://github.com/user-attachments/assets/58516bef-4800-4198-91bf-c428d878d787\">","sha":"8e1fcc126ac1b5b012b5730d51ca1ba6304020d5"}},"sourceBranch":"main","suggestedTargetBranches":["8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/197116","number":197116,"mergeCommit":{"message":"Add watsonx icon for inference endpoints management page (#197116)\n\nThis PR adds IBM Watsonx ai support for the Inference Endpoints\r\nManagement UI.\r\n\r\n<img width=\"1249\" alt=\"Screenshot 2024-10-21 at 12 22 09 PM\"\r\nsrc=\"https://github.com/user-attachments/assets/58516bef-4800-4198-91bf-c428d878d787\">","sha":"8e1fcc126ac1b5b012b5730d51ca1ba6304020d5"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Saikat Sarkar <132922331+saikatsarkar056@users.noreply.github.com> |
||
|
Kibana Machine
|
0b47f783e9
|
[8.16] [Security Solution][Notes] - fix user filter not checking correct license in notes management page (#197149) (#197244)
# Backport This will backport the following commits from `main` to `8.16`: - [[Security Solution][Notes] - fix user filter not checking correct license in notes management page (#197149)](https://github.com/elastic/kibana/pull/197149) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Philippe Oberti","email":"philippe.oberti@elastic.co"},"sourceCommit":{"committedDate":"2024-10-22T13:32:48Z","message":"[Security Solution][Notes] - fix user filter not checking correct license in notes management page (#197149)","sha":"dcd8e0c614183ae648e00979eb82123656076d16","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["backport","release_note:skip","v9.0.0","Team:Threat Hunting:Investigations","v8.16.0"],"title":"[Security Solution][Notes] - fix user filter not checking correct license in notes management page","number":197149,"url":"https://github.com/elastic/kibana/pull/197149","mergeCommit":{"message":"[Security Solution][Notes] - fix user filter not checking correct license in notes management page (#197149)","sha":"dcd8e0c614183ae648e00979eb82123656076d16"}},"sourceBranch":"main","suggestedTargetBranches":["8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/197149","number":197149,"mergeCommit":{"message":"[Security Solution][Notes] - fix user filter not checking correct license in notes management page (#197149)","sha":"dcd8e0c614183ae648e00979eb82123656076d16"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Philippe Oberti <philippe.oberti@elastic.co> |
||
|
Kibana Machine
|
6820eb917b
|
[8.16] [Security Assistant] Knowledge base settings author column fix (#197114) (#197137)
# Backport This will backport the following commits from `main` to `8.16`: - [[Security Assistant] Knowledge base settings author column fix (#197114)](https://github.com/elastic/kibana/pull/197114) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Steph Milovic","email":"stephanie.milovic@elastic.co"},"sourceCommit":{"committedDate":"2024-10-21T20:18:44Z","message":"[Security Assistant] Knowledge base settings author column fix (#197114)","sha":"1e12f31a7082ce8286f933f8a586fdb706c35a01","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team: SecuritySolution","backport:prev-minor","Team:Security Generative AI","v8.16.0"],"title":"[Security Assistant] Knowledge base settings author column fix ","number":197114,"url":"https://github.com/elastic/kibana/pull/197114","mergeCommit":{"message":"[Security Assistant] Knowledge base settings author column fix (#197114)","sha":"1e12f31a7082ce8286f933f8a586fdb706c35a01"}},"sourceBranch":"main","suggestedTargetBranches":["8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/197114","number":197114,"mergeCommit":{"message":"[Security Assistant] Knowledge base settings author column fix (#197114)","sha":"1e12f31a7082ce8286f933f8a586fdb706c35a01"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Steph Milovic <stephanie.milovic@elastic.co> |
||
|
Kibana Machine
|
18b517a9fb
|
[8.16] [Security Assistant] Fix KB output fields (#196567) (#197118)
# Backport This will backport the following commits from `main` to `8.16`: - [[Security Assistant] Fix KB output fields (#196567)](https://github.com/elastic/kibana/pull/196567) <!--- Backport version: 9.4.3 --> ### 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":"2024-10-21T18:32:06Z","message":"[Security Assistant] Fix KB output fields (#196567)\n\n## Summary\r\n\r\nFixes Assistant Knowledge Base output fields field logic\r\nFixes Security Assistant card not appearing on Serverless \r\nReverts Assistant Cog wheel settings button when FF\r\n`assistantKnowledgeBaseByDefault` is off\r\n\r\n\r\n","sha":"399aed9b19935651b979dc68ad88429a156dae2f","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","v9.0.0","backport:prev-minor","Feature:Security Assistant","Team:Security Generative AI","v8.16.0","v8.17.0"],"title":"[Security Assistant] Reverts Assistant Cog wheel settings button when assistantKnowledgeBaseByDefault FF is off","number":196567,"url":"https://github.com/elastic/kibana/pull/196567","mergeCommit":{"message":"[Security Assistant] Fix KB output fields (#196567)\n\n## Summary\r\n\r\nFixes Assistant Knowledge Base output fields field logic\r\nFixes Security Assistant card not appearing on Serverless \r\nReverts Assistant Cog wheel settings button when FF\r\n`assistantKnowledgeBaseByDefault` is off\r\n\r\n\r\n","sha":"399aed9b19935651b979dc68ad88429a156dae2f"}},"sourceBranch":"main","suggestedTargetBranches":["8.16","8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/196567","number":196567,"mergeCommit":{"message":"[Security Assistant] Fix KB output fields (#196567)\n\n## Summary\r\n\r\nFixes Assistant Knowledge Base output fields field logic\r\nFixes Security Assistant card not appearing on Serverless \r\nReverts Assistant Cog wheel settings button when FF\r\n`assistantKnowledgeBaseByDefault` is off\r\n\r\n\r\n","sha":"399aed9b19935651b979dc68ad88429a156dae2f"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.17.0","branchLabelMappingKey":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Patryk Kopyciński <contact@patrykkopycinski.com> |
||
|
Kibana Machine
|
b80bc6235d
|
[8.16] [Security Solution] [Attack discovery] Updates default Attack discovery max alerts for users still using legacy models (#196939) (#196959)
# Backport This will backport the following commits from `main` to `8.16`: - [[Security Solution] [Attack discovery] Updates default Attack discovery max alerts for users still using legacy models (#196939)](https://github.com/elastic/kibana/pull/196939) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Andrew Macri","email":"andrew.macri@elastic.co"},"sourceCommit":{"committedDate":"2024-10-18T21:06:55Z","message":"[Security Solution] [Attack discovery] Updates default Attack discovery max alerts for users still using legacy models (#196939)\n\n### [Security Solution] [Attack discovery] Updates default Attack discovery max alerts for users still using legacy models\r\n\r\nIn consideration of users still using legacy models, (e.g. GPT-4 instead of GPT-4o), this PR updates `DEFAULT_ATTACK_DISCOVERY_MAX_ALERTS` from its previous value `200` in <https://github.com/elastic/kibana/pull/195669> to `100`.\r\n\r\nThis PR also includes additional tests.\r\n\r\n## Desk testing\r\n\r\n1) Navigate to Security > Attack discovery\r\n\r\n2) Click the settings gear\r\n\r\n3) Select any value above or below `100` in the Alerts range slider\r\n\r\n4) Click `Reset`\r\n\r\n**Expected result**\r\n\r\n- The range slider resets to `100`","sha":"96585a540b2c5c717ecaf1f71cc2f6f69b4378f5","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team: SecuritySolution","Team:Security Generative AI","v8.16.0","backport:version"],"title":"[Security Solution] [Attack discovery] Updates default Attack discovery max alerts for users still using legacy models","number":196939,"url":"https://github.com/elastic/kibana/pull/196939","mergeCommit":{"message":"[Security Solution] [Attack discovery] Updates default Attack discovery max alerts for users still using legacy models (#196939)\n\n### [Security Solution] [Attack discovery] Updates default Attack discovery max alerts for users still using legacy models\r\n\r\nIn consideration of users still using legacy models, (e.g. GPT-4 instead of GPT-4o), this PR updates `DEFAULT_ATTACK_DISCOVERY_MAX_ALERTS` from its previous value `200` in <https://github.com/elastic/kibana/pull/195669> to `100`.\r\n\r\nThis PR also includes additional tests.\r\n\r\n## Desk testing\r\n\r\n1) Navigate to Security > Attack discovery\r\n\r\n2) Click the settings gear\r\n\r\n3) Select any value above or below `100` in the Alerts range slider\r\n\r\n4) Click `Reset`\r\n\r\n**Expected result**\r\n\r\n- The range slider resets to `100`","sha":"96585a540b2c5c717ecaf1f71cc2f6f69b4378f5"}},"sourceBranch":"main","suggestedTargetBranches":["8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/196939","number":196939,"mergeCommit":{"message":"[Security Solution] [Attack discovery] Updates default Attack discovery max alerts for users still using legacy models (#196939)\n\n### [Security Solution] [Attack discovery] Updates default Attack discovery max alerts for users still using legacy models\r\n\r\nIn consideration of users still using legacy models, (e.g. GPT-4 instead of GPT-4o), this PR updates `DEFAULT_ATTACK_DISCOVERY_MAX_ALERTS` from its previous value `200` in <https://github.com/elastic/kibana/pull/195669> to `100`.\r\n\r\nThis PR also includes additional tests.\r\n\r\n## Desk testing\r\n\r\n1) Navigate to Security > Attack discovery\r\n\r\n2) Click the settings gear\r\n\r\n3) Select any value above or below `100` in the Alerts range slider\r\n\r\n4) Click `Reset`\r\n\r\n**Expected result**\r\n\r\n- The range slider resets to `100`","sha":"96585a540b2c5c717ecaf1f71cc2f6f69b4378f5"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Andrew Macri <andrew.macri@elastic.co> |
||
Tim Sullivan
|
e0d0ff9d7f
|
[8.16] [Spaces] Read Security license to infer eligibility for sub feature customization (#195389) (#196924)
# Backport This will backport the following commits from `main` to `8.16`: - [[Spaces] Read Security license to infer eligibility for sub feature customization (#195389)](https://github.com/elastic/kibana/pull/195389) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Eyo O. Eyo","email":"7893459+eokoneyo@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-10-16T10:02:51Z","message":"[Spaces] Read Security license to infer eligibility for sub feature customization (#195389)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/195549\r\n\r\nThis PR adds implementation such that eligibility to allow for the\r\ntoggling of the switch for customization of sub features whilst defining\r\nprivileges that would be assigned to a space is determined from security\r\nlicense.\r\n\r\n\r\n### Before\r\n\r\n\r\n### After\r\n\r\n\r\n\r\n<!-- ### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [ ] 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- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\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—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—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-->","sha":"e6e30c20215ce7cbb8bd25d6646edc5d0a8bc33e","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Security","release_note:skip","backport missing","v9.0.0","backport:prev-major"],"number":195389,"url":"https://github.com/elastic/kibana/pull/195389","mergeCommit":{"message":"[Spaces] Read Security license to infer eligibility for sub feature customization (#195389)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/195549\r\n\r\nThis PR adds implementation such that eligibility to allow for the\r\ntoggling of the switch for customization of sub features whilst defining\r\nprivileges that would be assigned to a space is determined from security\r\nlicense.\r\n\r\n\r\n### Before\r\n\r\n\r\n### After\r\n\r\n\r\n\r\n<!-- ### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [ ] 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- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\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—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—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-->","sha":"e6e30c20215ce7cbb8bd25d6646edc5d0a8bc33e"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/195389","number":195389,"mergeCommit":{"message":"[Spaces] Read Security license to infer eligibility for sub feature customization (#195389)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/195549\r\n\r\nThis PR adds implementation such that eligibility to allow for the\r\ntoggling of the switch for customization of sub features whilst defining\r\nprivileges that would be assigned to a space is determined from security\r\nlicense.\r\n\r\n\r\n### Before\r\n\r\n\r\n### After\r\n\r\n\r\n\r\n<!-- ### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [ ] 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- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\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—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—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-->","sha":"e6e30c20215ce7cbb8bd25d6646edc5d0a8bc33e"}}]}] BACKPORT--> Co-authored-by: Eyo O. Eyo <7893459+eokoneyo@users.noreply.github.com> |
||
|
Kibana Machine
|
8094dd6d77
|
[8.16] Hide assistant's knowledge base UI when `assistantKnowledgeBaseByDefault` feature flag is disabled (#196762) (#196857)
# Backport This will backport the following commits from `main` to `8.16`: - [Hide assistant's knowledge base UI when `assistantKnowledgeBaseByDefault` feature flag is disabled (#196762)](https://github.com/elastic/kibana/pull/196762) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Ievgen Sorokopud","email":"ievgen.sorokopud@elastic.co"},"sourceCommit":{"committedDate":"2024-10-18T11:35:04Z","message":"Hide assistant's knowledge base UI when `assistantKnowledgeBaseByDefault` feature flag is disabled (#196762)\n\n## Summary\r\n\r\nThis is the followup to https://github.com/elastic/kibana/pull/195733\r\nwhere we implemented the RBAC to allow managing Global Knowledge Base\r\ndocs. With those changes we introduced a bug where we do not hide the\r\nRBAC configuration setting when `assistantKnowledgeBaseByDefault`\r\nfeature flag is disabled. It means that in Serverless users will see\r\nthis setting but it will do nothing for them.\r\n\r\n### Screenshots of the fixed behaviour\r\n\r\n* `assistantKnowledgeBaseByDefault = true`\r\n\r\n\r\n\r\n\r\n* `assistantKnowledgeBaseByDefault = false`\r\n\r\n\r\n","sha":"f6e8065dd75116ddf596b77f75a8468804008323","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Feature:Security Assistant","Team:Security Generative AI","v8.16.0","backport:version"],"title":"Hide assistant's knowledge base UI when `assistantKnowledgeBaseByDefault` feature flag is disabled","number":196762,"url":"https://github.com/elastic/kibana/pull/196762","mergeCommit":{"message":"Hide assistant's knowledge base UI when `assistantKnowledgeBaseByDefault` feature flag is disabled (#196762)\n\n## Summary\r\n\r\nThis is the followup to https://github.com/elastic/kibana/pull/195733\r\nwhere we implemented the RBAC to allow managing Global Knowledge Base\r\ndocs. With those changes we introduced a bug where we do not hide the\r\nRBAC configuration setting when `assistantKnowledgeBaseByDefault`\r\nfeature flag is disabled. It means that in Serverless users will see\r\nthis setting but it will do nothing for them.\r\n\r\n### Screenshots of the fixed behaviour\r\n\r\n* `assistantKnowledgeBaseByDefault = true`\r\n\r\n\r\n\r\n\r\n* `assistantKnowledgeBaseByDefault = false`\r\n\r\n\r\n","sha":"f6e8065dd75116ddf596b77f75a8468804008323"}},"sourceBranch":"main","suggestedTargetBranches":["8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/196762","number":196762,"mergeCommit":{"message":"Hide assistant's knowledge base UI when `assistantKnowledgeBaseByDefault` feature flag is disabled (#196762)\n\n## Summary\r\n\r\nThis is the followup to https://github.com/elastic/kibana/pull/195733\r\nwhere we implemented the RBAC to allow managing Global Knowledge Base\r\ndocs. With those changes we introduced a bug where we do not hide the\r\nRBAC configuration setting when `assistantKnowledgeBaseByDefault`\r\nfeature flag is disabled. It means that in Serverless users will see\r\nthis setting but it will do nothing for them.\r\n\r\n### Screenshots of the fixed behaviour\r\n\r\n* `assistantKnowledgeBaseByDefault = true`\r\n\r\n\r\n\r\n\r\n* `assistantKnowledgeBaseByDefault = false`\r\n\r\n\r\n","sha":"f6e8065dd75116ddf596b77f75a8468804008323"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Ievgen Sorokopud <ievgen.sorokopud@elastic.co> |
||
|
Kibana Machine
|
21a3625dd5
|
[8.16] [ML] Transforms: Limit the data grid result window (#196510) (#196829)
# Backport This will backport the following commits from `main` to `8.16`: - [[ML] Transforms: Limit the data grid result window (#196510)](https://github.com/elastic/kibana/pull/196510) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Robert Jaszczurek","email":"92210485+rbrtj@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-10-18T09:45:10Z","message":"[ML] Transforms: Limit the data grid result window (#196510)\n\n## Summary\r\n\r\nFix for: [#196101](https://github.com/elastic/kibana/issues/196101)\r\nAdded a limit for grid data, capping it at a max of `10000` documents,\r\nas any number above this triggers an error due to ES pagination\r\nlimitations. Since this is only a preview, displaying all the data in\r\nthe grid is unnecessary.\r\nAfter:\r\n\r\n\r\n\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---------\r\n\r\nCo-authored-by: István Zoltán Szabó <istvan.szabo@elastic.co>","sha":"592225dfb6ffefa2717b49479491231dec12ecf2","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix",":ml","v9.0.0","Team:ML","v8.16.0","backport:version"],"title":"[ML] Transforms: Limit the data grid result window","number":196510,"url":"https://github.com/elastic/kibana/pull/196510","mergeCommit":{"message":"[ML] Transforms: Limit the data grid result window (#196510)\n\n## Summary\r\n\r\nFix for: [#196101](https://github.com/elastic/kibana/issues/196101)\r\nAdded a limit for grid data, capping it at a max of `10000` documents,\r\nas any number above this triggers an error due to ES pagination\r\nlimitations. Since this is only a preview, displaying all the data in\r\nthe grid is unnecessary.\r\nAfter:\r\n\r\n\r\n\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---------\r\n\r\nCo-authored-by: István Zoltán Szabó <istvan.szabo@elastic.co>","sha":"592225dfb6ffefa2717b49479491231dec12ecf2"}},"sourceBranch":"main","suggestedTargetBranches":["8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/196510","number":196510,"mergeCommit":{"message":"[ML] Transforms: Limit the data grid result window (#196510)\n\n## Summary\r\n\r\nFix for: [#196101](https://github.com/elastic/kibana/issues/196101)\r\nAdded a limit for grid data, capping it at a max of `10000` documents,\r\nas any number above this triggers an error due to ES pagination\r\nlimitations. Since this is only a preview, displaying all the data in\r\nthe grid is unnecessary.\r\nAfter:\r\n\r\n\r\n\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---------\r\n\r\nCo-authored-by: István Zoltán Szabó <istvan.szabo@elastic.co>","sha":"592225dfb6ffefa2717b49479491231dec12ecf2"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Robert Jaszczurek <92210485+rbrtj@users.noreply.github.com> |
||
|
Kibana Machine
|
b363915825
|
[8.16] [Cloud Security] Remove Cursor pointer when hovering over Distribution Bar (#196402) (#196625)
# Backport This will backport the following commits from `main` to `8.16`: - [[Cloud Security] Remove Cursor pointer when hovering over Distribution Bar (#196402)](https://github.com/elastic/kibana/pull/196402) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Rickyanto Ang","email":"rickyangwyn@gmail.com"},"sourceCommit":{"committedDate":"2024-10-17T03:21:19Z","message":"[Cloud Security] Remove Cursor pointer when hovering over Distribution Bar (#196402)\n\n## Summary\r\n\r\nCurrently since clicking on Distribution Bar on Alerts Flyout or\r\nContextual Flyout doesn't do anything (like filtering), showing pointer\r\ncursor when user hovers over the Distribution is a bit misleading. As\r\nsuch this PR removes that cursor pointer when hovering over the bar.\r\nOnce we have the filter functionality, we will add it back","sha":"455e91ae970b6b54bae8de8d247feb73a90aa558","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Cloud Security","backport:prev-minor","v8.16.0"],"title":"[Cloud Security] Remove Cursor pointer when hovering over Distribution Bar","number":196402,"url":"https://github.com/elastic/kibana/pull/196402","mergeCommit":{"message":"[Cloud Security] Remove Cursor pointer when hovering over Distribution Bar (#196402)\n\n## Summary\r\n\r\nCurrently since clicking on Distribution Bar on Alerts Flyout or\r\nContextual Flyout doesn't do anything (like filtering), showing pointer\r\ncursor when user hovers over the Distribution is a bit misleading. As\r\nsuch this PR removes that cursor pointer when hovering over the bar.\r\nOnce we have the filter functionality, we will add it back","sha":"455e91ae970b6b54bae8de8d247feb73a90aa558"}},"sourceBranch":"main","suggestedTargetBranches":["8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/196402","number":196402,"mergeCommit":{"message":"[Cloud Security] Remove Cursor pointer when hovering over Distribution Bar (#196402)\n\n## Summary\r\n\r\nCurrently since clicking on Distribution Bar on Alerts Flyout or\r\nContextual Flyout doesn't do anything (like filtering), showing pointer\r\ncursor when user hovers over the Distribution is a bit misleading. As\r\nsuch this PR removes that cursor pointer when hovering over the bar.\r\nOnce we have the filter functionality, we will add it back","sha":"455e91ae970b6b54bae8de8d247feb73a90aa558"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Rickyanto Ang <rickyangwyn@gmail.com> |