mirror of
https://github.com/elastic/kibana.git
synced 2025-04-22 08:49:27 -04:00
6628 commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
Kibana Machine
|
4ef8c31807
|
[8.18] [Discover] Stop keydown event propagation when unified doc tabs are focused (#218131) (#218300) (#218537)
# Backport This will backport the following commits from `main` to `8.18`: - [[Discover] Stop keydown event propagation when unified doc tabs are focused (#218131) (#218300)](https://github.com/elastic/kibana/pull/218300) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Alejandro García Parrondo","email":"31973472+AlexGPlay@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-17T09:02:50Z","message":"[Discover] Stop keydown event propagation when unified doc tabs are focused (#218131) (#218300)\n\n## Summary\n\nWhen a tab was focused and the right or left arrow keys were used it was\nchanging the focused tab and the selected document, it should only\nchange the selected tab.\n\nFixes |
||
Ola Pawlus
|
c744aebc17
|
[8.18] [Dashboards] Update response on HTTP API should return a 200, not 201 (#217054) (#217494)
# Backport This will backport the following commits from `main` to `8.18`: - [[Dashboards] Update response on HTTP API should return a 200, not 201 (#217054)](https://github.com/elastic/kibana/pull/217054) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Ola","email":"98127445+olapawlus@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-04T17:48:58Z","message":"[Dashboards] Update response on HTTP API should return a 200, not 201 (#217054)\n\n## Summary\n\nChanges response from 201 to 200 in the dashboard updateRoute.\n\nCloses: #212673","sha":"3c2b4daf97fdaea09cd1cd33b71c561344ec90b0","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","Team:Presentation","backport:version","v9.1.0","v8.18.1","v9.0.1","v8.17.5"],"title":"[Dashboards] Update response on HTTP API should return a 200, not 201 ","number":217054,"url":"https://github.com/elastic/kibana/pull/217054","mergeCommit":{"message":"[Dashboards] Update response on HTTP API should return a 200, not 201 (#217054)\n\n## Summary\n\nChanges response from 201 to 200 in the dashboard updateRoute.\n\nCloses: #212673","sha":"3c2b4daf97fdaea09cd1cd33b71c561344ec90b0"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","9.0","8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/217054","number":217054,"mergeCommit":{"message":"[Dashboards] Update response on HTTP API should return a 200, not 201 (#217054)\n\n## Summary\n\nChanges response from 201 to 200 in the dashboard updateRoute.\n\nCloses: #212673","sha":"3c2b4daf97fdaea09cd1cd33b71c561344ec90b0"}},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> |
||
|
Kibana Machine
|
32ef6e1478
|
[8.18] [Dashboard] Fix page object getPanels method for new grid system (#217812) (#217857)
# Backport This will backport the following commits from `main` to `8.18`: - [[Dashboard] Fix page object getPanels method for new grid system (#217812)](https://github.com/elastic/kibana/pull/217812) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Marco Liberati","email":"dej611@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-10T14:22:27Z","message":"[Dashboard] Fix page object getPanels method for new grid system (#217812)\n\n## Summary\n\n@umbopepato made me notice that this method was always returning an\nempty list of element.\nThat was due to the selector used was targeting the old grid system.\nThis PR fixes that using the right selector for the new grid system.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"ff0ba15eaa2f63a6e8ba09454ac5fb4476d1353f","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Dashboard","Team:Presentation","loe:small","release_note:skip","impact:low","backport:all-open","FTR","v9.1.0"],"title":"[Dashboard] Fix page object getPanels method for new grid system","number":217812,"url":"https://github.com/elastic/kibana/pull/217812","mergeCommit":{"message":"[Dashboard] Fix page object getPanels method for new grid system (#217812)\n\n## Summary\n\n@umbopepato made me notice that this method was always returning an\nempty list of element.\nThat was due to the selector used was targeting the old grid system.\nThis PR fixes that using the right selector for the new grid system.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"ff0ba15eaa2f63a6e8ba09454ac5fb4476d1353f"}},"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/217812","number":217812,"mergeCommit":{"message":"[Dashboard] Fix page object getPanels method for new grid system (#217812)\n\n## Summary\n\n@umbopepato made me notice that this method was always returning an\nempty list of element.\nThat was due to the selector used was targeting the old grid system.\nThis PR fixes that using the right selector for the new grid system.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"ff0ba15eaa2f63a6e8ba09454ac5fb4476d1353f"}}]}] BACKPORT--> Co-authored-by: Marco Liberati <dej611@users.noreply.github.com> |
||
|
Kibana Machine
|
fb8150da8e
|
[8.18] [Discover] Fix getAdditionalCellActions FTR tests (#216540) (#216858)
# Backport This will backport the following commits from `main` to `8.18`: - [[Discover] Fix `getAdditionalCellActions` FTR tests (#216540)](https://github.com/elastic/kibana/pull/216540) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Davis McPhee","email":"davis.mcphee@elastic.co"},"sourceCommit":{"committedDate":"2025-04-02T14:45:08Z","message":"[Discover] Fix `getAdditionalCellActions` FTR tests (#216540)\n\n## Summary\n\nThis PR fixes the `getAdditionalCellActions` FTR tests that started\nfailing due to an issue dismissing alerts.\n\nResolves #213300.\nResolves #213422.\n\n### Checklist\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"d08e5521f28f4459a76b7176b902efbaea023b06","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:DataDiscovery","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"[Discover] Fix `getAdditionalCellActions` FTR tests","number":216540,"url":"https://github.com/elastic/kibana/pull/216540","mergeCommit":{"message":"[Discover] Fix `getAdditionalCellActions` FTR tests (#216540)\n\n## Summary\n\nThis PR fixes the `getAdditionalCellActions` FTR tests that started\nfailing due to an issue dismissing alerts.\n\nResolves #213300.\nResolves #213422.\n\n### Checklist\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"d08e5521f28f4459a76b7176b902efbaea023b06"}},"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/216540","number":216540,"mergeCommit":{"message":"[Discover] Fix `getAdditionalCellActions` FTR tests (#216540)\n\n## Summary\n\nThis PR fixes the `getAdditionalCellActions` FTR tests that started\nfailing due to an issue dismissing alerts.\n\nResolves #213300.\nResolves #213422.\n\n### Checklist\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"d08e5521f28f4459a76b7176b902efbaea023b06"}}]}] BACKPORT--> Co-authored-by: Davis McPhee <davis.mcphee@elastic.co> |
||
|
Kibana Machine
|
efa90a360d
|
[8.18] [Vega] Fix update vega spec in functional tests (#216620) (#216673)
# Backport This will backport the following commits from `main` to `8.18`: - [[Vega] Fix update vega spec in functional tests (#216620)](https://github.com/elastic/kibana/pull/216620) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Marco Vettorello","email":"marco.vettorello@elastic.co"},"sourceCommit":{"committedDate":"2025-04-01T15:26:17Z","message":"[Vega] Fix update vega spec in functional tests (#216620)\n\n## Summary\n\nThis PR fixes a flaky test practice that was causing issues in 7.17\nbranch.\nThe flakiness was introduced long ago when the choosen method to\nupdate/add more content to the Vega Spec was done by manually clicking\nin the Vega spec editor the left border (where the editor shows the line\nnumbers) to select all the text in the editor and go to the last line\nbut a char before the end of the text (right before the closing\nbracket).\n\nThe failure highlighted by\nhttps://github.com/elastic/kibana/issues/213646 where caused the added\n`config` text positioned in the wrong line/column due to the Konami Code\nlike type of functional test operation.\n\n\nThe fix instead provides a more robust method: it takes the written text\nin the editor, parse it to JSON, update the JSON and write it back again\nto the editor.\n\nWill fix the issue https://github.com/elastic/kibana/issues/213646 when\nbackported to 7.17.","sha":"200ec10593480edc3ef7b0d0ea77b29c787d1382","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["test","Team:Visualizations","release_note:skip","backport:all-open","v9.1.0"],"title":"[Vega] Fix update vega spec in functional tests","number":216620,"url":"https://github.com/elastic/kibana/pull/216620","mergeCommit":{"message":"[Vega] Fix update vega spec in functional tests (#216620)\n\n## Summary\n\nThis PR fixes a flaky test practice that was causing issues in 7.17\nbranch.\nThe flakiness was introduced long ago when the choosen method to\nupdate/add more content to the Vega Spec was done by manually clicking\nin the Vega spec editor the left border (where the editor shows the line\nnumbers) to select all the text in the editor and go to the last line\nbut a char before the end of the text (right before the closing\nbracket).\n\nThe failure highlighted by\nhttps://github.com/elastic/kibana/issues/213646 where caused the added\n`config` text positioned in the wrong line/column due to the Konami Code\nlike type of functional test operation.\n\n\nThe fix instead provides a more robust method: it takes the written text\nin the editor, parse it to JSON, update the JSON and write it back again\nto the editor.\n\nWill fix the issue https://github.com/elastic/kibana/issues/213646 when\nbackported to 7.17.","sha":"200ec10593480edc3ef7b0d0ea77b29c787d1382"}},"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/216620","number":216620,"mergeCommit":{"message":"[Vega] Fix update vega spec in functional tests (#216620)\n\n## Summary\n\nThis PR fixes a flaky test practice that was causing issues in 7.17\nbranch.\nThe flakiness was introduced long ago when the choosen method to\nupdate/add more content to the Vega Spec was done by manually clicking\nin the Vega spec editor the left border (where the editor shows the line\nnumbers) to select all the text in the editor and go to the last line\nbut a char before the end of the text (right before the closing\nbracket).\n\nThe failure highlighted by\nhttps://github.com/elastic/kibana/issues/213646 where caused the added\n`config` text positioned in the wrong line/column due to the Konami Code\nlike type of functional test operation.\n\n\nThe fix instead provides a more robust method: it takes the written text\nin the editor, parse it to JSON, update the JSON and write it back again\nto the editor.\n\nWill fix the issue https://github.com/elastic/kibana/issues/213646 when\nbackported to 7.17.","sha":"200ec10593480edc3ef7b0d0ea77b29c787d1382"}}]}] BACKPORT--> Co-authored-by: Marco Vettorello <marco.vettorello@elastic.co> |
||
|
Kibana Machine
|
4c972fddad
|
[8.18] [Lens] fix drag and drop ghost after Chrome update to 134 (#213928) (#214125)
# Backport This will backport the following commits from `main` to `8.18`: - https://github.com/elastic/kibana/pull/213928 - https://github.com/elastic/kibana/pull/215439 <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Marta Bondyra","email":"4283304+mbondyra@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-12T11:30:51Z","message":"[Lens] fix drag and drop ghost after Chrome update to 134 (#213928)\n\n## Summary\nFixes https://github.com/elastic/kibana/issues/213708\n\nFixes the ghost display. As @nickofthyme pointed out\n[here](https://github.com/elastic/kibana/issues/213708#issuecomment-2712076212),\nthe reason was using inset-inline-start: -10000px for the keyboard\nhandler that is one of the children of the draggable component. The\nquick fix is to just move it outside of the html element that is\ndragged. @markov00 please assesswhere it should be merged 🙏🏼\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"84ae9c98c208957b3efc02c6b00bed8d567d4209","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Discover","release_note:fix","Team:Visualizations","Feature:Lens","backport:prev-minor","backport:prev-major","Feature:UnifiedFieldList","v9.1.0"],"title":"[Lens] fix drag and drop ghost after Chrome update to 134","number":213928,"url":"https://github.com/elastic/kibana/pull/213928","mergeCommit":{"message":"[Lens] fix drag and drop ghost after Chrome update to 134 (#213928)\n\n## Summary\nFixes https://github.com/elastic/kibana/issues/213708\n\nFixes the ghost display. As @nickofthyme pointed out\n[here](https://github.com/elastic/kibana/issues/213708#issuecomment-2712076212),\nthe reason was using inset-inline-start: -10000px for the keyboard\nhandler that is one of the children of the draggable component. The\nquick fix is to just move it outside of the html element that is\ndragged. @markov00 please assesswhere it should be merged 🙏🏼\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"84ae9c98c208957b3efc02c6b00bed8d567d4209"}},"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/213928","number":213928,"mergeCommit":{"message":"[Lens] fix drag and drop ghost after Chrome update to 134 (#213928)\n\n## Summary\nFixes https://github.com/elastic/kibana/issues/213708\n\nFixes the ghost display. As @nickofthyme pointed out\n[here](https://github.com/elastic/kibana/issues/213708#issuecomment-2712076212),\nthe reason was using inset-inline-start: -10000px for the keyboard\nhandler that is one of the children of the draggable component. The\nquick fix is to just move it outside of the html element that is\ndragged. @markov00 please assesswhere it should be merged 🙏🏼\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"84ae9c98c208957b3efc02c6b00bed8d567d4209"}}]}] BACKPORT--> --------- Co-authored-by: Marta Bondyra <4283304+mbondyra@users.noreply.github.com> Co-authored-by: Nick Partridge <nicholas.partridge@elastic.co> |
||
|
Kibana Machine
|
11a542236b | skip failing test suite (#213300) | ||
|
Kibana Machine
|
d8f0411980 | skip failing test suite (#213288) | ||
Gerard Soldevila
|
36fa5a4da6
|
[8.18] SKA: Relocate "platform" packages that remain on /packages (208704) (#212751)
# Backport This will backport the following commits from `main` to `8.18`: - #208704 |
||
|
Kibana Machine
|
625fba329f
|
[8.18] [Lens/SCSS] Replace expression legacy metric scss (#209546) (#212883)
# Backport This will backport the following commits from `main` to `8.18`: - [[Lens/SCSS] Replace expression legacy metric scss (#209546)](https://github.com/elastic/kibana/pull/209546) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Maria Iriarte","email":"106958839+mariairiartef@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-03T11:34:35Z","message":"[Lens/SCSS] Replace expression legacy metric scss (#209546)\n\n## Summary\n\nPart of https://github.com/elastic/kibana/issues/208908\n\nReplaces scss to css-in-js.\n\n### Checklist\n\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: Marta Bondyra <4283304+mbondyra@users.noreply.github.com>","sha":"8cb484cb8da605a3fbd3b11a7e89a2a921091c9d","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["technical debt","Team:Visualizations","release_note:skip","Feature:Lens","v9.0.0","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Lens/SCSS] Replace expression legacy metric scss","number":209546,"url":"https://github.com/elastic/kibana/pull/209546","mergeCommit":{"message":"[Lens/SCSS] Replace expression legacy metric scss (#209546)\n\n## Summary\n\nPart of https://github.com/elastic/kibana/issues/208908\n\nReplaces scss to css-in-js.\n\n### Checklist\n\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: Marta Bondyra <4283304+mbondyra@users.noreply.github.com>","sha":"8cb484cb8da605a3fbd3b11a7e89a2a921091c9d"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/209546","number":209546,"mergeCommit":{"message":"[Lens/SCSS] Replace expression legacy metric scss (#209546)\n\n## Summary\n\nPart of https://github.com/elastic/kibana/issues/208908\n\nReplaces scss to css-in-js.\n\n### Checklist\n\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: Marta Bondyra <4283304+mbondyra@users.noreply.github.com>","sha":"8cb484cb8da605a3fbd3b11a7e89a2a921091c9d"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Maria Iriarte <106958839+mariairiartef@users.noreply.github.com> |
||
|
Kibana Machine
|
c757030e4b
|
[8.18] [Data View Field] Fix popularity score bugs (#211201) (#212615)
# Backport This will backport the following commits from `main` to `8.18`: - [[Data View Field] Fix popularity score bugs (#211201)](https://github.com/elastic/kibana/pull/211201) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Julia Rechkunova","email":"julia.rechkunova@elastic.co"},"sourceCommit":{"committedDate":"2025-02-27T10:34:22Z","message":"[Data View Field] Fix popularity score bugs (#211201)\n\n- Fixes https://github.com/elastic/kibana/issues/211109\n\n## Summary\n\nThis PR fixes a number of bugs in fields popularity logic:\n- [x] If field popularity was customized via UI form, the value will be\nsaved now as a number instead of a string\n- [x] Same for runtime fields in another part of the code\n- [x] Since the data was polluted with string values, this PR makes sure\nthat the incrementing would still work and the result would be converted\nto number.\n- [x] If user opened the field flyout, when selected/deselected fields\nas columns in the table, then opened the field flyout again, the data\nshown as Popularity was outdated. Now it should be fixed.\n- [x] Prevents reseting of Popularity scores in other fields.\n- [x] Functional tests in\n`test/functional/apps/discover/group6/_sidebar.ts` and\n`test/functional/apps/management/data_views/_index_pattern_popularity.ts`.\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"97260415030a3b816b3a8507c51c4a5184ff25df","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Feature:Data Views","v9.0.0","Team:DataDiscovery","backport:version","v8.17.0","v8.18.0","v9.1.0","v8.19.0"],"title":"[Data View Field] Fix popularity score bugs ","number":211201,"url":"https://github.com/elastic/kibana/pull/211201","mergeCommit":{"message":"[Data View Field] Fix popularity score bugs (#211201)\n\n- Fixes https://github.com/elastic/kibana/issues/211109\n\n## Summary\n\nThis PR fixes a number of bugs in fields popularity logic:\n- [x] If field popularity was customized via UI form, the value will be\nsaved now as a number instead of a string\n- [x] Same for runtime fields in another part of the code\n- [x] Since the data was polluted with string values, this PR makes sure\nthat the incrementing would still work and the result would be converted\nto number.\n- [x] If user opened the field flyout, when selected/deselected fields\nas columns in the table, then opened the field flyout again, the data\nshown as Popularity was outdated. Now it should be fixed.\n- [x] Prevents reseting of Popularity scores in other fields.\n- [x] Functional tests in\n`test/functional/apps/discover/group6/_sidebar.ts` and\n`test/functional/apps/management/data_views/_index_pattern_popularity.ts`.\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"97260415030a3b816b3a8507c51c4a5184ff25df"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.17","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/211201","number":211201,"mergeCommit":{"message":"[Data View Field] Fix popularity score bugs (#211201)\n\n- Fixes https://github.com/elastic/kibana/issues/211109\n\n## Summary\n\nThis PR fixes a number of bugs in fields popularity logic:\n- [x] If field popularity was customized via UI form, the value will be\nsaved now as a number instead of a string\n- [x] Same for runtime fields in another part of the code\n- [x] Since the data was polluted with string values, this PR makes sure\nthat the incrementing would still work and the result would be converted\nto number.\n- [x] If user opened the field flyout, when selected/deselected fields\nas columns in the table, then opened the field flyout again, the data\nshown as Popularity was outdated. Now it should be fixed.\n- [x] Prevents reseting of Popularity scores in other fields.\n- [x] Functional tests in\n`test/functional/apps/discover/group6/_sidebar.ts` and\n`test/functional/apps/management/data_views/_index_pattern_popularity.ts`.\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"97260415030a3b816b3a8507c51c4a5184ff25df"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Julia Rechkunova <julia.rechkunova@elastic.co> |
||
Davis McPhee
|
375cc499a2
|
[8.18] [Discover] [Embeddable] Fix Discover session embeddable drilldown (#211678) (#212147)
# Backport This will backport the following commits from `main` to `8.18`: - [[Discover] [Embeddable] Fix Discover session embeddable drilldown (#211678)](https://github.com/elastic/kibana/pull/211678) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Davis McPhee","email":"davis.mcphee@elastic.co"},"sourceCommit":{"committedDate":"2025-02-21T17:26:22Z","message":"[Discover] [Embeddable] Fix Discover session embeddable drilldown (#211678)\n\n## Summary\n\nThis PR re-adds drilldown support to the Discover session embeddable\nafter it was accidentally removed during the refactoring in #180536\n(related PR where drilldowns / dynamic actions were refactored:\n#178896). A new functional test has also been added to prevent future\nregressions.\n\nFixes #211677.\n\n### Checklist\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Matthias Wilhelm <matthias.wilhelm@elastic.co>","sha":"257971d4c0f99c0da56b9b817cff731977f8891f","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Discover","release_note:fix","Team:DataDiscovery","backport:prev-major","v9.1.0"],"title":"[Discover] [Embeddable] Fix Discover session embeddable drilldown","number":211678,"url":"https://github.com/elastic/kibana/pull/211678","mergeCommit":{"message":"[Discover] [Embeddable] Fix Discover session embeddable drilldown (#211678)\n\n## Summary\n\nThis PR re-adds drilldown support to the Discover session embeddable\nafter it was accidentally removed during the refactoring in #180536\n(related PR where drilldowns / dynamic actions were refactored:\n#178896). A new functional test has also been added to prevent future\nregressions.\n\nFixes #211677.\n\n### Checklist\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Matthias Wilhelm <matthias.wilhelm@elastic.co>","sha":"257971d4c0f99c0da56b9b817cff731977f8891f"}},"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/211678","number":211678,"mergeCommit":{"message":"[Discover] [Embeddable] Fix Discover session embeddable drilldown (#211678)\n\n## Summary\n\nThis PR re-adds drilldown support to the Discover session embeddable\nafter it was accidentally removed during the refactoring in #180536\n(related PR where drilldowns / dynamic actions were refactored:\n#178896). A new functional test has also been added to prevent future\nregressions.\n\nFixes #211677.\n\n### Checklist\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Matthias Wilhelm <matthias.wilhelm@elastic.co>","sha":"257971d4c0f99c0da56b9b817cff731977f8891f"}},{"url":"https://github.com/elastic/kibana/pull/212142","number":212142,"branch":"8.17","state":"OPEN"}]}] BACKPORT--> |
||
|
Kibana Machine
|
d0d21b19be
|
[8.18] [Lens] Remove scss from annotations plugin, visualization-ui-components and gauge expression (#208891) (#211565)
# Backport This will backport the following commits from `main` to `8.18`: - [[Lens] Remove scss from annotations plugin, visualization-ui-components and gauge expression (#208891)](https://github.com/elastic/kibana/pull/208891) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Marta Bondyra","email":"4283304+mbondyra@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-18T12:31:09Z","message":"[Lens] Remove scss from annotations plugin, visualization-ui-components and gauge expression (#208891)\n\n## Summary\r\n\r\npart of https://github.com/elastic/kibana/issues/208908\r\n\r\nReplaces scss to css-in-js. I've tested all the changes.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"91a19c0969bc140ad4c16e69eb23f424b0ecae4f","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Visualizations","release_note:skip","Feature:Lens","v9.0.0","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Lens] Remove scss from annotations plugin, visualization-ui-components and gauge expression","number":208891,"url":"https://github.com/elastic/kibana/pull/208891","mergeCommit":{"message":"[Lens] Remove scss from annotations plugin, visualization-ui-components and gauge expression (#208891)\n\n## Summary\r\n\r\npart of https://github.com/elastic/kibana/issues/208908\r\n\r\nReplaces scss to css-in-js. I've tested all the changes.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"91a19c0969bc140ad4c16e69eb23f424b0ecae4f"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/208891","number":208891,"mergeCommit":{"message":"[Lens] Remove scss from annotations plugin, visualization-ui-components and gauge expression (#208891)\n\n## Summary\r\n\r\npart of https://github.com/elastic/kibana/issues/208908\r\n\r\nReplaces scss to css-in-js. I've tested all the changes.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"91a19c0969bc140ad4c16e69eb23f424b0ecae4f"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Marta Bondyra <4283304+mbondyra@users.noreply.github.com> |
||
|
Kibana Machine
|
dd449b3158
|
[8.18] [ES|QL] Fixes the values control FT (#211159) (#211280)
# Backport This will backport the following commits from `main` to `8.18`: - [[ES|QL] Fixes the values control FT (#211159)](https://github.com/elastic/kibana/pull/211159) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Stratoula Kalafateli","email":"efstratia.kalafateli@elastic.co"},"sourceCommit":{"committedDate":"2025-02-14T17:00:03Z","message":"[ES|QL] Fixes the values control FT (#211159)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/208454\n\nAttempt to make the value controls FR more stable","sha":"d3fd2ed7701b54f6048046d3f93e1bc8929dd686","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","Team:Presentation","Feature:ES|QL","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[ES|QL] Fixes the values control FT","number":211159,"url":"https://github.com/elastic/kibana/pull/211159","mergeCommit":{"message":"[ES|QL] Fixes the values control FT (#211159)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/208454\n\nAttempt to make the value controls FR more stable","sha":"d3fd2ed7701b54f6048046d3f93e1bc8929dd686"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","8.x"],"targetPullRequestStates":[{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/211159","number":211159,"mergeCommit":{"message":"[ES|QL] Fixes the values control FT (#211159)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/208454\n\nAttempt to make the value controls FR more stable","sha":"d3fd2ed7701b54f6048046d3f93e1bc8929dd686"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co> |
||
|
Kibana Machine
|
0eb1a283c2
|
[8.18] [Discover] Add "All logs" data view to classic nav (#209042) (#210483)
# Backport This will backport the following commits from `main` to `8.18`: - [[Discover] Add "All logs" data view to classic nav (#209042)](https://github.com/elastic/kibana/pull/209042) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Davis McPhee","email":"davis.mcphee@elastic.co"},"sourceCommit":{"committedDate":"2025-02-11T01:18:26Z","message":"[Discover] Add \"All logs\" data view to classic nav (#209042)\n\n## Summary\r\n\r\nThis PR adds the default \"All logs\" data view introduced in #205991 to\r\nthe classic nav in addition to Observability nav.\r\n\r\nResolves #209013.\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/src/platform/packages/shared/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- [ ] 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 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- [ ] [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)","sha":"37465f43d2eb8428a8cc2e845df686c10abe8abe","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","v9.0.0","Team:DataDiscovery","Team:obs-ux-logs","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Discover] Add \"All logs\" data view to classic nav","number":209042,"url":"https://github.com/elastic/kibana/pull/209042","mergeCommit":{"message":"[Discover] Add \"All logs\" data view to classic nav (#209042)\n\n## Summary\r\n\r\nThis PR adds the default \"All logs\" data view introduced in #205991 to\r\nthe classic nav in addition to Observability nav.\r\n\r\nResolves #209013.\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/src/platform/packages/shared/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- [ ] 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 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- [ ] [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)","sha":"37465f43d2eb8428a8cc2e845df686c10abe8abe"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/209042","number":209042,"mergeCommit":{"message":"[Discover] Add \"All logs\" data view to classic nav (#209042)\n\n## Summary\r\n\r\nThis PR adds the default \"All logs\" data view introduced in #205991 to\r\nthe classic nav in addition to Observability nav.\r\n\r\nResolves #209013.\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/src/platform/packages/shared/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- [ ] 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 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- [ ] [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)","sha":"37465f43d2eb8428a8cc2e845df686c10abe8abe"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Davis McPhee <davis.mcphee@elastic.co> |
||
|
Kibana Machine
|
8e98d1ac9b
|
[8.18] [Console] Refactor flaky test (#209516) (#209728)
# Backport This will backport the following commits from `main` to `8.18`: - [[Console] Refactor flaky test (#209516)](https://github.com/elastic/kibana/pull/209516) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Ignacio Rivas","email":"rivasign@gmail.com"},"sourceCommit":{"committedDate":"2025-02-05T10:28:46Z","message":"[Console] Refactor flaky test (#209516)","sha":"86497d5e7f64816b3fc2a081f84a8e686f262e57","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Console","Team:Kibana Management","release_note:skip","v9.0.0","backport:prev-major","v9.1.0","v8.19.0"],"title":"[Console] Refactor flaky test","number":209516,"url":"https://github.com/elastic/kibana/pull/209516","mergeCommit":{"message":"[Console] Refactor flaky test (#209516)","sha":"86497d5e7f64816b3fc2a081f84a8e686f262e57"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/209516","number":209516,"mergeCommit":{"message":"[Console] Refactor flaky test (#209516)","sha":"86497d5e7f64816b3fc2a081f84a8e686f262e57"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Ignacio Rivas <rivasign@gmail.com> |
||
|
Kibana Machine
|
3c314a0c5f
|
[8.18] [Discover] Unskip Edit field flyout tests (#209271) (#209605)
# Backport This will backport the following commits from `main` to `8.18`: - [[Discover] Unskip Edit field flyout tests (#209271)](https://github.com/elastic/kibana/pull/209271) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Julia Rechkunova","email":"julia.rechkunova@elastic.co"},"sourceCommit":{"committedDate":"2025-02-04T17:32:49Z","message":"[Discover] Unskip Edit field flyout tests (#209271)\n\n- Closes https://github.com/elastic/kibana/issues/193102\r\n\r\n### Checklist\r\n\r\n- [x] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed","sha":"c53140036aa87b7cd2a4e0835302228ed71d79ac","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:DataDiscovery","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Discover] Unskip Edit field flyout tests","number":209271,"url":"https://github.com/elastic/kibana/pull/209271","mergeCommit":{"message":"[Discover] Unskip Edit field flyout tests (#209271)\n\n- Closes https://github.com/elastic/kibana/issues/193102\r\n\r\n### Checklist\r\n\r\n- [x] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed","sha":"c53140036aa87b7cd2a4e0835302228ed71d79ac"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/209271","number":209271,"mergeCommit":{"message":"[Discover] Unskip Edit field flyout tests (#209271)\n\n- Closes https://github.com/elastic/kibana/issues/193102\r\n\r\n### Checklist\r\n\r\n- [x] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed","sha":"c53140036aa87b7cd2a4e0835302228ed71d79ac"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Julia Rechkunova <julia.rechkunova@elastic.co> |
||
|
Kibana Machine
|
58c53c6702
|
[8.18] [Vega] Fix highlight for HJSON (#208858) (#209291)
# Backport This will backport the following commits from `main` to `8.18`: - [[Vega] Fix highlight for HJSON (#208858)](https://github.com/elastic/kibana/pull/208858) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Marco Vettorello","email":"marco.vettorello@elastic.co"},"sourceCommit":{"committedDate":"2025-02-03T13:18:35Z","message":"[Vega] Fix highlight for HJSON (#208858)\n\n## Summary\r\n\r\nThis PR fixes the missing highlight theme for HJSON specs in Vega.\r\nThe issue https://github.com/elastic/kibana/issues/205711 was caused by\r\nhttps://github.com/elastic/kibana/pull/182348 that inadvertently\r\nspecified the code-editor package as sideEffect free. This cause the\r\ncompiler to exclude every import without exported and used methods.\r\nThis was the case for the code-editor that registered some language\r\nhighlighters in that way.\r\n\r\nThe solution adopted here is to mark the register_language.ts file as a\r\nfile with side effects, the alternative solution can be to register\r\nthese directly from within the code_editor component.\r\nA third option is to move these registration within the monaco package\r\nwhere other languages are also registered.\r\nI'd like to leave to @elastic/appex-sharedux the preference to followup\r\nwith a better fix for the future.\r\n\r\nI'd also like to have the opinion from @elastic/kibana-operations\r\nbecause the misconfigured package issue can be seen only in production\r\nand not in development mode. Is it possible that webpack doesn't apply\r\ntreeshaking when in development mode?\r\n\r\nfix https://github.com/elastic/kibana/issues/205711\r\nShould also fix the same issue but for TSVB Markdown\r\n\r\nThe fix was tested on CI by running at first only the CI FT with the\r\n`sideEffects:false` to verify the failure (see\r\n[build](https://buildkite.com/elastic/kibana-pull-request/builds/272375))\r\nand then with the fix specifying the actual file that contains side\r\neffects.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"7260564f6a9cd7da71a80e9bd57d836a0bea57c4","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:TSVB","release_note:fix","Feature:Vega","Team:Visualizations","backport:prev-major","v9.1.0"],"title":"[Vega] Fix highlight for HJSON","number":208858,"url":"https://github.com/elastic/kibana/pull/208858","mergeCommit":{"message":"[Vega] Fix highlight for HJSON (#208858)\n\n## Summary\r\n\r\nThis PR fixes the missing highlight theme for HJSON specs in Vega.\r\nThe issue https://github.com/elastic/kibana/issues/205711 was caused by\r\nhttps://github.com/elastic/kibana/pull/182348 that inadvertently\r\nspecified the code-editor package as sideEffect free. This cause the\r\ncompiler to exclude every import without exported and used methods.\r\nThis was the case for the code-editor that registered some language\r\nhighlighters in that way.\r\n\r\nThe solution adopted here is to mark the register_language.ts file as a\r\nfile with side effects, the alternative solution can be to register\r\nthese directly from within the code_editor component.\r\nA third option is to move these registration within the monaco package\r\nwhere other languages are also registered.\r\nI'd like to leave to @elastic/appex-sharedux the preference to followup\r\nwith a better fix for the future.\r\n\r\nI'd also like to have the opinion from @elastic/kibana-operations\r\nbecause the misconfigured package issue can be seen only in production\r\nand not in development mode. Is it possible that webpack doesn't apply\r\ntreeshaking when in development mode?\r\n\r\nfix https://github.com/elastic/kibana/issues/205711\r\nShould also fix the same issue but for TSVB Markdown\r\n\r\nThe fix was tested on CI by running at first only the CI FT with the\r\n`sideEffects:false` to verify the failure (see\r\n[build](https://buildkite.com/elastic/kibana-pull-request/builds/272375))\r\nand then with the fix specifying the actual file that contains side\r\neffects.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"7260564f6a9cd7da71a80e9bd57d836a0bea57c4"}},"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/208858","number":208858,"mergeCommit":{"message":"[Vega] Fix highlight for HJSON (#208858)\n\n## Summary\r\n\r\nThis PR fixes the missing highlight theme for HJSON specs in Vega.\r\nThe issue https://github.com/elastic/kibana/issues/205711 was caused by\r\nhttps://github.com/elastic/kibana/pull/182348 that inadvertently\r\nspecified the code-editor package as sideEffect free. This cause the\r\ncompiler to exclude every import without exported and used methods.\r\nThis was the case for the code-editor that registered some language\r\nhighlighters in that way.\r\n\r\nThe solution adopted here is to mark the register_language.ts file as a\r\nfile with side effects, the alternative solution can be to register\r\nthese directly from within the code_editor component.\r\nA third option is to move these registration within the monaco package\r\nwhere other languages are also registered.\r\nI'd like to leave to @elastic/appex-sharedux the preference to followup\r\nwith a better fix for the future.\r\n\r\nI'd also like to have the opinion from @elastic/kibana-operations\r\nbecause the misconfigured package issue can be seen only in production\r\nand not in development mode. Is it possible that webpack doesn't apply\r\ntreeshaking when in development mode?\r\n\r\nfix https://github.com/elastic/kibana/issues/205711\r\nShould also fix the same issue but for TSVB Markdown\r\n\r\nThe fix was tested on CI by running at first only the CI FT with the\r\n`sideEffects:false` to verify the failure (see\r\n[build](https://buildkite.com/elastic/kibana-pull-request/builds/272375))\r\nand then with the fix specifying the actual file that contains side\r\neffects.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"7260564f6a9cd7da71a80e9bd57d836a0bea57c4"}}]}] BACKPORT--> Co-authored-by: Marco Vettorello <marco.vettorello@elastic.co> |
||
Ania Kowalska
|
cd3114baf6
|
[8.x] refactor RowHeightSettings component to EUI layout (#203606) (#208890)
# Backport This will backport the following commits from `main` to `8.x`: - [refactor RowHeightSettings component to EUI layout (#203606)](https://github.com/elastic/kibana/pull/203606) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Ania Kowalska","email":"63072419+akowalska622@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-01-30T08:12:02Z","message":"refactor RowHeightSettings component to EUI layout (#203606)","sha":"a376e9b16944c006975053295001690baec841bb","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Discover","v9.0.0","release_note:feature","Team:DataDiscovery","backport:prev-minor"],"title":"refactor RowHeightSettings component to EUI layout","number":203606,"url":"https://github.com/elastic/kibana/pull/203606","mergeCommit":{"message":"refactor RowHeightSettings component to EUI layout (#203606)","sha":"a376e9b16944c006975053295001690baec841bb"}},"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/203606","number":203606,"mergeCommit":{"message":"refactor RowHeightSettings component to EUI layout (#203606)","sha":"a376e9b16944c006975053295001690baec841bb"}}]}] BACKPORT--> |
||
Ignacio Rivas
|
bf3b2ba669
|
[8.x] [Console] Fix flaky autocomplete test for index fields (#208503) (#208781)
# Backport This will backport the following commits from `main` to `8.x`: - [[Console] Fix flaky autocomplete test for index fields (#208503)](https://github.com/elastic/kibana/pull/208503) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Ignacio Rivas","email":"rivasign@gmail.com"},"sourceCommit":{"committedDate":"2025-01-29T14:36:02Z","message":"[Console] Fix flaky autocomplete test for index fields (#208503)","sha":"4da814d138cd87e2d03cb3378631327f091ceae9","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Console","Team:Kibana Management","release_note:skip","v9.0.0","backport:prev-minor"],"title":"[Console] Fix flaky autocomplete test for index fields","number":208503,"url":"https://github.com/elastic/kibana/pull/208503","mergeCommit":{"message":"[Console] Fix flaky autocomplete test for index fields (#208503)","sha":"4da814d138cd87e2d03cb3378631327f091ceae9"}},"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/208503","number":208503,"mergeCommit":{"message":"[Console] Fix flaky autocomplete test for index fields (#208503)","sha":"4da814d138cd87e2d03cb3378631327f091ceae9"}}]}] BACKPORT--> |
||
|
Davis McPhee
|
c40c6d69c1
|
[8.x] [Discover] In-table search (#206454) (#208868)
# Backport This will backport the following commits from `main` to `8.x`: - [[Discover] In-table search (#206454)](https://github.com/elastic/kibana/pull/206454) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Julia Rechkunova","email":"julia.rechkunova@elastic.co"},"sourceCommit":{"committedDate":"2025-01-29T23:52:07Z","message":"[Discover] In-table search (#206454)\n\n- Closes https://github.com/elastic/kibana/issues/192360\r\n\r\n## Summary\r\n\r\nThe default browser Find-in-page does not work great with the grid\r\nvirtualization and our pagination and it can only find matches in rows\r\nwhich are currently displayed.\r\n\r\nThis PR adds in-table search support to the grid so users can find\r\nmatches in all grid rows (up to `500` sample docs/rows by default) and\r\njump between them with \"Previous\"/\"Next\" buttons.\r\n\r\n\r\n\r\nThe implementation is extracted in a new package\r\n`@kbn/data-grid-in-table-search`. This would allow to use in-table\r\nsearch with `EuiDataGrid` on other pages of Kibana too.\r\n\r\n`Cmd+F` shortcut is overridden when one of grid elements is in focus\r\notherwise we keep the browser default behaviour.\r\n\r\n### Checklist\r\n\r\n- [x] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/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- [ ] 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 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- [ ] [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---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: florent-leborgne <florent.leborgne@elastic.co>","sha":"8ffb2ff62830655587d2b91e295b5d76fc86806e","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["v9.0.0","release_note:feature","Team:DataDiscovery","backport:prev-minor","Project:OneDiscover"],"title":"[Discover] In-table search","number":206454,"url":"https://github.com/elastic/kibana/pull/206454","mergeCommit":{"message":"[Discover] In-table search (#206454)\n\n- Closes https://github.com/elastic/kibana/issues/192360\r\n\r\n## Summary\r\n\r\nThe default browser Find-in-page does not work great with the grid\r\nvirtualization and our pagination and it can only find matches in rows\r\nwhich are currently displayed.\r\n\r\nThis PR adds in-table search support to the grid so users can find\r\nmatches in all grid rows (up to `500` sample docs/rows by default) and\r\njump between them with \"Previous\"/\"Next\" buttons.\r\n\r\n\r\n\r\nThe implementation is extracted in a new package\r\n`@kbn/data-grid-in-table-search`. This would allow to use in-table\r\nsearch with `EuiDataGrid` on other pages of Kibana too.\r\n\r\n`Cmd+F` shortcut is overridden when one of grid elements is in focus\r\notherwise we keep the browser default behaviour.\r\n\r\n### Checklist\r\n\r\n- [x] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/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- [ ] 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 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- [ ] [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---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: florent-leborgne <florent.leborgne@elastic.co>","sha":"8ffb2ff62830655587d2b91e295b5d76fc86806e"}},"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/206454","number":206454,"mergeCommit":{"message":"[Discover] In-table search (#206454)\n\n- Closes https://github.com/elastic/kibana/issues/192360\r\n\r\n## Summary\r\n\r\nThe default browser Find-in-page does not work great with the grid\r\nvirtualization and our pagination and it can only find matches in rows\r\nwhich are currently displayed.\r\n\r\nThis PR adds in-table search support to the grid so users can find\r\nmatches in all grid rows (up to `500` sample docs/rows by default) and\r\njump between them with \"Previous\"/\"Next\" buttons.\r\n\r\n\r\n\r\nThe implementation is extracted in a new package\r\n`@kbn/data-grid-in-table-search`. This would allow to use in-table\r\nsearch with `EuiDataGrid` on other pages of Kibana too.\r\n\r\n`Cmd+F` shortcut is overridden when one of grid elements is in focus\r\notherwise we keep the browser default behaviour.\r\n\r\n### Checklist\r\n\r\n- [x] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/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- [ ] 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 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- [ ] [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---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: florent-leborgne <florent.leborgne@elastic.co>","sha":"8ffb2ff62830655587d2b91e295b5d76fc86806e"}}]}] BACKPORT--> --------- Co-authored-by: Julia Rechkunova <julia.rechkunova@elastic.co> Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
Larry Gregory
|
24f82ee808
|
[8.x] Additional prototype pollution protections (#206073) (#208742)
# Backport This will backport the following commits from `main` to `8.x`: - [Additional prototype pollution protections (#206073)](https://github.com/elastic/kibana/pull/206073) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Larry Gregory","email":"larry.gregory@elastic.co"},"sourceCommit":{"committedDate":"2025-01-28T22:00:43Z","message":"Additional prototype pollution protections (#206073)\n\n## Summary\n\n1. Extends the server-side prototype pollution protections introduced in\nhttps://github.com/elastic/kibana/pull/190716 to include\n`Array.prototype`.\n2. Applies the same prototype pollution protections to the client-side.\n\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] Sealing prototypes on the client can lead to failures in\nthird-party dependencies. I'm relying on sufficient functional test\ncoverage to detect issues here. As a result, these protections are\ndisabled by default for now, and can be controlled via setting\n`server.prototypeHardening: true/false`\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"9ce2dd8df9f2bd6c0ba1d089b69ddfd7fc1f4a02","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Security","release_note:skip","Feature:Hardening","v9.0.0","backport:prev-minor","ci:cloud-deploy","ci:project-deploy-elasticsearch","ci:all-gen-ai-suites"],"title":"Additional prototype pollution protections","number":206073,"url":"https://github.com/elastic/kibana/pull/206073","mergeCommit":{"message":"Additional prototype pollution protections (#206073)\n\n## Summary\n\n1. Extends the server-side prototype pollution protections introduced in\nhttps://github.com/elastic/kibana/pull/190716 to include\n`Array.prototype`.\n2. Applies the same prototype pollution protections to the client-side.\n\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] Sealing prototypes on the client can lead to failures in\nthird-party dependencies. I'm relying on sufficient functional test\ncoverage to detect issues here. As a result, these protections are\ndisabled by default for now, and can be controlled via setting\n`server.prototypeHardening: true/false`\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"9ce2dd8df9f2bd6c0ba1d089b69ddfd7fc1f4a02"}},"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/206073","number":206073,"mergeCommit":{"message":"Additional prototype pollution protections (#206073)\n\n## Summary\n\n1. Extends the server-side prototype pollution protections introduced in\nhttps://github.com/elastic/kibana/pull/190716 to include\n`Array.prototype`.\n2. Applies the same prototype pollution protections to the client-side.\n\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] Sealing prototypes on the client can lead to failures in\nthird-party dependencies. I'm relying on sufficient functional test\ncoverage to detect issues here. As a result, these protections are\ndisabled by default for now, and can be controlled via setting\n`server.prototypeHardening: true/false`\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"9ce2dd8df9f2bd6c0ba1d089b69ddfd7fc1f4a02"}}]}] BACKPORT--> |
||
|
Davis McPhee
|
e6fd9e599c
|
[8.x] [Discover] Add a default "All logs" temporary data view in the Observability Solution view (#205991) (#208792)
# Backport This will backport the following commits from `main` to `8.x`: - [[Discover] Add a default "All logs" temporary data view in the Observability Solution view (#205991)](https://github.com/elastic/kibana/pull/205991) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Davis McPhee","email":"davis.mcphee@elastic.co"},"sourceCommit":{"committedDate":"2025-01-29T15:04:32Z","message":"[Discover] Add a default \"All logs\" temporary data view in the Observability Solution view (#205991)\n\n## Summary\r\n\r\nThis PR adds an \"All logs\" ad hoc (temporary) data view to the Discover\r\nObservability root profile based on the central log sources setting,\r\nallowing quick access to logs (with the most up to date log sources)\r\nwithout needing to first manually create a data view:\r\n\r\n\r\nTo support this, a new `getDefaultAdHocDataViews` extension point has\r\nbeen added to Discover, allowing profiles to specify an array of ad hoc\r\ndata view specs would should be created by default when the profile is\r\nresolved, and automatically cleaned up when the profile changes or the\r\nuser leaves Discover.\r\n\r\nResolves #201669.\r\nResolves #189166.\r\n\r\n### Notes\r\n\r\n- The \"All logs\" ad hoc data view should only appear when using the\r\nObservability Solution view (in any deployment type).\r\n- Data view specs returned from `getDefaultAdHocDataViews` must include\r\nconsistent IDs across resolutions in order for Discover to manage them\r\ncorrectly (e.g. to find and reload the data view after a page refresh).\r\nSituations where we'd expect a change in ID (e.g. when saving to a\r\nDiscover session) are handled internally by Discover.\r\n- To avoid a breaking change, the returned ad hoc data views have no\r\nimpact on the default data view shown when navigating to Discover. If\r\nany persisted data views exist, one of them will be used as the default.\r\nIf no persisted data views exist, the first entry of the array returned\r\nby `getDefaultAdHocDataViews` will be used as the default.\r\n- We still want to notify users in Discover when they have no ES data at\r\nall, and prompt them to install integrations. For this reason, the \"no\r\ndata\" page is still shown in Discover even if there are default profile\r\nad hoc data views (unlike if there are persisted data views, in which\r\ncase we use the default and hide the \"no data\" page).\r\n- When saving a Discover session that uses a default profile ad hoc data\r\nview, the data view will be copied on save as `{DATA_VIEW_NAME} (copy)`.\r\nThis allows us to assign a unique ID to the version that gets saved with\r\nthe Discover session, and avoids having to choose between the profile\r\ndata view or the embedded data view when reopening the session, which\r\nhas drawbacks:\r\n- If choosing the profile data view, the Discover session may display\r\nincorrectly if the log sources setting changed since it was saved, and\r\nthe user would no longer be able to view the session as it was intended\r\nwithout first modifying the setting to the expected value.\r\n- If choosing the embedded data view, the replacement shown after\r\nopening the Discover session may not reflect the latest log sources\r\nsetting until a new session is started, and there would be no way for\r\nthe user to migrate the session to use the latest version of the profile\r\ndata view.\r\n\r\n### Checklist\r\n\r\n- [x] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/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- [ ] 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 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)","sha":"bf9d34465eaf49738b215cdcadfadb29c4c6188c","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","v9.0.0","Team:DataDiscovery","backport:prev-minor","Team:obs-ux-logs","Project:OneDiscover"],"title":"[Discover] Add a default \"All logs\" temporary data view in the Observability Solution view","number":205991,"url":"https://github.com/elastic/kibana/pull/205991","mergeCommit":{"message":"[Discover] Add a default \"All logs\" temporary data view in the Observability Solution view (#205991)\n\n## Summary\r\n\r\nThis PR adds an \"All logs\" ad hoc (temporary) data view to the Discover\r\nObservability root profile based on the central log sources setting,\r\nallowing quick access to logs (with the most up to date log sources)\r\nwithout needing to first manually create a data view:\r\n\r\n\r\nTo support this, a new `getDefaultAdHocDataViews` extension point has\r\nbeen added to Discover, allowing profiles to specify an array of ad hoc\r\ndata view specs would should be created by default when the profile is\r\nresolved, and automatically cleaned up when the profile changes or the\r\nuser leaves Discover.\r\n\r\nResolves #201669.\r\nResolves #189166.\r\n\r\n### Notes\r\n\r\n- The \"All logs\" ad hoc data view should only appear when using the\r\nObservability Solution view (in any deployment type).\r\n- Data view specs returned from `getDefaultAdHocDataViews` must include\r\nconsistent IDs across resolutions in order for Discover to manage them\r\ncorrectly (e.g. to find and reload the data view after a page refresh).\r\nSituations where we'd expect a change in ID (e.g. when saving to a\r\nDiscover session) are handled internally by Discover.\r\n- To avoid a breaking change, the returned ad hoc data views have no\r\nimpact on the default data view shown when navigating to Discover. If\r\nany persisted data views exist, one of them will be used as the default.\r\nIf no persisted data views exist, the first entry of the array returned\r\nby `getDefaultAdHocDataViews` will be used as the default.\r\n- We still want to notify users in Discover when they have no ES data at\r\nall, and prompt them to install integrations. For this reason, the \"no\r\ndata\" page is still shown in Discover even if there are default profile\r\nad hoc data views (unlike if there are persisted data views, in which\r\ncase we use the default and hide the \"no data\" page).\r\n- When saving a Discover session that uses a default profile ad hoc data\r\nview, the data view will be copied on save as `{DATA_VIEW_NAME} (copy)`.\r\nThis allows us to assign a unique ID to the version that gets saved with\r\nthe Discover session, and avoids having to choose between the profile\r\ndata view or the embedded data view when reopening the session, which\r\nhas drawbacks:\r\n- If choosing the profile data view, the Discover session may display\r\nincorrectly if the log sources setting changed since it was saved, and\r\nthe user would no longer be able to view the session as it was intended\r\nwithout first modifying the setting to the expected value.\r\n- If choosing the embedded data view, the replacement shown after\r\nopening the Discover session may not reflect the latest log sources\r\nsetting until a new session is started, and there would be no way for\r\nthe user to migrate the session to use the latest version of the profile\r\ndata view.\r\n\r\n### Checklist\r\n\r\n- [x] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/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- [ ] 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 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)","sha":"bf9d34465eaf49738b215cdcadfadb29c4c6188c"}},"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/205991","number":205991,"mergeCommit":{"message":"[Discover] Add a default \"All logs\" temporary data view in the Observability Solution view (#205991)\n\n## Summary\r\n\r\nThis PR adds an \"All logs\" ad hoc (temporary) data view to the Discover\r\nObservability root profile based on the central log sources setting,\r\nallowing quick access to logs (with the most up to date log sources)\r\nwithout needing to first manually create a data view:\r\n\r\n\r\nTo support this, a new `getDefaultAdHocDataViews` extension point has\r\nbeen added to Discover, allowing profiles to specify an array of ad hoc\r\ndata view specs would should be created by default when the profile is\r\nresolved, and automatically cleaned up when the profile changes or the\r\nuser leaves Discover.\r\n\r\nResolves #201669.\r\nResolves #189166.\r\n\r\n### Notes\r\n\r\n- The \"All logs\" ad hoc data view should only appear when using the\r\nObservability Solution view (in any deployment type).\r\n- Data view specs returned from `getDefaultAdHocDataViews` must include\r\nconsistent IDs across resolutions in order for Discover to manage them\r\ncorrectly (e.g. to find and reload the data view after a page refresh).\r\nSituations where we'd expect a change in ID (e.g. when saving to a\r\nDiscover session) are handled internally by Discover.\r\n- To avoid a breaking change, the returned ad hoc data views have no\r\nimpact on the default data view shown when navigating to Discover. If\r\nany persisted data views exist, one of them will be used as the default.\r\nIf no persisted data views exist, the first entry of the array returned\r\nby `getDefaultAdHocDataViews` will be used as the default.\r\n- We still want to notify users in Discover when they have no ES data at\r\nall, and prompt them to install integrations. For this reason, the \"no\r\ndata\" page is still shown in Discover even if there are default profile\r\nad hoc data views (unlike if there are persisted data views, in which\r\ncase we use the default and hide the \"no data\" page).\r\n- When saving a Discover session that uses a default profile ad hoc data\r\nview, the data view will be copied on save as `{DATA_VIEW_NAME} (copy)`.\r\nThis allows us to assign a unique ID to the version that gets saved with\r\nthe Discover session, and avoids having to choose between the profile\r\ndata view or the embedded data view when reopening the session, which\r\nhas drawbacks:\r\n- If choosing the profile data view, the Discover session may display\r\nincorrectly if the log sources setting changed since it was saved, and\r\nthe user would no longer be able to view the session as it was intended\r\nwithout first modifying the setting to the expected value.\r\n- If choosing the embedded data view, the replacement shown after\r\nopening the Discover session may not reflect the latest log sources\r\nsetting until a new session is started, and there would be no way for\r\nthe user to migrate the session to use the latest version of the profile\r\ndata view.\r\n\r\n### Checklist\r\n\r\n- [x] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/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- [ ] 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 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)","sha":"bf9d34465eaf49738b215cdcadfadb29c4c6188c"}}]}] BACKPORT--> |
||
|
Kibana Machine
|
b4420391d9
|
[8.x] Fix flaky console tests (#208337) (#208682)
# Backport This will backport the following commits from `main` to `8.x`: - [Fix flaky console tests (#208337)](https://github.com/elastic/kibana/pull/208337) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Sonia Sanz Vivas","email":"sonia.sanzvivas@elastic.co"},"sourceCommit":{"committedDate":"2025-01-29T08:09:05Z","message":"Fix flaky console tests (#208337)\n\nFixes https://github.com/elastic/kibana/issues/204381\n\n## Summary\nThe test that verifies tab changes in Console was failing because it was\nverifying the presence of the tab content before it was fully loaded.\n\n\n### Checklist\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"20ed84d41d215d4cc447012948a44aa7e46cb00e","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Console","Team:Kibana Management","release_note:skip","v9.0.0","backport:prev-minor"],"title":"Fix flaky console tests","number":208337,"url":"https://github.com/elastic/kibana/pull/208337","mergeCommit":{"message":"Fix flaky console tests (#208337)\n\nFixes https://github.com/elastic/kibana/issues/204381\n\n## Summary\nThe test that verifies tab changes in Console was failing because it was\nverifying the presence of the tab content before it was fully loaded.\n\n\n### Checklist\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"20ed84d41d215d4cc447012948a44aa7e46cb00e"}},"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/208337","number":208337,"mergeCommit":{"message":"Fix flaky console tests (#208337)\n\nFixes https://github.com/elastic/kibana/issues/204381\n\n## Summary\nThe test that verifies tab changes in Console was failing because it was\nverifying the presence of the tab content before it was fully loaded.\n\n\n### Checklist\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"20ed84d41d215d4cc447012948a44aa7e46cb00e"}}]}] BACKPORT--> Co-authored-by: Sonia Sanz Vivas <sonia.sanzvivas@elastic.co> |
||
|
Kibana Machine
|
e2caff5f90
|
[8.x] [Console] Fix flaky autocomplete functional tests (#208322) (#208371)
# Backport This will backport the following commits from `main` to `8.x`: - [[Console] Fix flaky autocomplete functional tests (#208322)](https://github.com/elastic/kibana/pull/208322) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Ignacio Rivas","email":"rivasign@gmail.com"},"sourceCommit":{"committedDate":"2025-01-27T14:01:19Z","message":"[Console] Fix flaky autocomplete functional tests (#208322)","sha":"458704f475fbd6c291aea13f636d9c0ffd78535f","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Console","Team:Kibana Management","release_note:skip","v9.0.0","backport:prev-major"],"title":"[Console] Fix flaky autocomplete functional tests","number":208322,"url":"https://github.com/elastic/kibana/pull/208322","mergeCommit":{"message":"[Console] Fix flaky autocomplete functional tests (#208322)","sha":"458704f475fbd6c291aea13f636d9c0ffd78535f"}},"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/208322","number":208322,"mergeCommit":{"message":"[Console] Fix flaky autocomplete functional tests (#208322)","sha":"458704f475fbd6c291aea13f636d9c0ffd78535f"}}]}] BACKPORT--> Co-authored-by: Ignacio Rivas <rivasign@gmail.com> |
||
Stratoula Kalafateli
|
e8d3a115f4
|
[8.x] [ES|QL] Dashboard variables (#202875) (#208340)
# Backport This will backport the following commits from `main` to `8.x`: - [[ES|QL] Dashboard variables (#202875)](https://github.com/elastic/kibana/pull/202875) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Stratoula Kalafateli","email":"efstratia.kalafateli@elastic.co"},"sourceCommit":{"committedDate":"2025-01-27T10:35:54Z","message":"[ES|QL] Dashboard variables (#202875)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/203967\r\n\r\nSupports dashboard variables in ES|QL charts.\r\n\r\nThis PR introduces the first phase of ES|QL controls. In this phase:\r\n- the flow starts from Lens ES|QL editor (and no vice-versa, this will\r\nhappen on a later phase after we discuss some technical details with ES)\r\n- it is only available for dashboards (we want to include them in other\r\napps as Discover but this is the next phase driven by the presentation\r\nteam)\r\n- it supports variables for intervals, fields and values. I haven't\r\nadded support for functions. I am going to do it after this PR being\r\nmerged (there are some business questions I want to answer first)\r\n\r\nFor more info check this\r\n[deck]( |
||
Tiago Costa
|
14b57223c4
|
skip flaky suite (#204381) | ||
Nathan Reese
|
c39e129298
|
[8.x] [embeddable] make presentation interface names consistent (#205279) (#207881)
# Backport This will backport the following commits from `main` to `8.x`: - [[embeddable] make presentation interface names consistent (#205279)](https://github.com/elastic/kibana/pull/205279) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Nathan Reese","email":"reese.nathan@elastic.co"},"sourceCommit":{"committedDate":"2025-01-22T16:46:01Z","message":"[embeddable] make presentation interface names consistent (#205279)\n\nPR cleans up presentation interface names for consistentency\r\n* adds `# Backport This will backport the following commits from `main` to `8.x`: - [[embeddable] make presentation interface names consistent (#205279)](https://github.com/elastic/kibana/pull/205279) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT suffix to all observables. For example, `dataLoading` =>\r\n`dataLoading# Backport This will backport the following commits from `main` to `8.x`: - [[embeddable] make presentation interface names consistent (#205279)](https://github.com/elastic/kibana/pull/205279) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT \r\n* removes `Panel` naming convention from interface names since an api\r\nmay not be a panel, an api may be a dashboard. For example,\r\n`PublisesPanelTitle` => `PublishesTitle`\r\n\r\n#### Note to Reviewers\r\nPay special attention to any place where your application creates an\r\nuntyped API. In the example below, there is no typescript violation when\r\nthe parent returns `dataLoading` instead of `dataLoading# Backport This will backport the following commits from `main` to `8.x`: - [[embeddable] make presentation interface names consistent (#205279)](https://github.com/elastic/kibana/pull/205279) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT since the\r\nparent is not typed as `PublishesDataLoading`. Please check for\r\ninstances like these.\r\n\r\n```\r\n<ReactEmbeddableRenderer\r\n getParentApi={() => {\r\n dataLoading: new BehaviorSubject()\r\n }}\r\n/>\r\n```\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"05916056cdc84c0f59392046aa4ffc7d16e083f9","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Embedding","Team:Presentation","release_note:skip","Feature:Drilldowns","v9.0.0","Team:obs-ux-infra_services","Team:obs-ux-management","project:embeddableRebuild","backport:version","v8.18.0"],"title":"[embeddable] make presentation interface names consistent","number":205279,"url":"https://github.com/elastic/kibana/pull/205279","mergeCommit":{"message":"[embeddable] make presentation interface names consistent (#205279)\n\nPR cleans up presentation interface names for consistentency\r\n* adds `# Backport This will backport the following commits from `main` to `8.x`: - [[embeddable] make presentation interface names consistent (#205279)](https://github.com/elastic/kibana/pull/205279) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT suffix to all observables. For example, `dataLoading` =>\r\n`dataLoading# Backport This will backport the following commits from `main` to `8.x`: - [[embeddable] make presentation interface names consistent (#205279)](https://github.com/elastic/kibana/pull/205279) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT \r\n* removes `Panel` naming convention from interface names since an api\r\nmay not be a panel, an api may be a dashboard. For example,\r\n`PublisesPanelTitle` => `PublishesTitle`\r\n\r\n#### Note to Reviewers\r\nPay special attention to any place where your application creates an\r\nuntyped API. In the example below, there is no typescript violation when\r\nthe parent returns `dataLoading` instead of `dataLoading# Backport This will backport the following commits from `main` to `8.x`: - [[embeddable] make presentation interface names consistent (#205279)](https://github.com/elastic/kibana/pull/205279) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT since the\r\nparent is not typed as `PublishesDataLoading`. Please check for\r\ninstances like these.\r\n\r\n```\r\n<ReactEmbeddableRenderer\r\n getParentApi={() => {\r\n dataLoading: new BehaviorSubject()\r\n }}\r\n/>\r\n```\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"05916056cdc84c0f59392046aa4ffc7d16e083f9"}},"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/205279","number":205279,"mergeCommit":{"message":"[embeddable] make presentation interface names consistent (#205279)\n\nPR cleans up presentation interface names for consistentency\r\n* adds `# Backport This will backport the following commits from `main` to `8.x`: - [[embeddable] make presentation interface names consistent (#205279)](https://github.com/elastic/kibana/pull/205279) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT suffix to all observables. For example, `dataLoading` =>\r\n`dataLoading# Backport This will backport the following commits from `main` to `8.x`: - [[embeddable] make presentation interface names consistent (#205279)](https://github.com/elastic/kibana/pull/205279) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT \r\n* removes `Panel` naming convention from interface names since an api\r\nmay not be a panel, an api may be a dashboard. For example,\r\n`PublisesPanelTitle` => `PublishesTitle`\r\n\r\n#### Note to Reviewers\r\nPay special attention to any place where your application creates an\r\nuntyped API. In the example below, there is no typescript violation when\r\nthe parent returns `dataLoading` instead of `dataLoading# Backport This will backport the following commits from `main` to `8.x`: - [[embeddable] make presentation interface names consistent (#205279)](https://github.com/elastic/kibana/pull/205279) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT since the\r\nparent is not typed as `PublishesDataLoading`. Please check for\r\ninstances like these.\r\n\r\n```\r\n<ReactEmbeddableRenderer\r\n getParentApi={() => {\r\n dataLoading: new BehaviorSubject()\r\n }}\r\n/>\r\n```\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"05916056cdc84c0f59392046aa4ffc7d16e083f9"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
Devon Thomson
|
13d328677e
|
[8.x] [Serialized state only] Update Library Transforms and Duplicate (#206140) (#207455)
# Backport This will backport the following commits from `main` to `8.x`: - [[Serialized state only] Update Library Transforms and Duplicate (#206140)](https://github.com/elastic/kibana/pull/206140) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Devon Thomson","email":"devon.thomson@elastic.co"},"sourceCommit":{"committedDate":"2025-01-21T18:43:43Z","message":"[Serialized state only] Update Library Transforms and Duplicate (#206140)\n\nUnifies the various `LibraryTransforms` interfaces, updates all by reference capable embeddables to use them in the same way, and migrates the clone functionality to use only serialized state.","sha":"3719be0144d0f5b1fc71d1c564a41446c8ef3133","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Embedding","release_note:fix","Team:Presentation","v9.0.0","backport:prev-minor","Feature:Embeddables","project:embeddableRebuild"],"title":"[Serialized state only] Update Library Transforms and Duplicate","number":206140,"url":"https://github.com/elastic/kibana/pull/206140","mergeCommit":{"message":"[Serialized state only] Update Library Transforms and Duplicate (#206140)\n\nUnifies the various `LibraryTransforms` interfaces, updates all by reference capable embeddables to use them in the same way, and migrates the clone functionality to use only serialized state.","sha":"3719be0144d0f5b1fc71d1c564a41446c8ef3133"}},"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/206140","number":206140,"mergeCommit":{"message":"[Serialized state only] Update Library Transforms and Duplicate (#206140)\n\nUnifies the various `LibraryTransforms` interfaces, updates all by reference capable embeddables to use them in the same way, and migrates the clone functionality to use only serialized state.","sha":"3719be0144d0f5b1fc71d1c564a41446c8ef3133"}}]}] BACKPORT--> |
||
|
Kibana Machine
|
85caa94b9f
|
[8.x] [Discover] [ES|QL] Prevent redundant requests when loading Discover sessions and toggling chart visibility (#206699) (#207216)
# Backport This will backport the following commits from `main` to `8.x`: - [[Discover] [ES|QL] Prevent redundant requests when loading Discover sessions and toggling chart visibility (#206699)](https://github.com/elastic/kibana/pull/206699) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Davis McPhee","email":"davis.mcphee@elastic.co"},"sourceCommit":{"committedDate":"2025-01-20T15:11:01Z","message":"[Discover] [ES|QL] Prevent redundant requests when loading Discover sessions and toggling chart visibility (#206699)\n\n## Summary\r\n\r\nThis PR prevents redundant Discover requests in ES|QL mode for the\r\nfollowing scenarios:\r\n- Creating a new Discover session.\r\n- Saving the current Discover session.\r\n- Loading a saved Discover session.\r\n- Toggling the Unified Histogram chart visibility.\r\n\r\nIt does so by addressing several underlying state related issues that\r\nwere triggering the redundant requests:\r\n- Skipping the initial emission of `currentSuggestionContext` on Unified\r\nHistogram mount, which immediately triggered a second fetch.\r\n- Treating the Unified Histogram `table` prop the same as other props\r\nwhich affect Lens suggestions (data view, query, columns), and deferring\r\nupdates to it until result fetching completes to avoid unnecessary\r\nsuggestion updates.\r\n- Removing all auto-fetching behaviour from Unified Histogram and\r\ninstead relying solely on the consumer to control when fetching should\r\noccur (including the initial fetch).\r\n\r\nResolves #165192.\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/src/platform/packages/shared/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- [ ] 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 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---------\r\n\r\nCo-authored-by: Matthias Wilhelm <matthias.wilhelm@elastic.co>","sha":"1c7a823920c3d794dcb6ce30bbc1b075be40ac19","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Discover","release_note:fix","v9.0.0","Team:DataDiscovery","backport:prev-minor","Feature:ES|QL"],"title":"[Discover] [ES|QL] Prevent redundant requests when loading Discover sessions and toggling chart visibility","number":206699,"url":"https://github.com/elastic/kibana/pull/206699","mergeCommit":{"message":"[Discover] [ES|QL] Prevent redundant requests when loading Discover sessions and toggling chart visibility (#206699)\n\n## Summary\r\n\r\nThis PR prevents redundant Discover requests in ES|QL mode for the\r\nfollowing scenarios:\r\n- Creating a new Discover session.\r\n- Saving the current Discover session.\r\n- Loading a saved Discover session.\r\n- Toggling the Unified Histogram chart visibility.\r\n\r\nIt does so by addressing several underlying state related issues that\r\nwere triggering the redundant requests:\r\n- Skipping the initial emission of `currentSuggestionContext` on Unified\r\nHistogram mount, which immediately triggered a second fetch.\r\n- Treating the Unified Histogram `table` prop the same as other props\r\nwhich affect Lens suggestions (data view, query, columns), and deferring\r\nupdates to it until result fetching completes to avoid unnecessary\r\nsuggestion updates.\r\n- Removing all auto-fetching behaviour from Unified Histogram and\r\ninstead relying solely on the consumer to control when fetching should\r\noccur (including the initial fetch).\r\n\r\nResolves #165192.\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/src/platform/packages/shared/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- [ ] 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 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---------\r\n\r\nCo-authored-by: Matthias Wilhelm <matthias.wilhelm@elastic.co>","sha":"1c7a823920c3d794dcb6ce30bbc1b075be40ac19"}},"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/206699","number":206699,"mergeCommit":{"message":"[Discover] [ES|QL] Prevent redundant requests when loading Discover sessions and toggling chart visibility (#206699)\n\n## Summary\r\n\r\nThis PR prevents redundant Discover requests in ES|QL mode for the\r\nfollowing scenarios:\r\n- Creating a new Discover session.\r\n- Saving the current Discover session.\r\n- Loading a saved Discover session.\r\n- Toggling the Unified Histogram chart visibility.\r\n\r\nIt does so by addressing several underlying state related issues that\r\nwere triggering the redundant requests:\r\n- Skipping the initial emission of `currentSuggestionContext` on Unified\r\nHistogram mount, which immediately triggered a second fetch.\r\n- Treating the Unified Histogram `table` prop the same as other props\r\nwhich affect Lens suggestions (data view, query, columns), and deferring\r\nupdates to it until result fetching completes to avoid unnecessary\r\nsuggestion updates.\r\n- Removing all auto-fetching behaviour from Unified Histogram and\r\ninstead relying solely on the consumer to control when fetching should\r\noccur (including the initial fetch).\r\n\r\nResolves #165192.\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/src/platform/packages/shared/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- [ ] 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 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---------\r\n\r\nCo-authored-by: Matthias Wilhelm <matthias.wilhelm@elastic.co>","sha":"1c7a823920c3d794dcb6ce30bbc1b075be40ac19"}}]}] BACKPORT--> Co-authored-by: Davis McPhee <davis.mcphee@elastic.co> |
||
|
Kibana Machine
|
343c322855
|
[8.x] [Console] Add a small action for copying variable names to clipboard (#206628) (#206897)
# Backport This will backport the following commits from `main` to `8.x`: - [[Console] Add a small action for copying variable names to clipboard (#206628)](https://github.com/elastic/kibana/pull/206628) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Ignacio Rivas","email":"rivasign@gmail.com"},"sourceCommit":{"committedDate":"2025-01-16T08:27:31Z","message":"[Console] Add a small action for copying variable names to clipboard (#206628)","sha":"983470fb852b5fc011e47b8f7a3d9f917d06a228","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Console","Team:Kibana Management","release_note:skip","v9.0.0","backport:prev-minor"],"title":"[Console] Add a small action for copying variable names to clipboard","number":206628,"url":"https://github.com/elastic/kibana/pull/206628","mergeCommit":{"message":"[Console] Add a small action for copying variable names to clipboard (#206628)","sha":"983470fb852b5fc011e47b8f7a3d9f917d06a228"}},"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/206628","number":206628,"mergeCommit":{"message":"[Console] Add a small action for copying variable names to clipboard (#206628)","sha":"983470fb852b5fc011e47b8f7a3d9f917d06a228"}}]}] BACKPORT--> Co-authored-by: Ignacio Rivas <rivasign@gmail.com> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> |
||
|
Kibana Machine
|
06063bba37
|
[8.x] [Discover] Remove redundant data fetching when hiding/showing the histogram/chart (#206389) (#207051)
# Backport This will backport the following commits from `main` to `8.x`: - [[Discover] Remove redundant data fetching when hiding/showing the histogram/chart (#206389)](https://github.com/elastic/kibana/pull/206389) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Matthias Wilhelm","email":"matthias.wilhelm@elastic.co"},"sourceCommit":{"committedDate":"2025-01-17T10:49:37Z","message":"[Discover] Remove redundant data fetching when hiding/showing the histogram/chart (#206389)\n\nSince the timerange in Discover of the main request is stable we don't need to trigger a main fetch for all data when the histogram/chart is being hidden/displayed, unless it's necessary to get the data (e.g. when the histogram/chart was hiden when a discover session was being loaded)","sha":"a04274723ef64182df96d37d134cc645e20571ee","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","Feature:Discover","performance","v9.0.0","Team:DataDiscovery","backport:prev-minor"],"title":"[Discover] Remove redundant data fetching when hiding/showing the histogram/chart","number":206389,"url":"https://github.com/elastic/kibana/pull/206389","mergeCommit":{"message":"[Discover] Remove redundant data fetching when hiding/showing the histogram/chart (#206389)\n\nSince the timerange in Discover of the main request is stable we don't need to trigger a main fetch for all data when the histogram/chart is being hidden/displayed, unless it's necessary to get the data (e.g. when the histogram/chart was hiden when a discover session was being loaded)","sha":"a04274723ef64182df96d37d134cc645e20571ee"}},"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/206389","number":206389,"mergeCommit":{"message":"[Discover] Remove redundant data fetching when hiding/showing the histogram/chart (#206389)\n\nSince the timerange in Discover of the main request is stable we don't need to trigger a main fetch for all data when the histogram/chart is being hidden/displayed, unless it's necessary to get the data (e.g. when the histogram/chart was hiden when a discover session was being loaded)","sha":"a04274723ef64182df96d37d134cc645e20571ee"}}]}] BACKPORT--> Co-authored-by: Matthias Wilhelm <matthias.wilhelm@elastic.co> |
||
|
Kibana Machine
|
1e5b858fad
|
[8.x] [Console] Copy as curl only for Kibana requests (#206631) (#206977)
# Backport This will backport the following commits from `main` to `8.x`: - [[Console] Copy as curl only for Kibana requests (#206631)](https://github.com/elastic/kibana/pull/206631) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Elena Stoeva","email":"59341489+ElenaStoeva@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-01-16T16:41:25Z","message":"[Console] Copy as curl only for Kibana requests (#206631)\n\nCloses https://github.com/elastic/kibana/issues/201781\r\n\r\n## Summary\r\n\r\nThis PR makes the context menu in Console only display \"Copy as curl\" if\r\nany of the selected requests is an internal Kibana request (i.e. starts\r\nwith the `kbn:` prefix).\r\n\r\nSample Kibana request: `GET kbn:/api/index_management/indices`\r\n\r\n\r\n\r\n\r\nhttps://github.com/user-attachments/assets/a6c5cbc3-4dc5-44db-8ebb-2cbc9b3aea2d\r\n\r\n---------\r\n\r\nCo-authored-by: Ignacio Rivas <rivasign@gmail.com>","sha":"b6f6c4cefe370301f39357a27c9674b8f67bb5e8","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Console","Team:Kibana Management","release_note:skip","v9.0.0","backport:prev-minor","v8.18.0"],"title":"[Console] Copy as curl only for Kibana requests","number":206631,"url":"https://github.com/elastic/kibana/pull/206631","mergeCommit":{"message":"[Console] Copy as curl only for Kibana requests (#206631)\n\nCloses https://github.com/elastic/kibana/issues/201781\r\n\r\n## Summary\r\n\r\nThis PR makes the context menu in Console only display \"Copy as curl\" if\r\nany of the selected requests is an internal Kibana request (i.e. starts\r\nwith the `kbn:` prefix).\r\n\r\nSample Kibana request: `GET kbn:/api/index_management/indices`\r\n\r\n\r\n\r\n\r\nhttps://github.com/user-attachments/assets/a6c5cbc3-4dc5-44db-8ebb-2cbc9b3aea2d\r\n\r\n---------\r\n\r\nCo-authored-by: Ignacio Rivas <rivasign@gmail.com>","sha":"b6f6c4cefe370301f39357a27c9674b8f67bb5e8"}},"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/206631","number":206631,"mergeCommit":{"message":"[Console] Copy as curl only for Kibana requests (#206631)\n\nCloses https://github.com/elastic/kibana/issues/201781\r\n\r\n## Summary\r\n\r\nThis PR makes the context menu in Console only display \"Copy as curl\" if\r\nany of the selected requests is an internal Kibana request (i.e. starts\r\nwith the `kbn:` prefix).\r\n\r\nSample Kibana request: `GET kbn:/api/index_management/indices`\r\n\r\n\r\n\r\n\r\nhttps://github.com/user-attachments/assets/a6c5cbc3-4dc5-44db-8ebb-2cbc9b3aea2d\r\n\r\n---------\r\n\r\nCo-authored-by: Ignacio Rivas <rivasign@gmail.com>","sha":"b6f6c4cefe370301f39357a27c9674b8f67bb5e8"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Elena Stoeva <59341489+ElenaStoeva@users.noreply.github.com> |
||
|
Stratoula Kalafateli
|
e9e01caa05
|
[ES|QL] Unskip history tests (#206949)
## Summary Closes https://github.com/elastic/kibana/issues/196866 Unskips the test now that https://github.com/elastic/kibana/pull/206418 has been merged |
||
Matthias Wilhelm
|
6b9e8344f5
|
[Discover] Update _sidebar_field_stats.ts to make upgrade tests pass (#206928)
The upgrade test was failing due the following synthx that does work in 8.x but not in 9.0: `[METADATA _index, _id]` This commit removes the brackets around the METADATA to make this work |
||
|
Nathan Reese
|
8be0a8df65
|
[8.x] [dashboard] lazy load dashboard actions (#206492) (#206870)
# Backport This will backport the following commits from `main` to `8.x`: - [[dashboard] lazy load dashboard actions (#206492)](https://github.com/elastic/kibana/pull/206492) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Nathan Reese","email":"reese.nathan@elastic.co"},"sourceCommit":{"committedDate":"2025-01-15T18:57:09Z","message":"[dashboard] lazy load dashboard actions (#206492)\n\n* move actions to `registerActionAsync`\r\n* remove global string file loaded in page load bundle\r\n* Break constants into smaller files so only constants required by page\r\nload bundle are exposed.\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":"55f3cf7a66e16d9a10dd64d04a7c6d0c94646bb6","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Presentation","release_note:skip","v9.0.0","backport:version","v8.18.0"],"title":"[dashboard] lazy load dashboard actions","number":206492,"url":"https://github.com/elastic/kibana/pull/206492","mergeCommit":{"message":"[dashboard] lazy load dashboard actions (#206492)\n\n* move actions to `registerActionAsync`\r\n* remove global string file loaded in page load bundle\r\n* Break constants into smaller files so only constants required by page\r\nload bundle are exposed.\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":"55f3cf7a66e16d9a10dd64d04a7c6d0c94646bb6"}},"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/206492","number":206492,"mergeCommit":{"message":"[dashboard] lazy load dashboard actions (#206492)\n\n* move actions to `registerActionAsync`\r\n* remove global string file loaded in page load bundle\r\n* Break constants into smaller files so only constants required by page\r\nload bundle are exposed.\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":"55f3cf7a66e16d9a10dd64d04a7c6d0c94646bb6"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/206853","number":206853,"state":"OPEN"}]}] BACKPORT--> |
||
|
Kibana Machine
|
9ae8e0ccea
|
[8.x] [Discover] Unskip and stabilize ESQL request count test (#206207) (#206388)
# Backport This will backport the following commits from `main` to `8.x`: - [[Discover] Unskip and stabilize ESQL request count test (#206207)](https://github.com/elastic/kibana/pull/206207) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Matthias Wilhelm","email":"matthias.wilhelm@elastic.co"},"sourceCommit":{"committedDate":"2025-01-13T06:59:33Z","message":"[Discover] Unskip and stabilize ESQL request count test (#206207)","sha":"b625221757760f35f5046b148a0061829efd92c6","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Discover","release_note:skip","v9.0.0","Team:DataDiscovery","backport:prev-minor"],"title":"[Discover] Unskip and stabilize ESQL request count test","number":206207,"url":"https://github.com/elastic/kibana/pull/206207","mergeCommit":{"message":"[Discover] Unskip and stabilize ESQL request count test (#206207)","sha":"b625221757760f35f5046b148a0061829efd92c6"}},"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/206207","number":206207,"mergeCommit":{"message":"[Discover] Unskip and stabilize ESQL request count test (#206207)","sha":"b625221757760f35f5046b148a0061829efd92c6"}}]}] BACKPORT--> --------- Co-authored-by: Matthias Wilhelm <matthias.wilhelm@elastic.co> Co-authored-by: Davis McPhee <davis.mcphee@elastic.co> Co-authored-by: Matthias Wilhelm <ankertal@gmail.com> |
||
|
Matthias Wilhelm
|
3231af94c2
|
[8.x] [Discover][ES]QL] Ensure the same time range is being used for documents and histogram (#204694) (#206563)
# Backport This will backport the following commits from `main` to `8.x`: - [[Discover][ES]QL] Ensure the same time range is being used for documents and histogram (#204694)](https://github.com/elastic/kibana/pull/204694) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Matthias Wilhelm","email":"matthias.wilhelm@elastic.co"},"sourceCommit":{"committedDate":"2025-01-10T16:06:45Z","message":"[Discover][ES]QL] Ensure the same time range is being used for documents and histogram (#204694)\n\nFixing the case a relative time range is set (for example \"Last 15 minutes\") and the time range goes out of sync for table and histogram requests on Discover in ES|QL mode.\n\nFixes a redundant ES|QL request for histogram data, with different timeranges, when the timerange is changed.","sha":"df495ce532e4b478984830d533dac238bfd15444","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Discover","release_note:fix","backport missing","v9.0.0","Team:DataDiscovery","backport:prev-minor","Feature:ES|QL"],"number":204694,"url":"https://github.com/elastic/kibana/pull/204694","mergeCommit":{"message":"[Discover][ES]QL] Ensure the same time range is being used for documents and histogram (#204694)\n\nFixing the case a relative time range is set (for example \"Last 15 minutes\") and the time range goes out of sync for table and histogram requests on Discover in ES|QL mode.\n\nFixes a redundant ES|QL request for histogram data, with different timeranges, when the timerange is changed.","sha":"df495ce532e4b478984830d533dac238bfd15444"}},"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/204694","number":204694,"mergeCommit":{"message":"[Discover][ES]QL] Ensure the same time range is being used for documents and histogram (#204694)\n\nFixing the case a relative time range is set (for example \"Last 15 minutes\") and the time range goes out of sync for table and histogram requests on Discover in ES|QL mode.\n\nFixes a redundant ES|QL request for histogram data, with different timeranges, when the timerange is changed.","sha":"df495ce532e4b478984830d533dac238bfd15444"}}]}] BACKPORT--> |
||
Anton Dosov
|
5cd26eef91
|
[8.x] Sustainable Kibana Architecture: Move CodeEditor related packages #205587 (#205738) (#205919)
# Backport This will backport the following commits from `main` to `8.x`: - [Sustainable Kibana Architecture: Move `CodeEditor` related packages #205587 (#205738)](https://github.com/elastic/kibana/pull/205738) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Anton Dosov","email":"anton.dosov@elastic.co"},"sourceCommit":{"committedDate":"2025-01-08T14:25:47Z","message":"Sustainable Kibana Architecture: Move `CodeEditor` related packages #205587 (#205738)\n\n## Summary\r\n\r\nThis PR aims at relocating some of the Kibana modules (plugins and\r\npackages) into a new folder structure, according to the _Sustainable\r\nKibana Architecture_ initiative.\r\n\r\n> [!IMPORTANT]\r\n> * We kindly ask you to:\r\n> * Manually fix the errors in the error section below (if there are\r\nany).\r\n> * Search for the `packages[\\/\\\\]` and `plugins[\\/\\\\]` patterns in the\r\nsource code (Babel and Eslint config files), and update them\r\nappropriately.\r\n> * Manually review\r\n`.buildkite/scripts/pipelines/pull_request/pipeline.ts` to ensure that\r\nany CI pipeline customizations continue to be correctly applied after\r\nthe changed path names\r\n> * Review all of the updated files, specially the `.ts` and `.js` files\r\nlisted in the sections below, as some of them contain relative paths\r\nthat have been updated.\r\n> * Think of potential impact of the move, including tooling and\r\nconfiguration files that can be pointing to the relocated modules. E.g.:\r\n> * customised eslint rules\r\n> * docs pointing to source code\r\n\r\n> [!NOTE]\r\n> * This PR has been auto-generated.\r\n> * Any manual contributions will be lost if the 'relocate' script is\r\nre-run.\r\n> * Try to obtain the missing reviews / approvals before applying manual\r\nfixes, and/or keep your changes in a .patch / git stash.\r\n> * Please use\r\n[#sustainable_kibana_architecture](https://elastic.slack.com/archives/C07TCKTA22E)\r\nSlack channel for feedback.\r\n\r\nAre you trying to rebase this PR to solve merge conflicts? Please follow\r\nthe steps describe\r\n[here](https://elastic.slack.com/archives/C07TCKTA22E/p1734019532879269?thread_ts=1734019339.935419&cid=C07TCKTA22E).\r\n\r\n#### 3 packages(s) are going to be relocated:\r\n\r\n| Id | Target folder |\r\n| -- | ------------- |\r\n| `@kbn/code-editor` |\r\n`src/platform/packages/shared/shared-ux/code_editor/impl` |\r\n| `@kbn/code-editor-mock` |\r\n`src/platform/packages/shared/shared-ux/code_editor/mocks` |\r\n| `@kbn/monaco` | `src/platform/packages/shared/kbn-monaco` |\r\n\r\n\r\n<details >\r\n<summary>Updated relative paths</summary>\r\n\r\n```\r\nsrc/platform/packages/shared/kbn-monaco/jest.config.js:12\r\nsrc/platform/packages/shared/kbn-monaco/tsconfig.json:2\r\nsrc/platform/packages/shared/kbn-monaco/tsconfig.type_check.json:2\r\nsrc/platform/packages/shared/shared-ux/code_editor/impl/jest.config.js:12\r\nsrc/platform/packages/shared/shared-ux/code_editor/impl/tsconfig.json:16\r\nsrc/platform/packages/shared/shared-ux/code_editor/impl/tsconfig.json:2\r\nsrc/platform/packages/shared/shared-ux/code_editor/impl/tsconfig.type_check.json:18\r\nsrc/platform/packages/shared/shared-ux/code_editor/impl/tsconfig.type_check.json:2\r\nsrc/platform/packages/shared/shared-ux/code_editor/impl/tsconfig.type_check.json:25\r\nsrc/platform/packages/shared/shared-ux/code_editor/impl/tsconfig.type_check.json:28\r\nsrc/platform/packages/shared/shared-ux/code_editor/impl/tsconfig.type_check.json:31\r\nsrc/platform/packages/shared/shared-ux/code_editor/impl/tsconfig.type_check.json:34\r\nsrc/platform/packages/shared/shared-ux/code_editor/impl/tsconfig.type_check.json:37\r\nsrc/platform/packages/shared/shared-ux/code_editor/impl/tsconfig.type_check.json:40\r\nsrc/platform/packages/shared/shared-ux/code_editor/mocks/tsconfig.json:16\r\nsrc/platform/packages/shared/shared-ux/code_editor/mocks/tsconfig.json:2\r\nsrc/platform/packages/shared/shared-ux/code_editor/mocks/tsconfig.type_check.json:18\r\nsrc/platform/packages/shared/shared-ux/code_editor/mocks/tsconfig.type_check.json:2\r\nsrc/platform/packages/shared/shared-ux/code_editor/mocks/tsconfig.type_check.json:25\r\n```\r\n\r\n</details>","sha":"3b2ab7b4134c05c00a74a70d7905f6b06e1364c1","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:SharedUX","backport:prev-minor","plugin groups"],"number":205738,"url":"https://github.com/elastic/kibana/pull/205738","mergeCommit":{"message":"Sustainable Kibana Architecture: Move `CodeEditor` related packages #205587 (#205738)\n\n## Summary\r\n\r\nThis PR aims at relocating some of the Kibana modules (plugins and\r\npackages) into a new folder structure, according to the _Sustainable\r\nKibana Architecture_ initiative.\r\n\r\n> [!IMPORTANT]\r\n> * We kindly ask you to:\r\n> * Manually fix the errors in the error section below (if there are\r\nany).\r\n> * Search for the `packages[\\/\\\\]` and `plugins[\\/\\\\]` patterns in the\r\nsource code (Babel and Eslint config files), and update them\r\nappropriately.\r\n> * Manually review\r\n`.buildkite/scripts/pipelines/pull_request/pipeline.ts` to ensure that\r\nany CI pipeline customizations continue to be correctly applied after\r\nthe changed path names\r\n> * Review all of the updated files, specially the `.ts` and `.js` files\r\nlisted in the sections below, as some of them contain relative paths\r\nthat have been updated.\r\n> * Think of potential impact of the move, including tooling and\r\nconfiguration files that can be pointing to the relocated modules. E.g.:\r\n> * customised eslint rules\r\n> * docs pointing to source code\r\n\r\n> [!NOTE]\r\n> * This PR has been auto-generated.\r\n> * Any manual contributions will be lost if the 'relocate' script is\r\nre-run.\r\n> * Try to obtain the missing reviews / approvals before applying manual\r\nfixes, and/or keep your changes in a .patch / git stash.\r\n> * Please use\r\n[#sustainable_kibana_architecture](https://elastic.slack.com/archives/C07TCKTA22E)\r\nSlack channel for feedback.\r\n\r\nAre you trying to rebase this PR to solve merge conflicts? Please follow\r\nthe steps describe\r\n[here](https://elastic.slack.com/archives/C07TCKTA22E/p1734019532879269?thread_ts=1734019339.935419&cid=C07TCKTA22E).\r\n\r\n#### 3 packages(s) are going to be relocated:\r\n\r\n| Id | Target folder |\r\n| -- | ------------- |\r\n| `@kbn/code-editor` |\r\n`src/platform/packages/shared/shared-ux/code_editor/impl` |\r\n| `@kbn/code-editor-mock` |\r\n`src/platform/packages/shared/shared-ux/code_editor/mocks` |\r\n| `@kbn/monaco` | `src/platform/packages/shared/kbn-monaco` |\r\n\r\n\r\n<details >\r\n<summary>Updated relative paths</summary>\r\n\r\n```\r\nsrc/platform/packages/shared/kbn-monaco/jest.config.js:12\r\nsrc/platform/packages/shared/kbn-monaco/tsconfig.json:2\r\nsrc/platform/packages/shared/kbn-monaco/tsconfig.type_check.json:2\r\nsrc/platform/packages/shared/shared-ux/code_editor/impl/jest.config.js:12\r\nsrc/platform/packages/shared/shared-ux/code_editor/impl/tsconfig.json:16\r\nsrc/platform/packages/shared/shared-ux/code_editor/impl/tsconfig.json:2\r\nsrc/platform/packages/shared/shared-ux/code_editor/impl/tsconfig.type_check.json:18\r\nsrc/platform/packages/shared/shared-ux/code_editor/impl/tsconfig.type_check.json:2\r\nsrc/platform/packages/shared/shared-ux/code_editor/impl/tsconfig.type_check.json:25\r\nsrc/platform/packages/shared/shared-ux/code_editor/impl/tsconfig.type_check.json:28\r\nsrc/platform/packages/shared/shared-ux/code_editor/impl/tsconfig.type_check.json:31\r\nsrc/platform/packages/shared/shared-ux/code_editor/impl/tsconfig.type_check.json:34\r\nsrc/platform/packages/shared/shared-ux/code_editor/impl/tsconfig.type_check.json:37\r\nsrc/platform/packages/shared/shared-ux/code_editor/impl/tsconfig.type_check.json:40\r\nsrc/platform/packages/shared/shared-ux/code_editor/mocks/tsconfig.json:16\r\nsrc/platform/packages/shared/shared-ux/code_editor/mocks/tsconfig.json:2\r\nsrc/platform/packages/shared/shared-ux/code_editor/mocks/tsconfig.type_check.json:18\r\nsrc/platform/packages/shared/shared-ux/code_editor/mocks/tsconfig.type_check.json:2\r\nsrc/platform/packages/shared/shared-ux/code_editor/mocks/tsconfig.type_check.json:25\r\n```\r\n\r\n</details>","sha":"3b2ab7b4134c05c00a74a70d7905f6b06e1364c1"}},"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/205738","number":205738,"mergeCommit":{"message":"Sustainable Kibana Architecture: Move `CodeEditor` related packages #205587 (#205738)\n\n## Summary\r\n\r\nThis PR aims at relocating some of the Kibana modules (plugins and\r\npackages) into a new folder structure, according to the _Sustainable\r\nKibana Architecture_ initiative.\r\n\r\n> [!IMPORTANT]\r\n> * We kindly ask you to:\r\n> * Manually fix the errors in the error section below (if there are\r\nany).\r\n> * Search for the `packages[\\/\\\\]` and `plugins[\\/\\\\]` patterns in the\r\nsource code (Babel and Eslint config files), and update them\r\nappropriately.\r\n> * Manually review\r\n`.buildkite/scripts/pipelines/pull_request/pipeline.ts` to ensure that\r\nany CI pipeline customizations continue to be correctly applied after\r\nthe changed path names\r\n> * Review all of the updated files, specially the `.ts` and `.js` files\r\nlisted in the sections below, as some of them contain relative paths\r\nthat have been updated.\r\n> * Think of potential impact of the move, including tooling and\r\nconfiguration files that can be pointing to the relocated modules. E.g.:\r\n> * customised eslint rules\r\n> * docs pointing to source code\r\n\r\n> [!NOTE]\r\n> * This PR has been auto-generated.\r\n> * Any manual contributions will be lost if the 'relocate' script is\r\nre-run.\r\n> * Try to obtain the missing reviews / approvals before applying manual\r\nfixes, and/or keep your changes in a .patch / git stash.\r\n> * Please use\r\n[#sustainable_kibana_architecture](https://elastic.slack.com/archives/C07TCKTA22E)\r\nSlack channel for feedback.\r\n\r\nAre you trying to rebase this PR to solve merge conflicts? Please follow\r\nthe steps describe\r\n[here](https://elastic.slack.com/archives/C07TCKTA22E/p1734019532879269?thread_ts=1734019339.935419&cid=C07TCKTA22E).\r\n\r\n#### 3 packages(s) are going to be relocated:\r\n\r\n| Id | Target folder |\r\n| -- | ------------- |\r\n| `@kbn/code-editor` |\r\n`src/platform/packages/shared/shared-ux/code_editor/impl` |\r\n| `@kbn/code-editor-mock` |\r\n`src/platform/packages/shared/shared-ux/code_editor/mocks` |\r\n| `@kbn/monaco` | `src/platform/packages/shared/kbn-monaco` |\r\n\r\n\r\n<details >\r\n<summary>Updated relative paths</summary>\r\n\r\n```\r\nsrc/platform/packages/shared/kbn-monaco/jest.config.js:12\r\nsrc/platform/packages/shared/kbn-monaco/tsconfig.json:2\r\nsrc/platform/packages/shared/kbn-monaco/tsconfig.type_check.json:2\r\nsrc/platform/packages/shared/shared-ux/code_editor/impl/jest.config.js:12\r\nsrc/platform/packages/shared/shared-ux/code_editor/impl/tsconfig.json:16\r\nsrc/platform/packages/shared/shared-ux/code_editor/impl/tsconfig.json:2\r\nsrc/platform/packages/shared/shared-ux/code_editor/impl/tsconfig.type_check.json:18\r\nsrc/platform/packages/shared/shared-ux/code_editor/impl/tsconfig.type_check.json:2\r\nsrc/platform/packages/shared/shared-ux/code_editor/impl/tsconfig.type_check.json:25\r\nsrc/platform/packages/shared/shared-ux/code_editor/impl/tsconfig.type_check.json:28\r\nsrc/platform/packages/shared/shared-ux/code_editor/impl/tsconfig.type_check.json:31\r\nsrc/platform/packages/shared/shared-ux/code_editor/impl/tsconfig.type_check.json:34\r\nsrc/platform/packages/shared/shared-ux/code_editor/impl/tsconfig.type_check.json:37\r\nsrc/platform/packages/shared/shared-ux/code_editor/impl/tsconfig.type_check.json:40\r\nsrc/platform/packages/shared/shared-ux/code_editor/mocks/tsconfig.json:16\r\nsrc/platform/packages/shared/shared-ux/code_editor/mocks/tsconfig.json:2\r\nsrc/platform/packages/shared/shared-ux/code_editor/mocks/tsconfig.type_check.json:18\r\nsrc/platform/packages/shared/shared-ux/code_editor/mocks/tsconfig.type_check.json:2\r\nsrc/platform/packages/shared/shared-ux/code_editor/mocks/tsconfig.type_check.json:25\r\n```\r\n\r\n</details>","sha":"3b2ab7b4134c05c00a74a70d7905f6b06e1364c1"}}]}] BACKPORT--> --------- Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> |
||
|
Kibana Machine
|
ffb432c30e
|
[8.x] [Dashboard] Add functional test for panel listing types (#205808) (#206060)
# Backport This will backport the following commits from `main` to `8.x`: - [[Dashboard] Add functional test for panel listing types (#205808)](https://github.com/elastic/kibana/pull/205808) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Nick Peihl","email":"nick.peihl@elastic.co"},"sourceCommit":{"committedDate":"2025-01-09T13:37:29Z","message":"[Dashboard] Add functional test for panel listing types (#205808)\n\nFixes #192663\r\n\r\n## Summary\r\n\r\nAdd functional tests that verify the number of panel types registered in\r\nthe dashboards Add panel flyout. Any changes to the number of registered\r\npanel types will trigger a review from the\r\n`@elastic/kibana-presentation` team.\r\n\r\nThis PR also adds an additional test for panel types registered with an\r\nadvanced license.","sha":"ce072268aa3b2a82fa2900dbb0cfbc9902f57fa4","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Presentation","release_note:skip","v9.0.0","backport:prev-minor"],"title":"[Dashboard] Add functional test for panel listing types","number":205808,"url":"https://github.com/elastic/kibana/pull/205808","mergeCommit":{"message":"[Dashboard] Add functional test for panel listing types (#205808)\n\nFixes #192663\r\n\r\n## Summary\r\n\r\nAdd functional tests that verify the number of panel types registered in\r\nthe dashboards Add panel flyout. Any changes to the number of registered\r\npanel types will trigger a review from the\r\n`@elastic/kibana-presentation` team.\r\n\r\nThis PR also adds an additional test for panel types registered with an\r\nadvanced license.","sha":"ce072268aa3b2a82fa2900dbb0cfbc9902f57fa4"}},"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/205808","number":205808,"mergeCommit":{"message":"[Dashboard] Add functional test for panel listing types (#205808)\n\nFixes #192663\r\n\r\n## Summary\r\n\r\nAdd functional tests that verify the number of panel types registered in\r\nthe dashboards Add panel flyout. Any changes to the number of registered\r\npanel types will trigger a review from the\r\n`@elastic/kibana-presentation` team.\r\n\r\nThis PR also adds an additional test for panel types registered with an\r\nadvanced license.","sha":"ce072268aa3b2a82fa2900dbb0cfbc9902f57fa4"}}]}] BACKPORT--> Co-authored-by: Nick Peihl <nick.peihl@elastic.co> |
||
|
Davis McPhee
|
886301a33a
|
[8.x] [Discover] Fix issue where KEEP columns are not applied after Elasticsearch error (#205833) (#205968)
# Backport This will backport the following commits from `main` to `8.x`: - [[Discover] Fix issue where `KEEP` columns are not applied after Elasticsearch error (#205833)](https://github.com/elastic/kibana/pull/205833) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Davis McPhee","email":"davis.mcphee@elastic.co"},"sourceCommit":{"committedDate":"2025-01-08T18:20:24Z","message":"[Discover] Fix issue where `KEEP` columns are not applied after Elasticsearch error (#205833)\n\n## Summary\r\n\r\nThis PR fixes an issue where columns are not applied correctly when\r\nusing the ES|QL `KEEP` command after an Elasticsearch error has\r\noccurred.\r\n\r\nFixes #205353.\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/src/platform/packages/shared/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- [ ] 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 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)","sha":"8eb326d5961ef377f0a05c98c281eb5b97bd19d3","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:DataDiscovery","backport:version","v8.17.0","v8.18.0"],"number":205833,"url":"https://github.com/elastic/kibana/pull/205833","mergeCommit":{"message":"[Discover] Fix issue where `KEEP` columns are not applied after Elasticsearch error (#205833)\n\n## Summary\r\n\r\nThis PR fixes an issue where columns are not applied correctly when\r\nusing the ES|QL `KEEP` command after an Elasticsearch error has\r\noccurred.\r\n\r\nFixes #205353.\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/src/platform/packages/shared/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- [ ] 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 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)","sha":"8eb326d5961ef377f0a05c98c281eb5b97bd19d3"}},"sourceBranch":"main","suggestedTargetBranches":["8.17","8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/205833","number":205833,"mergeCommit":{"message":"[Discover] Fix issue where `KEEP` columns are not applied after Elasticsearch error (#205833)\n\n## Summary\r\n\r\nThis PR fixes an issue where columns are not applied correctly when\r\nusing the ES|QL `KEEP` command after an Elasticsearch error has\r\noccurred.\r\n\r\nFixes #205353.\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/src/platform/packages/shared/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- [ ] 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 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)","sha":"8eb326d5961ef377f0a05c98c281eb5b97bd19d3"}},{"branch":"8.17","label":"v8.17.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.18.0","labelRegex":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
1e6f754b35
|
[8.x] [Discover] Unskip functional discover request counts test and skip ES|QL part (#205690) (#205993)
# Backport This will backport the following commits from `main` to `8.x`: - [[Discover] Unskip functional discover request counts test and skip ES|QL part (#205690)](https://github.com/elastic/kibana/pull/205690) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Matthias Wilhelm","email":"matthias.wilhelm@elastic.co"},"sourceCommit":{"committedDate":"2025-01-09T05:35:40Z","message":"[Discover] Unskip functional discover request counts test and skip ES|QL part (#205690)\n\nUnskipping the main test, and unskipping the `ES|QL` part due to flakiness","sha":"cbcb24e036dd598cc4109fdb83ebdb5bcaba2d4c","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:DataDiscovery","backport:prev-minor"],"title":"[Discover] Unskip functional discover request counts test and skip ES|QL part","number":205690,"url":"https://github.com/elastic/kibana/pull/205690","mergeCommit":{"message":"[Discover] Unskip functional discover request counts test and skip ES|QL part (#205690)\n\nUnskipping the main test, and unskipping the `ES|QL` part due to flakiness","sha":"cbcb24e036dd598cc4109fdb83ebdb5bcaba2d4c"}},"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/205690","number":205690,"mergeCommit":{"message":"[Discover] Unskip functional discover request counts test and skip ES|QL part (#205690)\n\nUnskipping the main test, and unskipping the `ES|QL` part due to flakiness","sha":"cbcb24e036dd598cc4109fdb83ebdb5bcaba2d4c"}}]}] BACKPORT--> Co-authored-by: Matthias Wilhelm <matthias.wilhelm@elastic.co> |
||
|
Davis McPhee
|
8b42d98561
|
[8.x] [Data Views] Backport Upgrade Assistant changes to warn about scripted field creation removal in 9.0 (#205561)
## Summary This PR backports the Upgrade Assistant changes from #202250 to warn about the upcoming scripted field creation removal in 9.0. It also includes some of the documentation changes and cleanup in the Data Views Management UI. ### Checklist - [x] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md) - [x] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [x] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) |
||
|
Anton Dosov
|
d58b812ece
|
[8.x] Sustainable Kibana Architecture: Move plugins owned by @elastic/appex-sharedux (#204959) (#205508)
# Backport This will backport the following commits from `main` to `8.x`: - [Sustainable Kibana Architecture: Move plugins owned by `@elastic/appex-sharedux` (#204959)](https://github.com/elastic/kibana/pull/204959) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Anton Dosov","email":"anton.dosov@elastic.co"},"sourceCommit":{"committedDate":"2025-01-03T11:38:57Z","message":"Sustainable Kibana Architecture: Move plugins owned by `@elastic/appex-sharedux` (#204959)\n\n## Summary\r\n\r\nPart of https://github.com/elastic/kibana/pull/203163\r\n\r\nRelocating only shared-ux-owned plugins for now","sha":"9215df9200edac72f2225760043ac45c9e82cdf0","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:SharedUX","backport:prev-minor","plugin groups"],"number":204959,"url":"https://github.com/elastic/kibana/pull/204959","mergeCommit":{"message":"Sustainable Kibana Architecture: Move plugins owned by `@elastic/appex-sharedux` (#204959)\n\n## Summary\r\n\r\nPart of https://github.com/elastic/kibana/pull/203163\r\n\r\nRelocating only shared-ux-owned plugins for now","sha":"9215df9200edac72f2225760043ac45c9e82cdf0"}},"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/204959","number":204959,"mergeCommit":{"message":"Sustainable Kibana Architecture: Move plugins owned by `@elastic/appex-sharedux` (#204959)\n\n## Summary\r\n\r\nPart of https://github.com/elastic/kibana/pull/203163\r\n\r\nRelocating only shared-ux-owned plugins for now","sha":"9215df9200edac72f2225760043ac45c9e82cdf0"}}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Timothy Sullivan <tsullivan@elastic.co> |
||
Michael Dokolin
|
861c2de3e5
|
[8.x] Sustainable Kibana Architecture: Move modules owned by @elastic/kibana-core (#201653) (#205563)
# Backport This will backport the following commits from `main` to `8.x`: - [Sustainable Kibana Architecture: Move modules owned by `@elastic/kibana-core` (#201653)](https://github.com/elastic/kibana/pull/201653) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Gerard Soldevila","email":"gerard.soldevila@elastic.co"},"sourceCommit":{"committedDate":"2025-01-04T18:47:24Z","message":"Sustainable Kibana Architecture: Move modules owned by `@elastic/kibana-core` (#201653)\n\n## Summary\n\nStart relocating Kibana modules (packages and plugins) to the new folder\nstructure, according to the _Kibana Sustainable Architecture_\ninitiative.\n#### 16 plugin(s) are going to be relocated:\n\n| Id | Target folder |\n| -- | ------------- |\n| `@kbn/cloud-chat-plugin` |\n`x-pack/platform/plugins/private/cloud_integrations/cloud_chat` |\n| `@kbn/cloud-experiments-plugin` |\n`x-pack/platform/plugins/shared/cloud_integrations/cloud_experiments` |\n| `@kbn/cloud-full-story-plugin` |\n`x-pack/platform/plugins/private/cloud_integrations/cloud_full_story` |\n| `@kbn/cloud-links-plugin` |\n`x-pack/platform/plugins/private/cloud_integrations/cloud_links` |\n| `@kbn/cloud-plugin` | `x-pack/platform/plugins/shared/cloud` |\n| `@kbn/features-plugin` | `x-pack/platform/plugins/shared/features` |\n| `@kbn/ftr-apis-plugin` | `src/platform/plugins/private/ftr_apis` |\n| `@kbn/kibana-usage-collection-plugin` |\n`src/platform/plugins/private/kibana_usage_collection` |\n| `@kbn/licensing-plugin` | `x-pack/platform/plugins/shared/licensing` |\n| `@kbn/newsfeed-plugin` | `src/platform/plugins/shared/newsfeed` |\n| `@kbn/saved-objects-management-plugin` |\n`src/platform/plugins/shared/saved_objects_management` |\n| `@kbn/telemetry-collection-manager-plugin` |\n`src/platform/plugins/shared/telemetry_collection_manager` |\n| `@kbn/telemetry-collection-xpack-plugin` |\n`x-pack/platform/plugins/private/telemetry_collection_xpack` |\n| `@kbn/telemetry-management-section-plugin` |\n`src/platform/plugins/shared/telemetry_management_section` |\n| `@kbn/telemetry-plugin` | `src/platform/plugins/shared/telemetry` |\n| `@kbn/usage-collection-plugin` |\n`src/platform/plugins/shared/usage_collection` |\n\n#### 22 package(s) are going to be relocated:\n\n| Id | Target folder |\n| -- | ------------- |\n| `@kbn/analytics` | `src/platform/packages/shared/kbn-analytics` |\n| `@kbn/analytics-collection-utils` |\n`src/platform/packages/private/analytics/utils/analytics_collection_utils`\n|\n| `@kbn/apm-config-loader` |\n`src/platform/packages/private/kbn-apm-config-loader` |\n| `@kbn/cloud` | `src/platform/packages/shared/cloud` |\n| `@kbn/config` | `src/platform/packages/shared/kbn-config` |\n| `@kbn/config-mocks` | `src/platform/packages/private/kbn-config-mocks`\n|\n| `@kbn/config-schema` |\n`src/platform/packages/shared/kbn-config-schema` |\n| `@kbn/crypto-browser` |\n`src/platform/packages/shared/kbn-crypto-browser` |\n| `@kbn/ebt-tools` | `src/platform/packages/shared/kbn-ebt-tools` |\n| `@kbn/es-errors` | `src/platform/packages/shared/kbn-es-errors` |\n| `@kbn/es-types` | `src/platform/packages/shared/kbn-es-types` |\n| `@kbn/hapi-mocks` | `src/platform/packages/private/kbn-hapi-mocks` |\n| `@kbn/health-gateway-server` |\n`src/platform/packages/private/kbn-health-gateway-server` |\n| `@kbn/i18n` | `src/platform/packages/shared/kbn-i18n` |\n| `@kbn/i18n-react` | `src/platform/packages/shared/kbn-i18n-react` |\n| `@kbn/logging` | `src/platform/packages/shared/kbn-logging` |\n| `@kbn/logging-mocks` |\n`src/platform/packages/shared/kbn-logging-mocks` |\n| `@kbn/router-to-openapispec` |\n`src/platform/packages/shared/kbn-router-to-openapispec` |\n| `@kbn/server-http-tools` |\n`src/platform/packages/shared/kbn-server-http-tools` |\n| `@kbn/std` | `src/platform/packages/shared/kbn-std` |\n| `@kbn/utility-types` |\n`src/platform/packages/shared/kbn-utility-types` |\n| `@kbn/zod` | `src/platform/packages/shared/kbn-zod` |\n\n---------\n\nCo-authored-by: Alejandro Fernández Haro <alejandro.haro@elastic.co>\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"6049493e4a2372ea22986b231ad2bd59584fe9b8","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","v9.0.0","backport:prev-minor","ci:project-deploy-observability","plugin groups"],"number":201653,"url":"https://github.com/elastic/kibana/pull/201653","mergeCommit":{"message":"Sustainable Kibana Architecture: Move modules owned by `@elastic/kibana-core` (#201653)\n\n## Summary\n\nStart relocating Kibana modules (packages and plugins) to the new folder\nstructure, according to the _Kibana Sustainable Architecture_\ninitiative.\n#### 16 plugin(s) are going to be relocated:\n\n| Id | Target folder |\n| -- | ------------- |\n| `@kbn/cloud-chat-plugin` |\n`x-pack/platform/plugins/private/cloud_integrations/cloud_chat` |\n| `@kbn/cloud-experiments-plugin` |\n`x-pack/platform/plugins/shared/cloud_integrations/cloud_experiments` |\n| `@kbn/cloud-full-story-plugin` |\n`x-pack/platform/plugins/private/cloud_integrations/cloud_full_story` |\n| `@kbn/cloud-links-plugin` |\n`x-pack/platform/plugins/private/cloud_integrations/cloud_links` |\n| `@kbn/cloud-plugin` | `x-pack/platform/plugins/shared/cloud` |\n| `@kbn/features-plugin` | `x-pack/platform/plugins/shared/features` |\n| `@kbn/ftr-apis-plugin` | `src/platform/plugins/private/ftr_apis` |\n| `@kbn/kibana-usage-collection-plugin` |\n`src/platform/plugins/private/kibana_usage_collection` |\n| `@kbn/licensing-plugin` | `x-pack/platform/plugins/shared/licensing` |\n| `@kbn/newsfeed-plugin` | `src/platform/plugins/shared/newsfeed` |\n| `@kbn/saved-objects-management-plugin` |\n`src/platform/plugins/shared/saved_objects_management` |\n| `@kbn/telemetry-collection-manager-plugin` |\n`src/platform/plugins/shared/telemetry_collection_manager` |\n| `@kbn/telemetry-collection-xpack-plugin` |\n`x-pack/platform/plugins/private/telemetry_collection_xpack` |\n| `@kbn/telemetry-management-section-plugin` |\n`src/platform/plugins/shared/telemetry_management_section` |\n| `@kbn/telemetry-plugin` | `src/platform/plugins/shared/telemetry` |\n| `@kbn/usage-collection-plugin` |\n`src/platform/plugins/shared/usage_collection` |\n\n#### 22 package(s) are going to be relocated:\n\n| Id | Target folder |\n| -- | ------------- |\n| `@kbn/analytics` | `src/platform/packages/shared/kbn-analytics` |\n| `@kbn/analytics-collection-utils` |\n`src/platform/packages/private/analytics/utils/analytics_collection_utils`\n|\n| `@kbn/apm-config-loader` |\n`src/platform/packages/private/kbn-apm-config-loader` |\n| `@kbn/cloud` | `src/platform/packages/shared/cloud` |\n| `@kbn/config` | `src/platform/packages/shared/kbn-config` |\n| `@kbn/config-mocks` | `src/platform/packages/private/kbn-config-mocks`\n|\n| `@kbn/config-schema` |\n`src/platform/packages/shared/kbn-config-schema` |\n| `@kbn/crypto-browser` |\n`src/platform/packages/shared/kbn-crypto-browser` |\n| `@kbn/ebt-tools` | `src/platform/packages/shared/kbn-ebt-tools` |\n| `@kbn/es-errors` | `src/platform/packages/shared/kbn-es-errors` |\n| `@kbn/es-types` | `src/platform/packages/shared/kbn-es-types` |\n| `@kbn/hapi-mocks` | `src/platform/packages/private/kbn-hapi-mocks` |\n| `@kbn/health-gateway-server` |\n`src/platform/packages/private/kbn-health-gateway-server` |\n| `@kbn/i18n` | `src/platform/packages/shared/kbn-i18n` |\n| `@kbn/i18n-react` | `src/platform/packages/shared/kbn-i18n-react` |\n| `@kbn/logging` | `src/platform/packages/shared/kbn-logging` |\n| `@kbn/logging-mocks` |\n`src/platform/packages/shared/kbn-logging-mocks` |\n| `@kbn/router-to-openapispec` |\n`src/platform/packages/shared/kbn-router-to-openapispec` |\n| `@kbn/server-http-tools` |\n`src/platform/packages/shared/kbn-server-http-tools` |\n| `@kbn/std` | `src/platform/packages/shared/kbn-std` |\n| `@kbn/utility-types` |\n`src/platform/packages/shared/kbn-utility-types` |\n| `@kbn/zod` | `src/platform/packages/shared/kbn-zod` |\n\n---------\n\nCo-authored-by: Alejandro Fernández Haro <alejandro.haro@elastic.co>\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"6049493e4a2372ea22986b231ad2bd59584fe9b8"}},"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/201653","number":201653,"mergeCommit":{"message":"Sustainable Kibana Architecture: Move modules owned by `@elastic/kibana-core` (#201653)\n\n## Summary\n\nStart relocating Kibana modules (packages and plugins) to the new folder\nstructure, according to the _Kibana Sustainable Architecture_\ninitiative.\n#### 16 plugin(s) are going to be relocated:\n\n| Id | Target folder |\n| -- | ------------- |\n| `@kbn/cloud-chat-plugin` |\n`x-pack/platform/plugins/private/cloud_integrations/cloud_chat` |\n| `@kbn/cloud-experiments-plugin` |\n`x-pack/platform/plugins/shared/cloud_integrations/cloud_experiments` |\n| `@kbn/cloud-full-story-plugin` |\n`x-pack/platform/plugins/private/cloud_integrations/cloud_full_story` |\n| `@kbn/cloud-links-plugin` |\n`x-pack/platform/plugins/private/cloud_integrations/cloud_links` |\n| `@kbn/cloud-plugin` | `x-pack/platform/plugins/shared/cloud` |\n| `@kbn/features-plugin` | `x-pack/platform/plugins/shared/features` |\n| `@kbn/ftr-apis-plugin` | `src/platform/plugins/private/ftr_apis` |\n| `@kbn/kibana-usage-collection-plugin` |\n`src/platform/plugins/private/kibana_usage_collection` |\n| `@kbn/licensing-plugin` | `x-pack/platform/plugins/shared/licensing` |\n| `@kbn/newsfeed-plugin` | `src/platform/plugins/shared/newsfeed` |\n| `@kbn/saved-objects-management-plugin` |\n`src/platform/plugins/shared/saved_objects_management` |\n| `@kbn/telemetry-collection-manager-plugin` |\n`src/platform/plugins/shared/telemetry_collection_manager` |\n| `@kbn/telemetry-collection-xpack-plugin` |\n`x-pack/platform/plugins/private/telemetry_collection_xpack` |\n| `@kbn/telemetry-management-section-plugin` |\n`src/platform/plugins/shared/telemetry_management_section` |\n| `@kbn/telemetry-plugin` | `src/platform/plugins/shared/telemetry` |\n| `@kbn/usage-collection-plugin` |\n`src/platform/plugins/shared/usage_collection` |\n\n#### 22 package(s) are going to be relocated:\n\n| Id | Target folder |\n| -- | ------------- |\n| `@kbn/analytics` | `src/platform/packages/shared/kbn-analytics` |\n| `@kbn/analytics-collection-utils` |\n`src/platform/packages/private/analytics/utils/analytics_collection_utils`\n|\n| `@kbn/apm-config-loader` |\n`src/platform/packages/private/kbn-apm-config-loader` |\n| `@kbn/cloud` | `src/platform/packages/shared/cloud` |\n| `@kbn/config` | `src/platform/packages/shared/kbn-config` |\n| `@kbn/config-mocks` | `src/platform/packages/private/kbn-config-mocks`\n|\n| `@kbn/config-schema` |\n`src/platform/packages/shared/kbn-config-schema` |\n| `@kbn/crypto-browser` |\n`src/platform/packages/shared/kbn-crypto-browser` |\n| `@kbn/ebt-tools` | `src/platform/packages/shared/kbn-ebt-tools` |\n| `@kbn/es-errors` | `src/platform/packages/shared/kbn-es-errors` |\n| `@kbn/es-types` | `src/platform/packages/shared/kbn-es-types` |\n| `@kbn/hapi-mocks` | `src/platform/packages/private/kbn-hapi-mocks` |\n| `@kbn/health-gateway-server` |\n`src/platform/packages/private/kbn-health-gateway-server` |\n| `@kbn/i18n` | `src/platform/packages/shared/kbn-i18n` |\n| `@kbn/i18n-react` | `src/platform/packages/shared/kbn-i18n-react` |\n| `@kbn/logging` | `src/platform/packages/shared/kbn-logging` |\n| `@kbn/logging-mocks` |\n`src/platform/packages/shared/kbn-logging-mocks` |\n| `@kbn/router-to-openapispec` |\n`src/platform/packages/shared/kbn-router-to-openapispec` |\n| `@kbn/server-http-tools` |\n`src/platform/packages/shared/kbn-server-http-tools` |\n| `@kbn/std` | `src/platform/packages/shared/kbn-std` |\n| `@kbn/utility-types` |\n`src/platform/packages/shared/kbn-utility-types` |\n| `@kbn/zod` | `src/platform/packages/shared/kbn-zod` |\n\n---------\n\nCo-authored-by: Alejandro Fernández Haro <alejandro.haro@elastic.co>\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"6049493e4a2372ea22986b231ad2bd59584fe9b8"}}]}] BACKPORT--> --------- Co-authored-by: Gerard Soldevila <gerard.soldevila@elastic.co> |
||
|
Kibana Machine
|
2c7c1c7c6d | skip failing test suite (#205344) | ||
|
Kibana Machine
|
c028120c67
|
[8.x] fix(tests, interactive setup): switch interactive setup tests config to non-deprecated `secure_password` setting (#205208) (#205214)
# Backport This will backport the following commits from `main` to `8.x`: - [fix(tests, interactive setup): switch interactive setup tests config to non-deprecated `secure_password` setting (#205208)](https://github.com/elastic/kibana/pull/205208) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Aleh Zasypkin","email":"aleh.zasypkin@elastic.co"},"sourceCommit":{"committedDate":"2024-12-27T16:51:43Z","message":"fix(tests, interactive setup): switch interactive setup tests config to non-deprecated `secure_password` setting (#205208)\n\n## Summary\n\nSwitch interactive setup tests config to non-deprecated\n`secure_password` setting as was flagged in\nhttps://github.com/elastic/kibana-team/issues/1173#issuecomment-2545077579","sha":"5e8b61fb062e12dba3f17e51512b54776959a379","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["test","Team:Security","release_note:skip","v9.0.0","backport:prev-minor"],"title":"fix(tests, interactive setup): switch interactive setup tests config to non-deprecated `secure_password` setting","number":205208,"url":"https://github.com/elastic/kibana/pull/205208","mergeCommit":{"message":"fix(tests, interactive setup): switch interactive setup tests config to non-deprecated `secure_password` setting (#205208)\n\n## Summary\n\nSwitch interactive setup tests config to non-deprecated\n`secure_password` setting as was flagged in\nhttps://github.com/elastic/kibana-team/issues/1173#issuecomment-2545077579","sha":"5e8b61fb062e12dba3f17e51512b54776959a379"}},"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/205208","number":205208,"mergeCommit":{"message":"fix(tests, interactive setup): switch interactive setup tests config to non-deprecated `secure_password` setting (#205208)\n\n## Summary\n\nSwitch interactive setup tests config to non-deprecated\n`secure_password` setting as was flagged in\nhttps://github.com/elastic/kibana-team/issues/1173#issuecomment-2545077579","sha":"5e8b61fb062e12dba3f17e51512b54776959a379"}}]}] BACKPORT--> Co-authored-by: Aleh Zasypkin <aleh.zasypkin@elastic.co> |
||
|
Kibana Machine
|
4f85910054
|
[8.x] Fix resolve index API to not throw 500 when encountering `no_such_remote_cluster_exception` (#204802) (#205016)
# Backport This will backport the following commits from `main` to `8.x`: - [Fix resolve index API to not throw 500 when encountering `no_such_remote_cluster_exception` (#204802)](https://github.com/elastic/kibana/pull/204802) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Lukas Olson","email":"lukas@elastic.co"},"sourceCommit":{"committedDate":"2024-12-19T21:55:29Z","message":"Fix resolve index API to not throw 500 when encountering `no_such_remote_cluster_exception` (#204802)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/197747.\r\n\r\nUpdates the `/internal/index-pattern-management/resolve_index/{query}`\r\nroute to properly handle `no_such_remote_cluster_exception` and return\r\n`404` rather than `500` server error.\r\n\r\nAdds unit tests for the route handler.\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] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n---------\r\n\r\nCo-authored-by: Julia Rechkunova <julia.rechkunova@gmail.com>","sha":"0952f6e0f52771b3503c9ddd2afd793d8ed86709","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Data Views","release_note:skip","v9.0.0","Team:DataDiscovery","backport:prev-minor"],"title":"Fix resolve index API to not throw 500 when encountering `no_such_remote_cluster_exception`","number":204802,"url":"https://github.com/elastic/kibana/pull/204802","mergeCommit":{"message":"Fix resolve index API to not throw 500 when encountering `no_such_remote_cluster_exception` (#204802)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/197747.\r\n\r\nUpdates the `/internal/index-pattern-management/resolve_index/{query}`\r\nroute to properly handle `no_such_remote_cluster_exception` and return\r\n`404` rather than `500` server error.\r\n\r\nAdds unit tests for the route handler.\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] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n---------\r\n\r\nCo-authored-by: Julia Rechkunova <julia.rechkunova@gmail.com>","sha":"0952f6e0f52771b3503c9ddd2afd793d8ed86709"}},"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/204802","number":204802,"mergeCommit":{"message":"Fix resolve index API to not throw 500 when encountering `no_such_remote_cluster_exception` (#204802)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/197747.\r\n\r\nUpdates the `/internal/index-pattern-management/resolve_index/{query}`\r\nroute to properly handle `no_such_remote_cluster_exception` and return\r\n`404` rather than `500` server error.\r\n\r\nAdds unit tests for the route handler.\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] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n---------\r\n\r\nCo-authored-by: Julia Rechkunova <julia.rechkunova@gmail.com>","sha":"0952f6e0f52771b3503c9ddd2afd793d8ed86709"}}]}] BACKPORT--> Co-authored-by: Lukas Olson <lukas@elastic.co> |
||
|
Kibana Machine
|
55a09ed370
|
[8.x] [Discover] Reintroduce ESQL request count tests (#204925) (#204997)
# Backport This will backport the following commits from `main` to `8.x`: - [[Discover] Reintroduce ESQL request count tests (#204925)](https://github.com/elastic/kibana/pull/204925) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Matthias Wilhelm","email":"matthias.wilhelm@elastic.co"},"sourceCommit":{"committedDate":"2024-12-19T18:44:25Z","message":"[Discover] Reintroduce ESQL request count tests (#204925)","sha":"fa3029225ae386a71f0109132354746a75201dd7","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Discover","release_note:skip","v9.0.0","Team:DataDiscovery","backport:prev-minor","Feature:ES|QL"],"title":"[Discover] Reintroduce ESQL request count tests","number":204925,"url":"https://github.com/elastic/kibana/pull/204925","mergeCommit":{"message":"[Discover] Reintroduce ESQL request count tests (#204925)","sha":"fa3029225ae386a71f0109132354746a75201dd7"}},"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/204925","number":204925,"mergeCommit":{"message":"[Discover] Reintroduce ESQL request count tests (#204925)","sha":"fa3029225ae386a71f0109132354746a75201dd7"}}]}] BACKPORT--> Co-authored-by: Matthias Wilhelm <matthias.wilhelm@elastic.co> |
||
Rodney Norris
|
046324b342
|
[8.x] [Search] Deprecate canDeployEntSearch config value (#204272) (#204585)
# Backport This will backport the following commits from `main` to `8.x`: - [[Search] Deprecate canDeployEntSearch config value (#204272)](https://github.com/elastic/kibana/pull/204272) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Rodney Norris","email":"rodney.norris@elastic.co"},"sourceCommit":{"committedDate":"2024-12-17T13:16:33Z","message":"[Search] Deprecate canDeployEntSearch config value (#204272)","sha":"9f53fbbcc38cf709f0202e39b5fce7004a88e87b","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Search","backport:prev-minor","v8.18.0"],"number":204272,"url":"https://github.com/elastic/kibana/pull/204272","mergeCommit":{"message":"[Search] Deprecate canDeployEntSearch config value (#204272)","sha":"9f53fbbcc38cf709f0202e39b5fce7004a88e87b"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/204272","number":204272,"mergeCommit":{"message":"[Search] Deprecate canDeployEntSearch config value (#204272)","sha":"9f53fbbcc38cf709f0202e39b5fce7004a88e87b"}},{"branch":"8.x","label":"v8.18.0","labelRegex":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |