mirror of
https://github.com/elastic/kibana.git
synced 2025-06-27 18:51:07 -04:00
6692 commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
Kibana Machine
|
ff543226e8
|
[9.0] [UI Counters] fix flaky test retry logic (#224151) (#224167)
# Backport This will backport the following commits from `main` to `9.0`: - [[UI Counters] fix flaky test retry logic (#224151)](https://github.com/elastic/kibana/pull/224151) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Ahmad Bamieh","email":"ahmad.bamyeh@elastic.co"},"sourceCommit":{"committedDate":"2025-06-17T01:37:37Z","message":"[UI Counters] fix flaky test retry logic (#224151)\n\nRevisit `waitForWithTimeout` to use 5 retries and an initial waiting\ntime\ncloses https://github.com/elastic/kibana/issues/98240\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"699212fa7eb7a5440759c8a01f095e0bf2ca9479","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","backport:prev-major","v9.1.0","v9.0.3"],"title":"[UI Counters] fix flaky test retry logic","number":224151,"url":"https://github.com/elastic/kibana/pull/224151","mergeCommit":{"message":"[UI Counters] fix flaky test retry logic (#224151)\n\nRevisit `waitForWithTimeout` to use 5 retries and an initial waiting\ntime\ncloses https://github.com/elastic/kibana/issues/98240\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"699212fa7eb7a5440759c8a01f095e0bf2ca9479"}},"sourceBranch":"main","suggestedTargetBranches":["9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/224151","number":224151,"mergeCommit":{"message":"[UI Counters] fix flaky test retry logic (#224151)\n\nRevisit `waitForWithTimeout` to use 5 retries and an initial waiting\ntime\ncloses https://github.com/elastic/kibana/issues/98240\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"699212fa7eb7a5440759c8a01f095e0bf2ca9479"}},{"branch":"9.0","label":"v9.0.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Ahmad Bamieh <ahmad.bamyeh@elastic.co> |
||
|
Kibana Machine
|
5419984424
|
[9.0] Add trace.id to EBT events (#222366) (#223517)
# Backport This will backport the following commits from `main` to `9.0`: - [Add trace.id to EBT events (#222366)](https://github.com/elastic/kibana/pull/222366) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Maryam Saeidi","email":"maryam.saeidi@elastic.co"},"sourceCommit":{"committedDate":"2025-06-11T20:11:41Z","message":"Add trace.id to EBT events (#222366)\n\nCloses https://github.com/elastic/observability-dev/issues/4445\n\nEBT implementation: https://github.com/elastic/ebt/pull/57\n\n## Summary\n\nIn this PR, we are adding `getTraceContext` to the `createAnalytics` in\norder to include `trace.id` in the EBT events.\n\n\n\n\n### ⚠️ Note\n\nSome events might not have a `trace.id` due to not having an active\ntransaction at the moment of reporting the event. For those, we can\nimplement more sophisticated logic to keep track of transactions and use\nthe `trace.id` of the last one for the event (in a follow-up ticket, if\nnecessary).\n\n### How to test\n- Add `telemetry.localShipper: true` to the kibana config and create a\ndata view for `ebt-kibana-browser` index\n- Check the `trace.id` in the events that are passed\n\n---------\n\nCo-authored-by: Alejandro Fernández Haro <alejandro.haro@elastic.co>","sha":"cfc7f0ed0e84e486b9757756334f61153bae2037","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:version","v9.1.0","v8.19.0","author:obs-ux-management","v9.0.3"],"title":"Add trace.id to EBT events","number":222366,"url":"https://github.com/elastic/kibana/pull/222366","mergeCommit":{"message":"Add trace.id to EBT events (#222366)\n\nCloses https://github.com/elastic/observability-dev/issues/4445\n\nEBT implementation: https://github.com/elastic/ebt/pull/57\n\n## Summary\n\nIn this PR, we are adding `getTraceContext` to the `createAnalytics` in\norder to include `trace.id` in the EBT events.\n\n\n\n\n### ⚠️ Note\n\nSome events might not have a `trace.id` due to not having an active\ntransaction at the moment of reporting the event. For those, we can\nimplement more sophisticated logic to keep track of transactions and use\nthe `trace.id` of the last one for the event (in a follow-up ticket, if\nnecessary).\n\n### How to test\n- Add `telemetry.localShipper: true` to the kibana config and create a\ndata view for `ebt-kibana-browser` index\n- Check the `trace.id` in the events that are passed\n\n---------\n\nCo-authored-by: Alejandro Fernández Haro <alejandro.haro@elastic.co>","sha":"cfc7f0ed0e84e486b9757756334f61153bae2037"}},"sourceBranch":"main","suggestedTargetBranches":["9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/222366","number":222366,"mergeCommit":{"message":"Add trace.id to EBT events (#222366)\n\nCloses https://github.com/elastic/observability-dev/issues/4445\n\nEBT implementation: https://github.com/elastic/ebt/pull/57\n\n## Summary\n\nIn this PR, we are adding `getTraceContext` to the `createAnalytics` in\norder to include `trace.id` in the EBT events.\n\n\n\n\n### ⚠️ Note\n\nSome events might not have a `trace.id` due to not having an active\ntransaction at the moment of reporting the event. For those, we can\nimplement more sophisticated logic to keep track of transactions and use\nthe `trace.id` of the last one for the event (in a follow-up ticket, if\nnecessary).\n\n### How to test\n- Add `telemetry.localShipper: true` to the kibana config and create a\ndata view for `ebt-kibana-browser` index\n- Check the `trace.id` in the events that are passed\n\n---------\n\nCo-authored-by: Alejandro Fernández Haro <alejandro.haro@elastic.co>","sha":"cfc7f0ed0e84e486b9757756334f61153bae2037"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/223464","number":223464,"state":"MERGED","mergeCommit":{"sha":"71b79af9b7c44566118e65b2e6d9341c5c39898d","message":"[8.19] Add trace.id to EBT events (#222366) (#223464)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.19`:\n- [Add trace.id to EBT events\n(#222366)](https://github.com/elastic/kibana/pull/222366)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Maryam Saeidi <maryam.saeidi@elastic.co>\nCo-authored-by: Alejandro Fernández Haro <alejandro.haro@elastic.co>"}},{"branch":"9.0","label":"v9.0.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Maryam Saeidi <maryam.saeidi@elastic.co> Co-authored-by: Alejandro Fernández Haro <alejandro.haro@elastic.co> |
||
Alejandro Fernández Haro
|
cd00c41781
|
[9.0] Update dependency @elastic/ebt to ^1.2.0 (main) (#222852) (#223112)
# Backport This will backport the following commits from `main` to `9.0`: - [Update dependency @elastic/ebt to ^1.2.0 (main) (#222852)](https://github.com/elastic/kibana/pull/222852) <!--- Backport version: 10.0.0 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"elastic-renovate-prod[bot]","email":"174716857+elastic-renovate-prod[bot]@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-06-06T08:13:25Z","message":"Update dependency @elastic/ebt to ^1.2.0 (main) (#222852)","sha":"6540ec423cb6f6364accfb99dd837898f8c5adc9","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","v9.0.0","backport:version","v9.1.0","v8.19.0"],"title":"Update dependency @elastic/ebt to ^1.2.0 (main)","number":222852,"url":"https://github.com/elastic/kibana/pull/222852","mergeCommit":{"message":"Update dependency @elastic/ebt to ^1.2.0 (main) (#222852)","sha":"6540ec423cb6f6364accfb99dd837898f8c5adc9"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.19"],"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/222852","number":222852,"mergeCommit":{"message":"Update dependency @elastic/ebt to ^1.2.0 (main) (#222852)","sha":"6540ec423cb6f6364accfb99dd837898f8c5adc9"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> |
||
Matthias Wilhelm
|
374e3c65d4
|
[9.0] [Dataview] Fix flaky Dataviews field edit tests by using a single document (#221088) (#222085)
# Backport This will backport the following commits from `main` to `9.0`: - [[Dataview] Fix flaky Dataviews field edit tests by using a single document (#221088)](https://github.com/elastic/kibana/pull/221088) <!--- Backport version: 10.0.0 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Matthias Wilhelm","email":"matthias.wilhelm@elastic.co"},"sourceCommit":{"committedDate":"2025-05-26T13:30:29Z","message":"[Dataview] Fix flaky Dataviews field edit tests by using a single document (#221088)\n\nUpdates functional tests to ingest only one document, avoiding flaky failures caused by inconsistent ordering. With only one document, ordering issues are no longer possible.","sha":"e13aa51e6e5c9dcf6c0142c961c9b75eb9b03cfa","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Data Views","release_note:skip","backport missing","Team:DataDiscovery","backport:prev-major","v9.1.0"],"title":"[Dataview] Fix flakiness in functional testing field edits ","number":221088,"url":"https://github.com/elastic/kibana/pull/221088","mergeCommit":{"message":"[Dataview] Fix flaky Dataviews field edit tests by using a single document (#221088)\n\nUpdates functional tests to ingest only one document, avoiding flaky failures caused by inconsistent ordering. With only one document, ordering issues are no longer possible.","sha":"e13aa51e6e5c9dcf6c0142c961c9b75eb9b03cfa"}},"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/221088","number":221088,"mergeCommit":{"message":"[Dataview] Fix flaky Dataviews field edit tests by using a single document (#221088)\n\nUpdates functional tests to ingest only one document, avoiding flaky failures caused by inconsistent ordering. With only one document, ordering issues are no longer possible.","sha":"e13aa51e6e5c9dcf6c0142c961c9b75eb9b03cfa"}}]}] BACKPORT--> |
||
Devon Thomson
|
4dbde1e3d7
|
[9.0] [Dashboard] Deprecate allow by value embeddables setting & remove usage (#221165) (#221952)
# Backport This will backport the following commits from `main` to `9.0`: - [[Dashboard] Deprecate allow by value embeddables setting & remove usage (#221165)](https://github.com/elastic/kibana/pull/221165) <!--- Backport version: 10.0.0 --> ### 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-05-28T19:43:06Z","message":"[Dashboard] Deprecate allow by value embeddables setting & remove usage (#221165)\n\nRemoves usage of the `allowByValueEmbeddables` setting","sha":"754afacb8e25e1b741a9f7a5b2cdc0b1ba243603","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Dashboard","release_note:deprecation","Team:Presentation","loe:small","technical debt","impact:low","backport:prev-minor","v9.1.0"],"title":"[Dashboard] Deprecate allow by value embeddables setting & remove usage","number":221165,"url":"https://github.com/elastic/kibana/pull/221165","mergeCommit":{"message":"[Dashboard] Deprecate allow by value embeddables setting & remove usage (#221165)\n\nRemoves usage of the `allowByValueEmbeddables` setting","sha":"754afacb8e25e1b741a9f7a5b2cdc0b1ba243603"}},"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/221165","number":221165,"mergeCommit":{"message":"[Dashboard] Deprecate allow by value embeddables setting & remove usage (#221165)\n\nRemoves usage of the `allowByValueEmbeddables` setting","sha":"754afacb8e25e1b741a9f7a5b2cdc0b1ba243603"}}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
Kibana Machine
|
ea2ff4db67
|
[9.0] [Discover] Show ES|QL request URL in Inpector flyout (#221816) (#221893)
# Backport This will backport the following commits from `main` to `9.0`: - [[Discover] Show ES|QL request URL in Inpector flyout (#221816)](https://github.com/elastic/kibana/pull/221816) <!--- 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-05-29T08:30:13Z","message":"[Discover] Show ES|QL request URL in Inpector flyout (#221816)\n\n- Closes https://github.com/elastic/kibana/issues/221581\n\n## Summary\n\nThis PR adds the missing `requestParams` to the search interceptor code.\nThis makes the request URL appear again in Inpector flyout (Request\ntab).\n\n<img width=\"1072\" alt=\"Screenshot 2025-05-28 at 17 55 09\"\nsrc=\"https://github.com/user-attachments/assets/1c11c7d7-1e49-4265-a014-88f369dad2a7\"\n/>\n\n\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\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":"7fae9c5d6e86a588f6657dabe6894519449a03ad","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","Team:DataDiscovery","Feature:ES|QL","backport:version","v9.1.0","v8.19.0"],"title":"[Discover] Show ES|QL request URL in Inpector flyout","number":221816,"url":"https://github.com/elastic/kibana/pull/221816","mergeCommit":{"message":"[Discover] Show ES|QL request URL in Inpector flyout (#221816)\n\n- Closes https://github.com/elastic/kibana/issues/221581\n\n## Summary\n\nThis PR adds the missing `requestParams` to the search interceptor code.\nThis makes the request URL appear again in Inpector flyout (Request\ntab).\n\n<img width=\"1072\" alt=\"Screenshot 2025-05-28 at 17 55 09\"\nsrc=\"https://github.com/user-attachments/assets/1c11c7d7-1e49-4265-a014-88f369dad2a7\"\n/>\n\n\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\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":"7fae9c5d6e86a588f6657dabe6894519449a03ad"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.19"],"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/221816","number":221816,"mergeCommit":{"message":"[Discover] Show ES|QL request URL in Inpector flyout (#221816)\n\n- Closes https://github.com/elastic/kibana/issues/221581\n\n## Summary\n\nThis PR adds the missing `requestParams` to the search interceptor code.\nThis makes the request URL appear again in Inpector flyout (Request\ntab).\n\n<img width=\"1072\" alt=\"Screenshot 2025-05-28 at 17 55 09\"\nsrc=\"https://github.com/user-attachments/assets/1c11c7d7-1e49-4265-a014-88f369dad2a7\"\n/>\n\n\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\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":"7fae9c5d6e86a588f6657dabe6894519449a03ad"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Julia Rechkunova <julia.rechkunova@elastic.co> |
||
|
Kibana Machine
|
a6d573870b | skip failing test suite (#213784) | ||
Ola Pawlus
|
0d4cf66dd1
|
[9.0] Fix: success message and scroll after adding panel from library (#220122) (#220776)
# Backport This will backport the following commits from `main` to `9.0`: - [Fix: success message and scroll after adding panel from library (#220122)](https://github.com/elastic/kibana/pull/220122) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Ola Pawlus","email":"98127445+olapawlus@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-05-09T17:24:49Z","message":"Fix: success message and scroll after adding panel from library (#220122)\n\nInitially there was no success message for any type in the library and\nthere was no scrolling to added panel.\n\nThis change sets displaySuccessMessage to true for each plugin\nregistered in the Add from Library flyout.\n\nIt ensures that:\n- users see a success toast after adding a panel,\n- the newly added panel is automatically scrolled into view.\n\nCloses: #188775\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"e7e8d2f13b44ae78b33ada4a3904b17066c6fd37","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","Feature:Dashboard","Feature:Embedding","regression","release_note:fix","Team:Presentation","loe:small","impact:high","backport:version","v9.1.0","v8.19.0","v8.18.2","v9.0.2"],"title":"Fix: success message and scroll after adding panel from library","number":220122,"url":"https://github.com/elastic/kibana/pull/220122","mergeCommit":{"message":"Fix: success message and scroll after adding panel from library (#220122)\n\nInitially there was no success message for any type in the library and\nthere was no scrolling to added panel.\n\nThis change sets displaySuccessMessage to true for each plugin\nregistered in the Add from Library flyout.\n\nIt ensures that:\n- users see a success toast after adding a panel,\n- the newly added panel is automatically scrolled into view.\n\nCloses: #188775\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"e7e8d2f13b44ae78b33ada4a3904b17066c6fd37"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/220122","number":220122,"mergeCommit":{"message":"Fix: success message and scroll after adding panel from library (#220122)\n\nInitially there was no success message for any type in the library and\nthere was no scrolling to added panel.\n\nThis change sets displaySuccessMessage to true for each plugin\nregistered in the Add from Library flyout.\n\nIt ensures that:\n- users see a success toast after adding a panel,\n- the newly added panel is automatically scrolled into view.\n\nCloses: #188775\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"e7e8d2f13b44ae78b33ada4a3904b17066c6fd37"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/220703","number":220703,"state":"MERGED","mergeCommit":{"sha":"7501611e3277d378ea00e1731b39be0ebeb7769b","message":"[8.19] Fix: success message and scroll after adding panel from library (#220122) (#220703)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.19`:\n- [Fix: success message and scroll after adding panel from library\n(#220122)](https://github.com/elastic/kibana/pull/220122)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Ola Pawlus <98127445+olapawlus@users.noreply.github.com>"}},{"branch":"8.18","label":"v8.18.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
Elena Stoeva
|
7fab7e2ff8
|
[9.0] [Console] Fix context menu test for opening documentation (#218551) (#219064)
# Backport This will backport the following commits from `main` to `9.0`: - [[Console] Fix context menu test for opening documentation (#218551)](https://github.com/elastic/kibana/pull/218551) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Elena Stoeva","email":"59341489+ElenaStoeva@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-22T10:44:10Z","message":"[Console] Fix context menu test for opening documentation (#218551)\n\nFixes https://github.com/elastic/kibana/issues/218297\nFixes https://github.com/elastic/kibana/issues/143229\n\n## Summary\n\nThis PR fixes the Console tests for opening documentation which were\nfailing because the doc link\nhttps://www.elastic.co/guide/en/elasticsearch/reference/current/search-search.html\nis now redirecting to\nhttps://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-search.","sha":"4776e9bade7e79f01fa24566969888e9f5afdb06","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Console","Team:Kibana Management","release_note:skip","backport:prev-minor","v9.1.0","v9.0.1"],"title":"[Console] Fix context menu test for opening documentation","number":218551,"url":"https://github.com/elastic/kibana/pull/218551","mergeCommit":{"message":"[Console] Fix context menu test for opening documentation (#218551)\n\nFixes https://github.com/elastic/kibana/issues/218297\nFixes https://github.com/elastic/kibana/issues/143229\n\n## Summary\n\nThis PR fixes the Console tests for opening documentation which were\nfailing because the doc link\nhttps://www.elastic.co/guide/en/elasticsearch/reference/current/search-search.html\nis now redirecting to\nhttps://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-search.","sha":"4776e9bade7e79f01fa24566969888e9f5afdb06"}},"sourceBranch":"main","suggestedTargetBranches":["9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/218551","number":218551,"mergeCommit":{"message":"[Console] Fix context menu test for opening documentation (#218551)\n\nFixes https://github.com/elastic/kibana/issues/218297\nFixes https://github.com/elastic/kibana/issues/143229\n\n## Summary\n\nThis PR fixes the Console tests for opening documentation which were\nfailing because the doc link\nhttps://www.elastic.co/guide/en/elasticsearch/reference/current/search-search.html\nis now redirecting to\nhttps://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-search.","sha":"4776e9bade7e79f01fa24566969888e9f5afdb06"}},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Matthew Kime <matt@mattki.me> |
||
|
Elena Stoeva
|
fa3f35b4cd
|
[9.0] [Console] Fix output when HTTP request to server fails (#219073) (#219439)
# Backport This will backport the following commits from `main` to `9.0`: - [[Console] Fix output when HTTP request to server fails (#219073)](https://github.com/elastic/kibana/pull/219073) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Elena Stoeva","email":"59341489+ElenaStoeva@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-25T17:09:09Z","message":"[Console] Fix output when HTTP request to server fails (#219073)\n\nFollow-up to\nhttps://github.com/elastic/kibana/pull/218104#issuecomment-2824757130\n\n## Summary\n\nThis PR fixes the Console output when the HTTP request to the server\nfails with a non-empty error body. In\nhttps://github.com/elastic/kibana/pull/218104, we incorrectly set the\noutput to be `Request failed to get to the server (status code: ' +\nstatusCode + ')` even if there is an error body. In this PR, we make\nsure to display the error body if it's non-empty.\n\n**How to test:**\n\nSend a request that fails and verify that the error body is displayed:\n\n```\nPOST kbn:/api/alerting/rule/3603c386-9102-4c74-800d-2242e52bec98\n{\n \"name\": \"Alert on status change\",\n \"rule_type_id\": \".es-querya\"\n}\n```\n<img width=\"1160\" alt=\"Screenshot 2025-04-24 at 14 41 57\"\nsrc=\"https://github.com/user-attachments/assets/ced78171-4924-477f-ba2f-d5812bff1678\"\n/>","sha":"cb0acc16ee85e4dccc67dcb69dbbba3f328accad","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Console","Team:Kibana Management","release_note:skip","backport:prev-minor","v9.1.0","v8.19.0","v8.18.1","v9.0.1"],"title":"[Console] Fix output when HTTP request to server fails","number":219073,"url":"https://github.com/elastic/kibana/pull/219073","mergeCommit":{"message":"[Console] Fix output when HTTP request to server fails (#219073)\n\nFollow-up to\nhttps://github.com/elastic/kibana/pull/218104#issuecomment-2824757130\n\n## Summary\n\nThis PR fixes the Console output when the HTTP request to the server\nfails with a non-empty error body. In\nhttps://github.com/elastic/kibana/pull/218104, we incorrectly set the\noutput to be `Request failed to get to the server (status code: ' +\nstatusCode + ')` even if there is an error body. In this PR, we make\nsure to display the error body if it's non-empty.\n\n**How to test:**\n\nSend a request that fails and verify that the error body is displayed:\n\n```\nPOST kbn:/api/alerting/rule/3603c386-9102-4c74-800d-2242e52bec98\n{\n \"name\": \"Alert on status change\",\n \"rule_type_id\": \".es-querya\"\n}\n```\n<img width=\"1160\" alt=\"Screenshot 2025-04-24 at 14 41 57\"\nsrc=\"https://github.com/user-attachments/assets/ced78171-4924-477f-ba2f-d5812bff1678\"\n/>","sha":"cb0acc16ee85e4dccc67dcb69dbbba3f328accad"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/219073","number":219073,"mergeCommit":{"message":"[Console] Fix output when HTTP request to server fails (#219073)\n\nFollow-up to\nhttps://github.com/elastic/kibana/pull/218104#issuecomment-2824757130\n\n## Summary\n\nThis PR fixes the Console output when the HTTP request to the server\nfails with a non-empty error body. In\nhttps://github.com/elastic/kibana/pull/218104, we incorrectly set the\noutput to be `Request failed to get to the server (status code: ' +\nstatusCode + ')` even if there is an error body. In this PR, we make\nsure to display the error body if it's non-empty.\n\n**How to test:**\n\nSend a request that fails and verify that the error body is displayed:\n\n```\nPOST kbn:/api/alerting/rule/3603c386-9102-4c74-800d-2242e52bec98\n{\n \"name\": \"Alert on status change\",\n \"rule_type_id\": \".es-querya\"\n}\n```\n<img width=\"1160\" alt=\"Screenshot 2025-04-24 at 14 41 57\"\nsrc=\"https://github.com/user-attachments/assets/ced78171-4924-477f-ba2f-d5812bff1678\"\n/>","sha":"cb0acc16ee85e4dccc67dcb69dbbba3f328accad"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/219295","number":219295,"state":"MERGED","mergeCommit":{"sha":"cd3c92728e0e6792a2dcf8a39b3d8bf71589c929","message":"[8.19] [Console] Fix output when HTTP request to server fails (#219073) (#219295)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.19`:\n- [[Console] Fix output when HTTP request to server fails\n(#219073)](https://github.com/elastic/kibana/pull/219073)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Elena Stoeva <59341489+ElenaStoeva@users.noreply.github.com>"}},{"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"}]}] BACKPORT--> |
||
Patrick Mueller
|
7b1686c83d
|
[9.0] [ResponseOps][Alerting] allow rule types to be disabled via config (#218844) (#219323)
# Backport This will backport the following commits from `main` to `9.0`: - [[ResponseOps][Alerting] allow rule types to be disabled via config (#218844)](https://github.com/elastic/kibana/pull/218844) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Patrick Mueller","email":"patrick.mueller@elastic.co"},"sourceCommit":{"committedDate":"2025-04-24T13:43:36Z","message":"[ResponseOps][Alerting] allow rule types to be disabled via config (#218844)\n\nresolves https://github.com/elastic/kibana/issues/218616\n\nAdds kibana config `xpack.alerting.disabledRuleTypes: string[]`, which\ncan be used to \"disable\" specific rule types. The config is checked when\na rule type is registered, and if the rule type should be disabled, it\nwon't be added to the rule type registry and will log an INFO message\nabout the rule type being disabled.","sha":"bdef66fa4c5b5015e0d4f9694cefc59c13e2be49","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Alerting","release_note:skip","Team:ResponseOps","Feature:Alerting/RulesFramework","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1"],"title":"[ResponseOps][Alerting] allow rule types to be disabled via config","number":218844,"url":"https://github.com/elastic/kibana/pull/218844","mergeCommit":{"message":"[ResponseOps][Alerting] allow rule types to be disabled via config (#218844)\n\nresolves https://github.com/elastic/kibana/issues/218616\n\nAdds kibana config `xpack.alerting.disabledRuleTypes: string[]`, which\ncan be used to \"disable\" specific rule types. The config is checked when\na rule type is registered, and if the rule type should be disabled, it\nwon't be added to the rule type registry and will log an INFO message\nabout the rule type being disabled.","sha":"bdef66fa4c5b5015e0d4f9694cefc59c13e2be49"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","8.18","9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/218844","number":218844,"mergeCommit":{"message":"[ResponseOps][Alerting] allow rule types to be disabled via config (#218844)\n\nresolves https://github.com/elastic/kibana/issues/218616\n\nAdds kibana config `xpack.alerting.disabledRuleTypes: string[]`, which\ncan be used to \"disable\" specific rule types. The config is checked when\na rule type is registered, and if the rule type should be disabled, it\nwon't be added to the rule type registry and will log an INFO message\nabout the rule type being disabled.","sha":"bdef66fa4c5b5015e0d4f9694cefc59c13e2be49"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"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"}]}] BACKPORT--> --------- Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> |
||
Lene Gadewoll
|
1c15615a80
|
[9.0] Upgrade EUI to v101.4.0 (#218778) (#219117)
# Backport This will backport the following commits from `main` to `9.0`: - [Upgrade EUI to v101.4.0 (#218778)](https://github.com/elastic/kibana/pull/218778) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Lene Gadewoll","email":"lene.gadewoll@elastic.co"},"sourceCommit":{"committedDate":"2025-04-24T13:54:52Z","message":"Upgrade EUI to v101.4.0 (#218778)\n\n`101.3.0` ⏩ `101.4.0`\n\n[Questions? Please see our Kibana upgrade\nFAQ.](https://github.com/elastic/eui/blob/main/wiki/eui-team-processes/upgrading-kibana.md#faq-for-kibana-teams)\n\n## Changes\n\nThis PR only updates tests and snapshots related to changes on EUI side:\n- updated `aria-current=\"true\"` to `aria-current=\"page\"`\n- updated icon usage `userAvatar` to `user`\n\n## Package updates\n\n### `@elastic/eui`\n\n#### [`v101.4.0`](https://github.com/elastic/eui/releases/v101.4.0)\n\n- Spread `labelProps` to the `label` element in `EuiCheckableCard`\n([#8586](https://github.com/elastic/eui/pull/8586))\n- Add `controls`, `flask`, `comment`, and `readOnly` glyphs to `EuiIcon`\n([#8580](https://github.com/elastic/eui/pull/8580))\n- Refactored `EuiExpression`, `EuiFacetGroup`, `EuiFacetButton`,\n`EuiFilterGroup`, `EuiHeader`, `EuiImage` and `EuiListGroup` to memoize\ntheir internal Emotion styles\n([#8565](https://github.com/elastic/eui/pull/8565))\n- Updated global `border.radius.medium` token value for default\n`Borealis` theme to `4px`\n([#8563](https://github.com/elastic/eui/pull/8563))\n- Updated `EuiProvider` to build themes including `highContrastMode`\n([#8558](https://github.com/elastic/eui/pull/8558))\n\n**Accessibility**\n\n- Removed the `aria-label` attribute from the `ul` element in\n`EuiPagination` to avoid duplicate screen reader output\n([#8597](https://github.com/elastic/eui/pull/8597))\n- Set a more specific `aria-current=\"page\"` on list items in\n`EuiPagination` ([#8597](https://github.com/elastic/eui/pull/8597))\n- Added `aria-modal` to `EuiFlyout` with `type=\"overlay\"`\n([#8591](https://github.com/elastic/eui/pull/8591))\n\n**Dependency updates**\n\n- Updated `@elastic/prismjs-esql` to v1.1.0\n([#8587](https://github.com/elastic/eui/pull/8587))\n\n### `@elastic/eui-theme-borealis@0.2.0`\n\n- Updated component tokens to use `computed` values to ensure correct\ninheritance from theme overrides\n([#8558](https://github.com/elastic/eui/pull/8558))\n- Added `overrides.HCM` to `euiThemeBorealis` to support theme internal\noverrides ([#8558](https://github.com/elastic/eui/pull/8558))\n- Updated `border.radius.medium` token value to `4px`\n([#8563](https://github.com/elastic/eui/pull/8563))\n\n### `@elastic/eui-theme-common@0.2.0`\n\n- Added support for theme `overrides` as optional part of\n`EuiThemeShape` ([#8558](https://github.com/elastic/eui/pull/8558))\n- Updated `getComputed` to support high contrast mode overrides defined\non `overrides.HCM` ([#8558](https://github.com/elastic/eui/pull/8558))\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"d2d27658f36040752ee7747bddb9d17030823352","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","EUI","backport:prev-minor","v9.1.0"],"title":"Upgrade EUI to v101.4.0","number":218778,"url":"https://github.com/elastic/kibana/pull/218778","mergeCommit":{"message":"Upgrade EUI to v101.4.0 (#218778)\n\n`101.3.0` ⏩ `101.4.0`\n\n[Questions? Please see our Kibana upgrade\nFAQ.](https://github.com/elastic/eui/blob/main/wiki/eui-team-processes/upgrading-kibana.md#faq-for-kibana-teams)\n\n## Changes\n\nThis PR only updates tests and snapshots related to changes on EUI side:\n- updated `aria-current=\"true\"` to `aria-current=\"page\"`\n- updated icon usage `userAvatar` to `user`\n\n## Package updates\n\n### `@elastic/eui`\n\n#### [`v101.4.0`](https://github.com/elastic/eui/releases/v101.4.0)\n\n- Spread `labelProps` to the `label` element in `EuiCheckableCard`\n([#8586](https://github.com/elastic/eui/pull/8586))\n- Add `controls`, `flask`, `comment`, and `readOnly` glyphs to `EuiIcon`\n([#8580](https://github.com/elastic/eui/pull/8580))\n- Refactored `EuiExpression`, `EuiFacetGroup`, `EuiFacetButton`,\n`EuiFilterGroup`, `EuiHeader`, `EuiImage` and `EuiListGroup` to memoize\ntheir internal Emotion styles\n([#8565](https://github.com/elastic/eui/pull/8565))\n- Updated global `border.radius.medium` token value for default\n`Borealis` theme to `4px`\n([#8563](https://github.com/elastic/eui/pull/8563))\n- Updated `EuiProvider` to build themes including `highContrastMode`\n([#8558](https://github.com/elastic/eui/pull/8558))\n\n**Accessibility**\n\n- Removed the `aria-label` attribute from the `ul` element in\n`EuiPagination` to avoid duplicate screen reader output\n([#8597](https://github.com/elastic/eui/pull/8597))\n- Set a more specific `aria-current=\"page\"` on list items in\n`EuiPagination` ([#8597](https://github.com/elastic/eui/pull/8597))\n- Added `aria-modal` to `EuiFlyout` with `type=\"overlay\"`\n([#8591](https://github.com/elastic/eui/pull/8591))\n\n**Dependency updates**\n\n- Updated `@elastic/prismjs-esql` to v1.1.0\n([#8587](https://github.com/elastic/eui/pull/8587))\n\n### `@elastic/eui-theme-borealis@0.2.0`\n\n- Updated component tokens to use `computed` values to ensure correct\ninheritance from theme overrides\n([#8558](https://github.com/elastic/eui/pull/8558))\n- Added `overrides.HCM` to `euiThemeBorealis` to support theme internal\noverrides ([#8558](https://github.com/elastic/eui/pull/8558))\n- Updated `border.radius.medium` token value to `4px`\n([#8563](https://github.com/elastic/eui/pull/8563))\n\n### `@elastic/eui-theme-common@0.2.0`\n\n- Added support for theme `overrides` as optional part of\n`EuiThemeShape` ([#8558](https://github.com/elastic/eui/pull/8558))\n- Updated `getComputed` to support high contrast mode overrides defined\non `overrides.HCM` ([#8558](https://github.com/elastic/eui/pull/8558))\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"d2d27658f36040752ee7747bddb9d17030823352"}},"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/218778","number":218778,"mergeCommit":{"message":"Upgrade EUI to v101.4.0 (#218778)\n\n`101.3.0` ⏩ `101.4.0`\n\n[Questions? Please see our Kibana upgrade\nFAQ.](https://github.com/elastic/eui/blob/main/wiki/eui-team-processes/upgrading-kibana.md#faq-for-kibana-teams)\n\n## Changes\n\nThis PR only updates tests and snapshots related to changes on EUI side:\n- updated `aria-current=\"true\"` to `aria-current=\"page\"`\n- updated icon usage `userAvatar` to `user`\n\n## Package updates\n\n### `@elastic/eui`\n\n#### [`v101.4.0`](https://github.com/elastic/eui/releases/v101.4.0)\n\n- Spread `labelProps` to the `label` element in `EuiCheckableCard`\n([#8586](https://github.com/elastic/eui/pull/8586))\n- Add `controls`, `flask`, `comment`, and `readOnly` glyphs to `EuiIcon`\n([#8580](https://github.com/elastic/eui/pull/8580))\n- Refactored `EuiExpression`, `EuiFacetGroup`, `EuiFacetButton`,\n`EuiFilterGroup`, `EuiHeader`, `EuiImage` and `EuiListGroup` to memoize\ntheir internal Emotion styles\n([#8565](https://github.com/elastic/eui/pull/8565))\n- Updated global `border.radius.medium` token value for default\n`Borealis` theme to `4px`\n([#8563](https://github.com/elastic/eui/pull/8563))\n- Updated `EuiProvider` to build themes including `highContrastMode`\n([#8558](https://github.com/elastic/eui/pull/8558))\n\n**Accessibility**\n\n- Removed the `aria-label` attribute from the `ul` element in\n`EuiPagination` to avoid duplicate screen reader output\n([#8597](https://github.com/elastic/eui/pull/8597))\n- Set a more specific `aria-current=\"page\"` on list items in\n`EuiPagination` ([#8597](https://github.com/elastic/eui/pull/8597))\n- Added `aria-modal` to `EuiFlyout` with `type=\"overlay\"`\n([#8591](https://github.com/elastic/eui/pull/8591))\n\n**Dependency updates**\n\n- Updated `@elastic/prismjs-esql` to v1.1.0\n([#8587](https://github.com/elastic/eui/pull/8587))\n\n### `@elastic/eui-theme-borealis@0.2.0`\n\n- Updated component tokens to use `computed` values to ensure correct\ninheritance from theme overrides\n([#8558](https://github.com/elastic/eui/pull/8558))\n- Added `overrides.HCM` to `euiThemeBorealis` to support theme internal\noverrides ([#8558](https://github.com/elastic/eui/pull/8558))\n- Updated `border.radius.medium` token value to `4px`\n([#8563](https://github.com/elastic/eui/pull/8563))\n\n### `@elastic/eui-theme-common@0.2.0`\n\n- Added support for theme `overrides` as optional part of\n`EuiThemeShape` ([#8558](https://github.com/elastic/eui/pull/8558))\n- Updated `getComputed` to support high contrast mode overrides defined\non `overrides.HCM` ([#8558](https://github.com/elastic/eui/pull/8558))\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"d2d27658f36040752ee7747bddb9d17030823352"}}]}] BACKPORT--> |
||
|
Elena Stoeva
|
de1b09a732
|
[9.0] [Console] Fix test for opening documentation (#218318) (#218552)
# Backport This will backport the following commits from `main` to `9.0`: - [[Console] Fix test for opening documentation (#218318)](https://github.com/elastic/kibana/pull/218318) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Elena Stoeva","email":"59341489+ElenaStoeva@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-17T09:28:01Z","message":"[Console] Fix test for opening documentation (#218318)\n\nFixes https://github.com/elastic/kibana/issues/218255\n\n## Summary\n\nThis PR fixes the Console tests for opening documentation which were\nfailing because the doc link\nhttps://www.elastic.co/guide/en/elasticsearch/reference/current/search-search.html\nis now redirecting to\nhttps://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-search.","sha":"5ce6ce575f25fa93a89234e1a5431627209d989b","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Console","Team:Kibana Management","release_note:skip","backport:prev-minor","v9.1.0","v9.0.1"],"title":"[Console] Fix test for opening documentation","number":218318,"url":"https://github.com/elastic/kibana/pull/218318","mergeCommit":{"message":"[Console] Fix test for opening documentation (#218318)\n\nFixes https://github.com/elastic/kibana/issues/218255\n\n## Summary\n\nThis PR fixes the Console tests for opening documentation which were\nfailing because the doc link\nhttps://www.elastic.co/guide/en/elasticsearch/reference/current/search-search.html\nis now redirecting to\nhttps://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-search.","sha":"5ce6ce575f25fa93a89234e1a5431627209d989b"}},"sourceBranch":"main","suggestedTargetBranches":["9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/218318","number":218318,"mergeCommit":{"message":"[Console] Fix test for opening documentation (#218318)\n\nFixes https://github.com/elastic/kibana/issues/218255\n\n## Summary\n\nThis PR fixes the Console tests for opening documentation which were\nfailing because the doc link\nhttps://www.elastic.co/guide/en/elasticsearch/reference/current/search-search.html\nis now redirecting to\nhttps://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-search.","sha":"5ce6ce575f25fa93a89234e1a5431627209d989b"}},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
267bb614aa
|
[9.0] [Discover] Stop keydown event propagation when unified doc tabs are focused (#218131) (#218300) (#218539)
# Backport This will backport the following commits from `main` to `9.0`: - [[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 |
||
|
Kibana Machine
|
91b43cf280 | skip failing test suite (#143229) | ||
|
Kibana Machine
|
41b029d2b1 | skip failing test suite (#213784) | ||
|
Kibana Machine
|
f9d26b45b6
|
[9.0] [Console] Fix a11y overlay test (#218130) (#218220)
# Backport This will backport the following commits from `main` to `9.0`: - [[Console] Fix a11y overlay test (#218130)](https://github.com/elastic/kibana/pull/218130) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Elena Stoeva","email":"59341489+ElenaStoeva@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-15T09:07:06Z","message":"[Console] Fix a11y overlay test (#218130)\n\nFixes https://github.com/elastic/kibana/issues/217057\n\n## Summary\n\nThis PR fixes the flaky test for the a11y overlay by adding a `retry`\nand allowing more time for the overlay element to be detected.\n\nFlaky test runner build:\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8176","sha":"d5bceb79d06d6688e7d7968be1ae71c6bf13e142","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","backport:prev-minor","v9.1.0","v8.19.0"],"title":"[Console] Fix a11y overlay test","number":218130,"url":"https://github.com/elastic/kibana/pull/218130","mergeCommit":{"message":"[Console] Fix a11y overlay test (#218130)\n\nFixes https://github.com/elastic/kibana/issues/217057\n\n## Summary\n\nThis PR fixes the flaky test for the a11y overlay by adding a `retry`\nand allowing more time for the overlay element to be detected.\n\nFlaky test runner build:\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8176","sha":"d5bceb79d06d6688e7d7968be1ae71c6bf13e142"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/218130","number":218130,"mergeCommit":{"message":"[Console] Fix a11y overlay test (#218130)\n\nFixes https://github.com/elastic/kibana/issues/217057\n\n## Summary\n\nThis PR fixes the flaky test for the a11y overlay by adding a `retry`\nand allowing more time for the overlay element to be detected.\n\nFlaky test runner build:\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8176","sha":"d5bceb79d06d6688e7d7968be1ae71c6bf13e142"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Elena Stoeva <59341489+ElenaStoeva@users.noreply.github.com> |
||
|
Ola Pawlus
|
2340287bdd
|
[9.0] [Dashboards] Update response on HTTP API should return a 200, not 201 (#217054) (#217499)
# Backport This will backport the following commits from `main` to `9.0`: - [[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":["9.0"],"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,"url":"https://github.com/elastic/kibana/pull/217494","number":217494,"state":"OPEN"},{"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,"url":"https://github.com/elastic/kibana/pull/217498","number":217498,"state":"OPEN"}]}] BACKPORT--> --------- Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> |
||
|
Kibana Machine
|
f0f94d54eb
|
[9.0] [Dashboard] Fix page object getPanels method for new grid system (#217812) (#217859)
# Backport This will backport the following commits from `main` to `9.0`: - [[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> |
||
Robert Oskamp
|
9a52c90fb8
|
[9.0] [kbn-scout] add test config category to reporting (#210167) (#217504)
# Backport This will backport the following commits from `main` to `9.0`: - [[kbn-scout] add test config category to reporting (#210167)](https://github.com/elastic/kibana/pull/210167) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Robert Oskamp","email":"robert.oskamp@elastic.co"},"sourceCommit":{"committedDate":"2025-02-12T10:17:04Z","message":"[kbn-scout] add test config category to reporting (#210167)\n\n## Summary\r\n\r\nThis PR adds a test config category to the scout reporting. This allows\r\nus to distinguish between UI and API FTR tests.\r\nA new property `testConfigCategory` has been added to all FTR configs\r\nthat don't already inherit it from a higher level config.","sha":"4bd80160b24fc2d136608d95e320291d3074eba2","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","ci:project-deploy-observability","Team:obs-ux-infra_services","backport:version","v9.1.0","v8.19.0"],"title":"[kbn-scout] add test config category to reporting","number":210167,"url":"https://github.com/elastic/kibana/pull/210167","mergeCommit":{"message":"[kbn-scout] add test config category to reporting (#210167)\n\n## Summary\r\n\r\nThis PR adds a test config category to the scout reporting. This allows\r\nus to distinguish between UI and API FTR tests.\r\nA new property `testConfigCategory` has been added to all FTR configs\r\nthat don't already inherit it from a higher level config.","sha":"4bd80160b24fc2d136608d95e320291d3074eba2"}},"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/210167","number":210167,"mergeCommit":{"message":"[kbn-scout] add test config category to reporting (#210167)\n\n## Summary\r\n\r\nThis PR adds a test config category to the scout reporting. This allows\r\nus to distinguish between UI and API FTR tests.\r\nA new property `testConfigCategory` has been added to all FTR configs\r\nthat don't already inherit it from a higher level config.","sha":"4bd80160b24fc2d136608d95e320291d3074eba2"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/210802","number":210802,"state":"MERGED","mergeCommit":{"sha":"84c90d5bb4749eb1d898d1ab242bbce73d6d9353","message":"[8.x] [kbn-scout] add test config category to reporting (#210167) (#210802)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[kbn-scout] add test config category to reporting\n(#210167)](https://github.com/elastic/kibana/pull/210167)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n"}}]}] BACKPORT--> |
||
Stratoula Kalafateli
|
66e6f03b52
|
[9.0] [ES|QL] Small changes to help potential flakiness (#216982) (#217030)
# Backport This will backport the following commits from `main` to `9.0`: - [[ES|QL] Small changes to help potential flakiness (#216982)](https://github.com/elastic/kibana/pull/216982) <!--- Backport version: 9.6.6 --> ### 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-04-03T14:00:32Z","message":"[ES|QL] Small changes to help potential flakiness (#216982)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/216398\n\nAnother small change to ensure flakiness. 100 times run\n\n### Checklist\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","sha":"eaf467f53c6bdfdfeba7249aaf03576aacf975af","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Feature:ES|QL","backport:version","v9.1.0","v8.19.0"],"title":"[ES|QL] Small changes to help potential flakiness","number":216982,"url":"https://github.com/elastic/kibana/pull/216982","mergeCommit":{"message":"[ES|QL] Small changes to help potential flakiness (#216982)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/216398\n\nAnother small change to ensure flakiness. 100 times run\n\n### Checklist\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","sha":"eaf467f53c6bdfdfeba7249aaf03576aacf975af"}},"sourceBranch":"main","suggestedTargetBranches":["9.0"],"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/216982","number":216982,"mergeCommit":{"message":"[ES|QL] Small changes to help potential flakiness (#216982)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/216398\n\nAnother small change to ensure flakiness. 100 times run\n\n### Checklist\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","sha":"eaf467f53c6bdfdfeba7249aaf03576aacf975af"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/217027","number":217027,"state":"OPEN"}]}] BACKPORT--> |
||
|
Stratoula Kalafateli
|
7ce4926655
|
[9.0] [ES|QL] Fixes the field controls FT flakiness (#216747) (#216981)
# Backport This will backport the following commits from `main` to `9.0`: - [[ES|QL] Fixes the field controls FT flakiness (#216747)](https://github.com/elastic/kibana/pull/216747) <!--- Backport version: 9.6.6 --> ### 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-04-02T13:31:48Z","message":"[ES|QL] Fixes the field controls FT flakiness (#216747)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/216398\n\nI also stabilized the values FT as it was also flaky 🤞 \n\n### Checklist\n\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","sha":"cf289cbd1e18a3b0798d00f866e446ce3753d8e9","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Feature:ES|QL","backport:version","v9.1.0","v8.19.0"],"title":"[ES|QL] Fixes the field controls FT flakiness","number":216747,"url":"https://github.com/elastic/kibana/pull/216747","mergeCommit":{"message":"[ES|QL] Fixes the field controls FT flakiness (#216747)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/216398\n\nI also stabilized the values FT as it was also flaky 🤞 \n\n### Checklist\n\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","sha":"cf289cbd1e18a3b0798d00f866e446ce3753d8e9"}},"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/216747","number":216747,"mergeCommit":{"message":"[ES|QL] Fixes the field controls FT flakiness (#216747)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/216398\n\nI also stabilized the values FT as it was also flaky 🤞 \n\n### Checklist\n\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","sha":"cf289cbd1e18a3b0798d00f866e446ce3753d8e9"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/216837","number":216837,"state":"MERGED","mergeCommit":{"sha":"0ccb82963a0987926370cb9eae212270c361838f","message":"[8.x] [ES|QL] Fixes the field controls FT flakiness (#216747) (#216837)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[ES|QL] Fixes the field controls FT flakiness\n(#216747)](https://github.com/elastic/kibana/pull/216747)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>"}}]}] BACKPORT--> |
||
|
Kibana Machine
|
67fb2fb9e4
|
[9.0] [Discover] Fix getAdditionalCellActions FTR tests (#216540) (#216860)
# Backport This will backport the following commits from `main` to `9.0`: - [[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
|
6c6c7c5077
|
[9.0] [Vega] Fix update vega spec in functional tests (#216620) (#216676)
# Backport This will backport the following commits from `main` to `9.0`: - [[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
|
6d39f4e844
|
[9.0] [Lens] fix drag and drop ghost after Chrome update to 134 (#213928) (#214127)
# Backport This will backport the following commits from `main` to `9.0`: - 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
|
ddcc4993d4
|
[9.0] unskip Failing test: Chrome UI Functional Tests.test/functional/apps/dashboard/group6/view_edit·ts (#211653) (#214433)
# Backport This will backport the following commits from `main` to `9.0`: - [unskip Failing test: Chrome UI Functional Tests.test/functional/apps/dashboard/group6/view_edit·ts (#211653)](https://github.com/elastic/kibana/pull/211653) <!--- Backport version: 9.6.6 --> ### 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-03-13T15:56:35Z","message":"unskip Failing test: Chrome UI Functional Tests.test/functional/apps/dashboard/group6/view_edit·ts (#211653)\n\nCloses https://github.com/elastic/kibana/issues/200748\n\nFlaky test runner\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8023\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"c886fb0f7362f18b0abb9a973c7f03b09b701446","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Presentation","release_note:skip","v9.0.0","backport:version","v9.1.0","v8.19.0"],"title":"unskip Failing test: Chrome UI Functional Tests.test/functional/apps/dashboard/group6/view_edit·ts","number":211653,"url":"https://github.com/elastic/kibana/pull/211653","mergeCommit":{"message":"unskip Failing test: Chrome UI Functional Tests.test/functional/apps/dashboard/group6/view_edit·ts (#211653)\n\nCloses https://github.com/elastic/kibana/issues/200748\n\nFlaky test runner\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8023\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"c886fb0f7362f18b0abb9a973c7f03b09b701446"}},"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/211653","number":211653,"mergeCommit":{"message":"unskip Failing test: Chrome UI Functional Tests.test/functional/apps/dashboard/group6/view_edit·ts (#211653)\n\nCloses https://github.com/elastic/kibana/issues/200748\n\nFlaky test runner\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8023\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"c886fb0f7362f18b0abb9a973c7f03b09b701446"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Nathan Reese <reese.nathan@elastic.co> |
||
|
Kibana Machine
|
efcfc36ba1
|
[9.0] [TSVB] Remove temporary fix for Borealis in TSVB test (#212050) (#213720)
# Backport This will backport the following commits from `main` to `9.0`: - [[TSVB] Remove temporary fix for Borealis in TSVB test (#212050)](https://github.com/elastic/kibana/pull/212050) <!--- 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-03-10T12:21:34Z","message":"[TSVB] Remove temporary fix for Borealis in TSVB test (#212050)\n\n## Summary\n\nFixes a workaround implemented in the TSVB functional tests to cover a\nflaky test that wasn't possible to solve locally.","sha":"d6afbe9675c52a4fcd83d0969faeef43aa6ea8a7","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["test","Feature:TSVB","Team:Visualizations","release_note:skip","backport:prev-minor","v9.1.0"],"title":"[TSVB] Remove temporary fix for Borealis in TSVB test","number":212050,"url":"https://github.com/elastic/kibana/pull/212050","mergeCommit":{"message":"[TSVB] Remove temporary fix for Borealis in TSVB test (#212050)\n\n## Summary\n\nFixes a workaround implemented in the TSVB functional tests to cover a\nflaky test that wasn't possible to solve locally.","sha":"d6afbe9675c52a4fcd83d0969faeef43aa6ea8a7"}},"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/212050","number":212050,"mergeCommit":{"message":"[TSVB] Remove temporary fix for Borealis in TSVB test (#212050)\n\n## Summary\n\nFixes a workaround implemented in the TSVB functional tests to cover a\nflaky test that wasn't possible to solve locally.","sha":"d6afbe9675c52a4fcd83d0969faeef43aa6ea8a7"}}]}] BACKPORT--> Co-authored-by: Marco Vettorello <marco.vettorello@elastic.co> |
||
|
Kibana Machine
|
fe7df8fbe3 | skip failing test suite (#213300) | ||
|
Kibana Machine
|
af0d7ebcf2
|
[9.0] [Lens/SCSS] Replace expression legacy metric scss (#209546) (#212885)
# Backport This will backport the following commits from `main` to `9.0`: - [[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> |
||
Gerard Soldevila
|
19db8f87a9
|
[9.0] SKA: Relocate "platform" packages that remain on /packages (#208704) (#212224)
# Backport This will backport the following commits from `main` to `9.0`: - [SKA: Relocate "platform" packages that remain on `/packages` (#208704)](https://github.com/elastic/kibana/pull/208704) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Gerard Soldevila","email":"gerard.soldevila@elastic.co"},"sourceCommit":{"committedDate":"2025-02-24T11:03:30Z","message":"SKA: Relocate \"platform\" packages that remain on `/packages` (#208704)\n\n## Summary\n\nThe `/packages` folder at the root of the Kibana repository used to\ncontain a lot of packages.\nIn the context of SKA, they have been gradually moved to various\nlocations:\n* `src/platform/packages`\n* `x-pack/platform/packages`\n* `src/core/packages`\n\nCurrently, only `devOnly: true` packages are left in this folder. This\ncomprises libraries for CLI scripts as well as testing utilities.\n\nWith this PR, we are moving ~half of these packages under\n`src/platform/packages/(private|shared)/`.\nIn particular, we are moving those packages that are being used from\nplatform and/or solutions.\n\nSince they are `\"devOnly\": true`, this means they are ONLY used from\ntests, cypress tests, storybook configs, ./scripts/ folders inside some\nmodules, or other non-prod-time logic. Nonetheless, they are effectively\nreferenced from platform and/or solutions code, hence I decided they\nshould be placed under `platform` folders.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"6a7c904f921434fe21dfa00eceabfb5e64e915dc","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","v9.0.0","ci:project-deploy-observability","Team:obs-ux-infra_services","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"SKA: Relocate \"platform\" packages that remain on `/packages`","number":208704,"url":"https://github.com/elastic/kibana/pull/208704","mergeCommit":{"message":"SKA: Relocate \"platform\" packages that remain on `/packages` (#208704)\n\n## Summary\n\nThe `/packages` folder at the root of the Kibana repository used to\ncontain a lot of packages.\nIn the context of SKA, they have been gradually moved to various\nlocations:\n* `src/platform/packages`\n* `x-pack/platform/packages`\n* `src/core/packages`\n\nCurrently, only `devOnly: true` packages are left in this folder. This\ncomprises libraries for CLI scripts as well as testing utilities.\n\nWith this PR, we are moving ~half of these packages under\n`src/platform/packages/(private|shared)/`.\nIn particular, we are moving those packages that are being used from\nplatform and/or solutions.\n\nSince they are `\"devOnly\": true`, this means they are ONLY used from\ntests, cypress tests, storybook configs, ./scripts/ folders inside some\nmodules, or other non-prod-time logic. Nonetheless, they are effectively\nreferenced from platform and/or solutions code, hence I decided they\nshould be placed under `platform` folders.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"6a7c904f921434fe21dfa00eceabfb5e64e915dc"}},"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/208704","number":208704,"mergeCommit":{"message":"SKA: Relocate \"platform\" packages that remain on `/packages` (#208704)\n\n## Summary\n\nThe `/packages` folder at the root of the Kibana repository used to\ncontain a lot of packages.\nIn the context of SKA, they have been gradually moved to various\nlocations:\n* `src/platform/packages`\n* `x-pack/platform/packages`\n* `src/core/packages`\n\nCurrently, only `devOnly: true` packages are left in this folder. This\ncomprises libraries for CLI scripts as well as testing utilities.\n\nWith this PR, we are moving ~half of these packages under\n`src/platform/packages/(private|shared)/`.\nIn particular, we are moving those packages that are being used from\nplatform and/or solutions.\n\nSince they are `\"devOnly\": true`, this means they are ONLY used from\ntests, cypress tests, storybook configs, ./scripts/ folders inside some\nmodules, or other non-prod-time logic. Nonetheless, they are effectively\nreferenced from platform and/or solutions code, hence I decided they\nshould be placed under `platform` folders.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"6a7c904f921434fe21dfa00eceabfb5e64e915dc"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
875ed7061c
|
[9.0] [Data View Field] Fix popularity score bugs (#211201) (#212617)
# Backport This will backport the following commits from `main` to `9.0`: - [[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
|
7711ae2fa0
|
[9.0] [Discover] [Embeddable] Fix Discover session embeddable drilldown (#211678) (#212143)
# Backport This will backport the following commits from `main` to `9.0`: - [[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
|
715a79bd47
|
[9.0] unskip dashboard_listing (#211742) (#211799)
# Backport This will backport the following commits from `main` to `9.0`: - [unskip dashboard_listing (#211742)](https://github.com/elastic/kibana/pull/211742) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Anton Dosov","email":"anton.dosov@elastic.co"},"sourceCommit":{"committedDate":"2025-02-19T15:42:26Z","message":"unskip dashboard_listing (#211742)\n\n## Summary\n\nclose https://github.com/elastic/kibana/issues/192564\n\nI thought I fixed this earlier, but looks like I forget to unskip 😮💨\nhttps://github.com/elastic/kibana/pull/197381\nThis is another attempt","sha":"97ee552d0ffa025c0d7b8032384c4a5b5513a495","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","v9.1.0"],"title":"unskip dashboard_listing","number":211742,"url":"https://github.com/elastic/kibana/pull/211742","mergeCommit":{"message":"unskip dashboard_listing (#211742)\n\n## Summary\n\nclose https://github.com/elastic/kibana/issues/192564\n\nI thought I fixed this earlier, but looks like I forget to unskip 😮💨\nhttps://github.com/elastic/kibana/pull/197381\nThis is another attempt","sha":"97ee552d0ffa025c0d7b8032384c4a5b5513a495"}},"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/211742","number":211742,"mergeCommit":{"message":"unskip dashboard_listing (#211742)\n\n## Summary\n\nclose https://github.com/elastic/kibana/issues/192564\n\nI thought I fixed this earlier, but looks like I forget to unskip 😮💨\nhttps://github.com/elastic/kibana/pull/197381\nThis is another attempt","sha":"97ee552d0ffa025c0d7b8032384c4a5b5513a495"}}]}] BACKPORT--> Co-authored-by: Anton Dosov <anton.dosov@elastic.co> |
||
|
Kibana Machine
|
99fb27899e
|
[9.0] [Lens] Remove scss from annotations plugin, visualization-ui-components and gauge expression (#208891) (#211567)
# Backport This will backport the following commits from `main` to `9.0`: - [[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
|
250d0551de
|
[9.0] [Console] Fix bug with inline autocompletion (#210187) (#210992)
# Backport This will backport the following commits from `main` to `9.0`: - [[Console] Fix bug with inline autocompletion (#210187)](https://github.com/elastic/kibana/pull/210187) <!--- 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-13T12:15:22Z","message":"[Console] Fix bug with inline autocompletion (#210187)","sha":"baadf59aa2107ec34e16448a316d7ad144acac7c","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","backport:prev-minor","v9.1.0","v8.19.0"],"title":"[Console] Fix bug with inline autocompletion","number":210187,"url":"https://github.com/elastic/kibana/pull/210187","mergeCommit":{"message":"[Console] Fix bug with inline autocompletion (#210187)","sha":"baadf59aa2107ec34e16448a316d7ad144acac7c"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/210187","number":210187,"mergeCommit":{"message":"[Console] Fix bug with inline autocompletion (#210187)","sha":"baadf59aa2107ec34e16448a316d7ad144acac7c"}},{"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
|
3f49fd963f
|
[9.0] [Discover] Fix formatting and sorting for custom ES|QL vars (#209360) (#210519)
# Backport This will backport the following commits from `main` to `9.0`: - [[Discover] Fix formatting and sorting for custom ES|QL vars (#209360)](https://github.com/elastic/kibana/pull/209360) <!--- 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-11T09:58:51Z","message":"[Discover] Fix formatting and sorting for custom ES|QL vars (#209360)\n\n- Closes https://github.com/elastic/kibana/issues/208020\r\n\r\n## Summary\r\n\r\nBy default the data view (which is used in ES|QL mode) has only mapped\r\nfields as per field caps for the current index pattern. This PR\r\ndynamically extends with additional fields based on ES|QL meta\r\ninformation.\r\n\r\nThis change helps to fix the formatting for ES|QL var values and fixes\r\nsorting on them.\r\n\r\n<img width=\"1673\" alt=\"Screenshot 2025-02-03 at 18 42 14\"\r\nsrc=\"https://github.com/user-attachments/assets/3647a375-f0f5-43e6-815d-d5a4292c637a\"\r\n/>\r\n<img width=\"643\" alt=\"Screenshot 2025-02-03 at 18 42 50\"\r\nsrc=\"https://github.com/user-attachments/assets/9d84bc23-7665-43c1-8ac2-d67174b68c31\"\r\n/>\r\n\r\n\r\n### Checklist\r\n\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: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>","sha":"9635cfa5268c6250111f8eb5edcd693311a47193","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","Team:DataDiscovery","Feature:ES|QL","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Discover] Fix formatting and sorting for custom ES|QL vars","number":209360,"url":"https://github.com/elastic/kibana/pull/209360","mergeCommit":{"message":"[Discover] Fix formatting and sorting for custom ES|QL vars (#209360)\n\n- Closes https://github.com/elastic/kibana/issues/208020\r\n\r\n## Summary\r\n\r\nBy default the data view (which is used in ES|QL mode) has only mapped\r\nfields as per field caps for the current index pattern. This PR\r\ndynamically extends with additional fields based on ES|QL meta\r\ninformation.\r\n\r\nThis change helps to fix the formatting for ES|QL var values and fixes\r\nsorting on them.\r\n\r\n<img width=\"1673\" alt=\"Screenshot 2025-02-03 at 18 42 14\"\r\nsrc=\"https://github.com/user-attachments/assets/3647a375-f0f5-43e6-815d-d5a4292c637a\"\r\n/>\r\n<img width=\"643\" alt=\"Screenshot 2025-02-03 at 18 42 50\"\r\nsrc=\"https://github.com/user-attachments/assets/9d84bc23-7665-43c1-8ac2-d67174b68c31\"\r\n/>\r\n\r\n\r\n### Checklist\r\n\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: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>","sha":"9635cfa5268c6250111f8eb5edcd693311a47193"}},"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/209360","number":209360,"mergeCommit":{"message":"[Discover] Fix formatting and sorting for custom ES|QL vars (#209360)\n\n- Closes https://github.com/elastic/kibana/issues/208020\r\n\r\n## Summary\r\n\r\nBy default the data view (which is used in ES|QL mode) has only mapped\r\nfields as per field caps for the current index pattern. This PR\r\ndynamically extends with additional fields based on ES|QL meta\r\ninformation.\r\n\r\nThis change helps to fix the formatting for ES|QL var values and fixes\r\nsorting on them.\r\n\r\n<img width=\"1673\" alt=\"Screenshot 2025-02-03 at 18 42 14\"\r\nsrc=\"https://github.com/user-attachments/assets/3647a375-f0f5-43e6-815d-d5a4292c637a\"\r\n/>\r\n<img width=\"643\" alt=\"Screenshot 2025-02-03 at 18 42 50\"\r\nsrc=\"https://github.com/user-attachments/assets/9d84bc23-7665-43c1-8ac2-d67174b68c31\"\r\n/>\r\n\r\n\r\n### Checklist\r\n\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: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>","sha":"9635cfa5268c6250111f8eb5edcd693311a47193"}},{"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
|
63c3a6ded8
|
[9.0] [Discover] Add "All logs" data view to classic nav (#209042) (#210485)
# Backport This will backport the following commits from `main` to `9.0`: - [[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
|
f8094be915
|
[9.0] Remove dependency date-fns !! (#209539) (#209829)
# Backport This will backport the following commits from `main` to `9.0`: - [Remove dependency date-fns !! (#209539)](https://github.com/elastic/kibana/pull/209539) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Shahzad","email":"shahzad31comp@gmail.com"},"sourceCommit":{"committedDate":"2025-02-05T16:34:16Z","message":"Remove dependency date-fns !! (#209539)\n\n## Summary\r\n\r\nWhat's better than upgrade? removing it alltogther !!","sha":"679e2badafcf773024e37b3901bc8c241de41e85","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","v9.1.0"],"title":"Remove dependency date-fns !!","number":209539,"url":"https://github.com/elastic/kibana/pull/209539","mergeCommit":{"message":"Remove dependency date-fns !! (#209539)\n\n## Summary\r\n\r\nWhat's better than upgrade? removing it alltogther !!","sha":"679e2badafcf773024e37b3901bc8c241de41e85"}},"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/209539","number":209539,"mergeCommit":{"message":"Remove dependency date-fns !! (#209539)\n\n## Summary\r\n\r\nWhat's better than upgrade? removing it alltogther !!","sha":"679e2badafcf773024e37b3901bc8c241de41e85"}}]}] BACKPORT--> Co-authored-by: Shahzad <shahzad31comp@gmail.com> |
||
|
Kibana Machine
|
f439055195
|
[9.0] [Console] Refactor flaky test (#209516) (#209730)
# Backport This will backport the following commits from `main` to `9.0`: - [[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
|
5ef47d4c86
|
[9.0] [Discover] Unskip Edit field flyout tests (#209271) (#209607)
# Backport This will backport the following commits from `main` to `9.0`: - [[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> |
||
Rodney Norris
|
e6a47de012
|
[9.0] [Search][Configuration] Remove Enterprise Search node values (#208856) (#209147)
# Backport This will backport the following commits from `main` to `9.0`: - [[Search][Configuration] Remove Enterprise Search node values (#208856)](https://github.com/elastic/kibana/pull/208856) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Rodney Norris","email":"rodney.norris@elastic.co"},"sourceCommit":{"committedDate":"2025-01-30T19:28:26Z","message":"[Search][Configuration] Remove Enterprise Search node values (#208856)\n\n## Summary\r\n\r\nThis removes the config values associated with the enterprise search\r\nnode.\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- [x] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)","sha":"26fac70c9b82d65de1b93acf6be4d28503fb9f6a","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:version","v9.1.0"],"title":"[Search][Configuration] Remove Enterprise Search node values","number":208856,"url":"https://github.com/elastic/kibana/pull/208856","mergeCommit":{"message":"[Search][Configuration] Remove Enterprise Search node values (#208856)\n\n## Summary\r\n\r\nThis removes the config values associated with the enterprise search\r\nnode.\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- [x] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)","sha":"26fac70c9b82d65de1b93acf6be4d28503fb9f6a"}},"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/208856","number":208856,"mergeCommit":{"message":"[Search][Configuration] Remove Enterprise Search node values (#208856)\n\n## Summary\r\n\r\nThis removes the config values associated with the enterprise search\r\nnode.\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- [x] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)","sha":"26fac70c9b82d65de1b93acf6be4d28503fb9f6a"}},{"branch":"9.1","label":"v9.1.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
e061252f1e
|
skip failing test suite (#193102) | ||
Nathan Reese
|
29c42287d8
|
[9.0] [dashboard] remove legacy section from 'Add panel' flyout (#208116) (#209015)
# Backport This will backport the following commits from `main` to `9.0`: - [[dashboard] remove legacy section from 'Add panel' flyout (#208116)](https://github.com/elastic/kibana/pull/208116) <!--- 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-30T19:22:51Z","message":"[dashboard] remove legacy section from 'Add panel' flyout (#208116)\n\nUsers should use Lens to visualize data. Users should not use TSVB or\r\naggregation based panels. To this end, \"easy button\" UIs, such as\r\ndashboard's \"Add panel\" flyout, should guide users to lens and not guide\r\nthem to legacy applications.\r\n\r\nThis PR removes `legacy` section from dashboard \"Add panel\" flyout.\r\nUsers can still add legacy panels to dashboards via \"visualize\"\r\napplication. The path is more steps, but this is as intended. Using old\r\nstuff should be painful and require extra work as a caret to move users\r\nto new stuff.\r\n\r\n<img width=\"500\" alt=\"Screenshot 2025-01-23 at 1 08 41 PM\"\r\nsrc=\"https://github.com/user-attachments/assets/e142cba9-a880-4ad6-a3f8-a981a03daaec\"\r\n/>\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"758768136d58815b282d3f0bb2eb11b9b33d7989","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","v9.0.0","backport:version","v9.1.0","v8.19.0"],"title":"[dashboard] remove legacy section from 'Add panel' flyout","number":208116,"url":"https://github.com/elastic/kibana/pull/208116","mergeCommit":{"message":"[dashboard] remove legacy section from 'Add panel' flyout (#208116)\n\nUsers should use Lens to visualize data. Users should not use TSVB or\r\naggregation based panels. To this end, \"easy button\" UIs, such as\r\ndashboard's \"Add panel\" flyout, should guide users to lens and not guide\r\nthem to legacy applications.\r\n\r\nThis PR removes `legacy` section from dashboard \"Add panel\" flyout.\r\nUsers can still add legacy panels to dashboards via \"visualize\"\r\napplication. The path is more steps, but this is as intended. Using old\r\nstuff should be painful and require extra work as a caret to move users\r\nto new stuff.\r\n\r\n<img width=\"500\" alt=\"Screenshot 2025-01-23 at 1 08 41 PM\"\r\nsrc=\"https://github.com/user-attachments/assets/e142cba9-a880-4ad6-a3f8-a981a03daaec\"\r\n/>\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"758768136d58815b282d3f0bb2eb11b9b33d7989"}},"sourceBranch":"main","suggestedTargetBranches":["9.1","8.19"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/208116","number":208116,"mergeCommit":{"message":"[dashboard] remove legacy section from 'Add panel' flyout (#208116)\n\nUsers should use Lens to visualize data. Users should not use TSVB or\r\naggregation based panels. To this end, \"easy button\" UIs, such as\r\ndashboard's \"Add panel\" flyout, should guide users to lens and not guide\r\nthem to legacy applications.\r\n\r\nThis PR removes `legacy` section from dashboard \"Add panel\" flyout.\r\nUsers can still add legacy panels to dashboards via \"visualize\"\r\napplication. The path is more steps, but this is as intended. Using old\r\nstuff should be painful and require extra work as a caret to move users\r\nto new stuff.\r\n\r\n<img width=\"500\" alt=\"Screenshot 2025-01-23 at 1 08 41 PM\"\r\nsrc=\"https://github.com/user-attachments/assets/e142cba9-a880-4ad6-a3f8-a981a03daaec\"\r\n/>\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"758768136d58815b282d3f0bb2eb11b9b33d7989"}},{"branch":"9.1","label":"v9.1.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
Ania Kowalska
|
a376e9b169
|
refactor RowHeightSettings component to EUI layout (#203606) | ||
Julia Rechkunova
|
8ffb2ff628
|
[Discover] In-table search (#206454)
- Closes https://github.com/elastic/kibana/issues/192360 ## Summary The default browser Find-in-page does not work great with the grid virtualization and our pagination and it can only find matches in rows which are currently displayed. This PR adds in-table search support to the grid so users can find matches in all grid rows (up to `500` sample docs/rows by default) and jump between them with "Previous"/"Next" buttons.  The implementation is extracted in a new package `@kbn/data-grid-in-table-search`. This would allow to use in-table search with `EuiDataGrid` on other pages of Kibana too. `Cmd+F` shortcut is overridden when one of grid elements is in focus otherwise we keep the browser default behaviour. ### 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/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [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) --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: florent-leborgne <florent.leborgne@elastic.co> |
||
|
Davis McPhee
|
b53d3990a2
|
[Saved Queries] Rework saved query privileges (#202863)
## Summary This PR reworks saved query privileges to rely solely on a single global `savedQueryManagement` privilege, and eliminates app-specific overrides. This change simplifies the security model for users, fixes bugginess in the saved query management UI, and reduces code complexity associated with maintaining two separate security mechanisms (app-specific overrides and global saved query management privileges). ### Background Saved queries allow users to store a combination of KQL or Lucene queries, filters, and time filters to use across various applications in Kibana. Access to saved query saved objects are currently granted by the following feature privileges: ```json [ "feature_discover.all", "feature_dashboard.all", "feature_savedQueryManagement.all", "feature_maps.all", "feature_savedObjectsManagement.all", "feature_visualize.all" ] ``` There is also a saved query management UI within the Unified Search bar shared by applications across Kibana: <img src="https://github.com/user-attachments/assets/e4a7539b-3dd4-4d47-9ff8-205281ef50e3" width="500" /> The way access to this UI is managed in Kibana is currently confusing and buggy: - If a user has `feature_discover.all` and `feature_dashboard.all` they will be able to load and save queries in Discover and Dashboard. - If a user has `feature_discover.all` and `feature_dashboard.read` they will be able to load queries in both Discover and Dashboard, but only save queries in Discover (even though they have write access to the SO, and API access). Instead they have to navigate to Discover to save a query before navigating back to Dashboard to load it, making for a confusing and frustrating UX. - Access to the UI is even more confusing in apps not listed in the above feature privileges (e.g. alerting, SLOs). Some of them chose to check one of the above feature privileges, meaning users who otherwise should have saved query access won't see the management UI if they don't also have the exact feature privilege being checked. Other apps just always show the management UI, leading to bugs and failures when users without one of the above feature privileges attempt to save queries. ### Existing improvements In v8.11.0, we introduced a new ["Saved Query Management"](https://github.com/elastic/kibana/pull/166937) privilege, allowing users to access saved queries across all of Kibana with a single global privilege: <img src="https://github.com/user-attachments/assets/ccbe79a4-bd0b-4ed6-89c9-117cc1f99ee2" width="600" /> When this privilege is added to a role, it solves the `feature_discover.all` and `feature_dashboard.read` issue mentioned above. However, it does not fix any of the mentioned issues for roles without the new privilege. We have so far postponed further improvements to avoid a breaking change. ### Approach To fully resolve these issues and migrate to a single global privilege, these changes have been made: - Remove saved query SO access from all application feature privileges and instead only allow access through the global saved query management privilege. - Stop relying on application feature privileges for toggling the saved query management UI, and instead rely on the global privilege. To implement this with minimal breaking changes, we've used the Kibana privilege migration framework. This allows us to seamlessly migrate existing roles containing feature privileges that currently provide access to saved queries, ensuring they are assigned the global saved query management privilege on upgrade. As a result, we had to deprecate the following feature privileges, replacing them with V2 privileges without saved query SO access: ```json [ "feature_discover.all", "feature_dashboard.all", "feature_maps.all", "feature_visualize.all" ] ``` Each area of code that currently relies on any of these feature privileges had to be updated to instead access `feature_X_V2` instead (as well as future code). This PR still introduces a minor breaking change, since users who have `feature_discover.all` and `feature_dashboard.read` are now able to save queries in Dashboard after upgrade, but we believe this is a better UX (and likely the expected one) and worth a small breaking change. ### Testing - All existing privileges should continue to work as they do now, including deprecated V1 feature privileges and customized serverless privileges. There should be no changes for existing user roles apart from the minor breaking change outlined above. - Check that code changes in your area don't introduce breaking changes to existing behaviour. Many of the changes are just updating client UI capabilities code from `feature.privilege` to `feature_v2.privilege`, which is backward compatible. - The `savedQueryManagement` feature should now globally control access to saved query management in Unified Search for all new user roles. Regardless of privileges for Discover, Dashboard, Maps, or Visualize, new user roles should follow this behaviour: - If `savedQueryManagement` is `none`, the user cannot see or access the saved query management UI or APIs. - If `savedQueryManagement` is `read`, the user can load queries from the UI and access read APIs, but cannot save queries from the UI or make changes to queries through APIs. - If `savedQueryManagement` is `all`, the user can both load and save queries from the UI and through APIs. ### 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) - [x] 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) ### Identify risks This PR risks introducing unintended breaking changes to user privileges related to saved queries if the deprecated features have not been properly migrated, and users could gain or lose access to saved query management on upgrade. This would be bad if it happened, but not overly severe since it wouldn't grant them access to any ES data they couldn't previously access (only query saved objects). We have automated testing in place to help ensure features have been migrated correctly, but the scope of these changes are broad and touch many places in the codebase. Additionally, the UI capabilities types are not very strict, and are referenced with string paths in many places, which makes changing them riskier than changing strictly typed code. A combination of regex searches and temporarily modifying the `Capabilities` type to cause type errors for deprecated privileges was used to identify references in code. Reviewers should consider if there are any other ways that UI capabilities can be referenced which were not addressed in this PR. Our automated tests already help mitigate the risk, but it's important that code owners thoroughly review the changes in their area and consider if they could have unintended consequences. The Platform Security team should also review this PR thoroughly, especially since some changes were made to platform code around privilege handling. The Data Discovery team will also manually test the behaviour when upgrading existing user roles with deprecated feature privileges as part of 9.0 upgrade testing. --------- Co-authored-by: Matthias Wilhelm <matthias.wilhelm@elastic.co> Co-authored-by: Matthias Wilhelm <ankertal@gmail.com> Co-authored-by: Aleh Zasypkin <aleh.zasypkin@gmail.com> Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: “jeramysoucy” <jeramy.soucy@elastic.co> |
||
|
Davis McPhee
|
bf9d34465e
|
[Discover] Add a default "All logs" temporary data view in the Observability Solution view (#205991)
## Summary This PR adds an "All logs" ad hoc (temporary) data view to the Discover Observability root profile based on the central log sources setting, allowing quick access to logs (with the most up to date log sources) without needing to first manually create a data view:  To support this, a new `getDefaultAdHocDataViews` extension point has been added to Discover, allowing profiles to specify an array of ad hoc data view specs would should be created by default when the profile is resolved, and automatically cleaned up when the profile changes or the user leaves Discover. Resolves #201669. Resolves #189166. ### Notes - The "All logs" ad hoc data view should only appear when using the Observability Solution view (in any deployment type). - Data view specs returned from `getDefaultAdHocDataViews` must include consistent IDs across resolutions in order for Discover to manage them correctly (e.g. to find and reload the data view after a page refresh). Situations where we'd expect a change in ID (e.g. when saving to a Discover session) are handled internally by Discover. - To avoid a breaking change, the returned ad hoc data views have no impact on the default data view shown when navigating to Discover. If any persisted data views exist, one of them will be used as the default. If no persisted data views exist, the first entry of the array returned by `getDefaultAdHocDataViews` will be used as the default. - We still want to notify users in Discover when they have no ES data at all, and prompt them to install integrations. For this reason, the "no data" page is still shown in Discover even if there are default profile ad hoc data views (unlike if there are persisted data views, in which case we use the default and hide the "no data" page). - When saving a Discover session that uses a default profile ad hoc data view, the data view will be copied on save as `{DATA_VIEW_NAME} (copy)`. This allows us to assign a unique ID to the version that gets saved with the Discover session, and avoids having to choose between the profile data view or the embedded data view when reopening the session, which has drawbacks: - If choosing the profile data view, the Discover session may display incorrectly if the log sources setting changed since it was saved, and the user would no longer be able to view the session as it was intended without first modifying the setting to the expected value. - If choosing the embedded data view, the replacement shown after opening the Discover session may not reflect the latest log sources setting until a new session is started, and there would be no way for the user to migrate the session to use the latest version of the profile data view. ### 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/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [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. - [x] [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) |
||
Ignacio Rivas
|
4da814d138
|
[Console] Fix flaky autocomplete test for index fields (#208503) | ||
Sonia Sanz Vivas
|
20ed84d41d
|
Fix flaky console tests (#208337)
Fixes https://github.com/elastic/kibana/issues/204381 ## Summary The test that verifies tab changes in Console was failing because it was verifying the presence of the tab content before it was fully loaded. ### Checklist - [x] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> |
||
Larry Gregory
|
9ce2dd8df9
|
Additional prototype pollution protections (#206073)
## Summary 1. Extends the server-side prototype pollution protections introduced in https://github.com/elastic/kibana/pull/190716 to include `Array.prototype`. 2. Applies the same prototype pollution protections to the client-side. ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] Sealing prototypes on the client can lead to failures in third-party dependencies. I'm relying on sufficient functional test coverage to detect issues here. As a result, these protections are disabled by default for now, and can be controlled via setting `server.prototypeHardening: true/false` --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> |