[Canvas] Apply embeddable transforms to embeddable elements by cqliu1 · Pull Request #252191 · elastic/kibana

cqliu1 · 2026-02-07T00:57:30Z

Summary

This passes expressions using the embeddable function through their respective embeddable transforms as part of the Canvas REST API. This also removes the injectReferences and extractReferences in favor of the embeddable transforms. Passing the embeddable configs through their respective transforms is essential for making sure the embeddable object is the correct shape and has the correct references.

Checklist

Check the PR satisfies following conditions.

Reviewers should verify this PR satisfies this list as well.

Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
Documentation was added for features that require explanation or tutorials
Unit or functional tests 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
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 was used on any tests changed
The PR description includes the appropriate Release Notes section, and the correct release_note:* label is applied per the guidelines
Review the backport guidelines and apply applicable backport:* labels.

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.

See some risk examples
...

elasticmachine · 2026-02-12T00:26:17Z

Pinging @elastic/kibana-presentation (Team:Presentation)

Add unit tests for transformWorkpadIn and transformWorkpadOut Remove expressions dep on workpad route context Fix tests Remove console log Changes from node scripts/eslint_all_files --no-cache --fix Fix transformWorkpadOut test Remove unused import Changes from node scripts/eslint_all_files --no-cache --fix Remove comments Remove extract and inject from embeddable functions in favor of transforms Fix reference names and handle legacy expressions Fix embeddable migrations Changes from node scripts/jest_integration -u src/core/server/integration_tests/ci_checks Fix references for legacy embeddable functions Changes from node scripts/jest_integration -u src/core/server/integration_tests/ci_checks Changes from node scripts/eslint_all_files --no-cache --fix Update comments Clean up tests Fix tests Update constant Changes from node scripts/eslint_all_files --no-cache --fix Add error handling for transform_workpad_in

x-pack/platform/plugins/private/canvas/server/embeddable/get_references_for_element.ts

…encesForElement

nreese

LGTM with required changes in x-pack/platform/plugins/private/canvas/server/embeddable/transform_workpad_in.ts
code review and tested in chrome

nreese · 2026-03-10T19:43:12Z

x-pack/platform/plugins/private/canvas/server/embeddable/transform_references_out.test.ts

+      ]);
+    });
+  });
+  describe('savedLens function', () => {


This entire describe block can be deleted. Duplicative test cases from "embeddable functions" test block.There is no difference between "embeddable" and "savedLens" expression as far as transformPanelReferencesOut is concerned.

Removed in da36ddb

nreese · 2026-03-10T19:48:29Z

x-pack/platform/plugins/private/canvas/server/embeddable/transform_workpad_in.ts

+      ast.chain = ast.chain.map((fn) => {
+        if (fn.function === 'embeddable') {
+          const embeddableConfig = decode(fn.arguments.config[0] as string);
+          const embeddableType = fn.arguments.type[0] as string;


Need to do the same work around for lens here

const embeddableType = fn.arguments.type[0] as string; // Temporary escape hatch for lens as code // TODO remove when lens as code transforms are ready for production const transformType = embeddableType === 'lens' ? 'lens-dashboard-app' : embeddableType; const transforms = embeddableService.getTransforms(transformType);

Addressed in f82191f.

…apply-embeddable-transforms

elasticmachine · 2026-03-10T22:46:26Z

⏳ Build in-progress, with failures

Buildkite Build
Commit: a9238bf

Failed CI Steps

Test Failures

[job] [logs] Scout: [ security / entity_store ] plugin / local-stateful-classic - Entity Store CCS logs extraction (test against local instance) - Should run CCS extraction for generic and write to updates then latest index
[job] [logs] Scout: [ security / entity_store ] plugin / local-stateful-classic - Entity Store CCS logs extraction (test against local instance) - Should run CCS extraction for generic and write to updates then latest index
[job] [logs] Scout: [ security / entity_store ] plugin / local-stateful-classic - Entity Store CCS logs extraction (test against local instance) - Should run CCS extraction for host and write to updates then latest index
[job] [logs] Scout: [ security / entity_store ] plugin / local-stateful-classic - Entity Store CCS logs extraction (test against local instance) - Should run CCS extraction for host and write to updates then latest index
[job] [logs] Scout: [ security / entity_store ] plugin / local-stateful-classic - Entity Store CCS logs extraction (test against local instance) - Should run CCS extraction for service and write to updates then latest index
[job] [logs] Scout: [ security / entity_store ] plugin / local-stateful-classic - Entity Store CCS logs extraction (test against local instance) - Should run CCS extraction for service and write to updates then latest index
[job] [logs] Scout: [ security / entity_store ] plugin / local-stateful-classic - Entity Store CCS logs extraction (test against local instance) - Should run CCS extraction for user and write to updates then latest index
[job] [logs] Scout: [ security / entity_store ] plugin / local-stateful-classic - Entity Store CCS logs extraction (test against local instance) - Should run CCS extraction for user and write to updates then latest index

History

…apply-embeddable-transforms

kibanamachine · 2026-03-11T00:11:30Z

Starting backport for target branches: 9.2, 9.3

https://github.com/elastic/kibana/actions/runs/22930172197

…252191) ## Summary Closes elastic#251762. This passes expressions using the `embeddable` function through their respective embeddable transforms as part of the Canvas REST API. This also removes the `injectReferences` and `extractReferences` in favor of the embeddable transforms. Passing the embeddable configs through their respective transforms is essential for making sure the embeddable object is the correct shape and has the correct references. ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] 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 - [ ] [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 - [ ] 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) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### 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. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> (cherry picked from commit f4c092e)

kibanamachine · 2026-03-11T00:19:44Z

💚 All backports created successfully

Status	Branch	Result
✅	9.2
✅	9.3

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation

…52191) (#257013) # Backport This will backport the following commits from `main` to `9.3`: - [[Canvas] Apply embeddable transforms to embeddable elements (#252191)](#252191)  ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport)  Co-authored-by: Catherine Liu <catherine.liu@elastic.co>

…52191) (#257012) # Backport This will backport the following commits from `main` to `9.2`: - [[Canvas] Apply embeddable transforms to embeddable elements (#252191)](#252191)  ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport)  Co-authored-by: Catherine Liu <catherine.liu@elastic.co>

…e_fix * commit '565f7545c422192218b803874fbdf93e8d8f08ee': (27 commits) [Lens API] ESQL schema for XY separately for Agent and some small token optimizations (elastic#256885) Fix "Accessing resource attributes before async attributes settled" telemetry error (elastic#256880) [Security Solution][Attacks/Alerts][Attacks page][Table section] Preserver "Sort by" state on Attacks page (elastic#256717) (elastic#256795) [APM] Improve redirect with default date range guard (elastic#256887) [Security Solution][Attacks/Alerts][Attacks page][Table section] Add assignees avatars to the group component (elastic#250126) (elastic#256901) [Docs] add xpack.alerting.rules.maxScheduledPerMinute setting description (elastic#257041) [SO] Fix non-deterministic ordering in nested find API integration tests (elastic#256447) [Write-restricted dashboards] Update user profile retrieval for getShouldAddAccessControl (elastic#255065) [One Workflow] Add Scout API test scaffold and execution tests (elastic#256300) [Fleet] add use_apm if dynamic_signal_types are enabled (elastic#256429) [Fleet] ignore data streams starting with `.` in Fleet API (elastic#256625) [ES|QL] METRICS_INFO support: columns_after & summary (elastic#256758) [Agent Builder] Agent plugins: initial installation support (elastic#256478) [Streams] Add field descriptions and documentation-only field overrides (elastic#255136) [api-docs] 2026-03-11 Daily api_docs build (elastic#257023) [Security Solution] fix alerts page infinite loading state due to data view error (elastic#256983) [Logging] Add `service.*` global fields (elastic#256878) [Canvas] Apply embeddable transforms to embeddable elements (elastic#252191) [table_list_view_table] stabilize jest test (elastic#254991) [Obs AI] get_index_info: add unit tests (elastic#256802) ...

## Summary Follow up to #252191. This PR targets 9.3. This replaces mention of the `lens-dashboard-app` temporary lens transforms introduced in 9.4 and accesses the correct `lens` transforms. ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] 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 - [ ] [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 - [ ] 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) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### 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. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ...

## Summary Closes #257291. Follow up to #252191 where we automatically convert legacy `savedLens`, `savedVisualizations`, and `savedMap` expressions into generic `embeddable` expressions. This PR removes `savedLens`, `savedVisualizations`, `savedMap`, and `savedSearch` functions and any related code. Note: The `savedSearch` function was created but never exposed to the user, so no migration is necessary for `savedSearch`, and it can be safely removed. ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] 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 - [ ] [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 - [ ] 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) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### 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. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>

## Summary Closes #251762. This passes expressions using the `embeddable` function through their respective embeddable transforms as part of the Canvas REST API. This also removes the `injectReferences` and `extractReferences` in favor of the embeddable transforms. Passing the embeddable configs through their respective transforms is essential for making sure the embeddable object is the correct shape and has the correct references. ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] 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 - [ ] [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 - [ ] 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) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### 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. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>

## Summary Closes #257291. Follow up to #252191 where we automatically convert legacy `savedLens`, `savedVisualizations`, and `savedMap` expressions into generic `embeddable` expressions. This PR removes `savedLens`, `savedVisualizations`, `savedMap`, and `savedSearch` functions and any related code. Note: The `savedSearch` function was created but never exposed to the user, so no migration is necessary for `savedSearch`, and it can be safely removed. ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] 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 - [ ] [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 - [ ] 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) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### 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. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>

## Summary Follow up to elastic#252191. This PR targets 9.3. This replaces mention of the `lens-dashboard-app` temporary lens transforms introduced in 9.4 and accesses the correct `lens` transforms. ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] 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 - [ ] [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 - [ ] 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) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### 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. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... (cherry picked from commit 28bd0d1)

## Summary Closes elastic#257291. Follow up to elastic#252191 where we automatically convert legacy `savedLens`, `savedVisualizations`, and `savedMap` expressions into generic `embeddable` expressions. This PR removes `savedLens`, `savedVisualizations`, `savedMap`, and `savedSearch` functions and any related code. Note: The `savedSearch` function was created but never exposed to the user, so no migration is necessary for `savedSearch`, and it can be safely removed. ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] 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 - [ ] [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 - [ ] 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) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### 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. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>

cqliu1 added Team:Presentation Presentation Team for Dashboard, Input Controls, and Canvas t// loe:medium Medium Level of Effort impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. v9.4.0 Feature:Canvas labels Feb 7, 2026

cqliu1 force-pushed the canvas/apply-embeddable-transforms branch 2 times, most recently from 1b37fb1 to c2cda93 Compare February 11, 2026 21:09

cqliu1 marked this pull request as ready for review February 12, 2026 00:26

cqliu1 requested a review from a team as a code owner February 12, 2026 00:26

cqliu1 added release_note:fix backport:skip This PR does not require backporting labels Feb 12, 2026

ThomThomson self-requested a review February 12, 2026 21:23

cqliu1 force-pushed the canvas/apply-embeddable-transforms branch from b32aa1d to bc77b6e Compare February 13, 2026 03:42

cqliu1 requested a review from a team as a code owner March 2, 2026 19:31

cqliu1 force-pushed the canvas/apply-embeddable-transforms branch from 81685b2 to 8648790 Compare March 2, 2026 20:12

cqliu1 removed the request for review from a team March 2, 2026 20:28

cqliu1 force-pushed the canvas/apply-embeddable-transforms branch from 1af62d2 to dedf145 Compare March 3, 2026 00:14

cqliu1 added loe:large Large Level of Effort v9.3.2 backport:version Backport to applied version labels and removed loe:medium Medium Level of Effort backport:skip This PR does not require backporting labels Mar 3, 2026

cqliu1 added 7 commits March 3, 2026 17:06

Fix import

1c8fb44

Fix tests

cc08eda

Fix workpad route context tests

4421856

Fix tests

8ce2fbf

Fix more tests

536b78c

Fix savedMap test

24481aa

cqliu1 added 3 commits March 10, 2026 11:38

Fixed transform panel references out

9b3d2cd

Add getReferenceForElement helper and tests

e41f418

Update test

de1ca58

nreese reviewed Mar 10, 2026

View reviewed changes

x-pack/platform/plugins/private/canvas/server/embeddable/get_references_for_element.ts Show resolved Hide resolved

Remove link index prefix from transformPanelReferencesOut to getRefer…

f49276e

…encesForElement

nreese approved these changes Mar 10, 2026

View reviewed changes

cqliu1 added 3 commits March 10, 2026 13:11

Add temporary lens-dashboard-app transform type to transformWorkpadIn

f82191f

Remove extraneous tests

da36ddb

Merge branch 'main' of https://github.com/elastic/kibana into canvas/…

a9238bf

…apply-embeddable-transforms

Merge branch 'main' of https://github.com/elastic/kibana into canvas/…

0c29b76

…apply-embeddable-transforms

cqliu1 merged commit f4c092e into elastic:main Mar 11, 2026
18 checks passed

kibanamachine mentioned this pull request Mar 11, 2026

[9.2] [Canvas] Apply embeddable transforms to embeddable elements (#252191) #257012

Merged

kibanamachine mentioned this pull request Mar 11, 2026

[9.3] [Canvas] Apply embeddable transforms to embeddable elements (#252191) #257013

Merged

cqliu1 mentioned this pull request Mar 11, 2026

[9.3][Canvas] Fix lens transforms #257224

Merged

10 tasks

This was referenced Mar 11, 2026

[Canvas] Remove legacy embeddable functions #257291

Closed

[Canvas] Remove legacy embeddable functions #257294

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[Canvas] Apply embeddable transforms to embeddable elements#252191

[Canvas] Apply embeddable transforms to embeddable elements#252191
cqliu1 merged 43 commits intoelastic:mainfrom
cqliu1:canvas/apply-embeddable-transforms

cqliu1 commented Feb 7, 2026 •

edited by kibanamachine

Loading

Uh oh!

elasticmachine commented Feb 12, 2026

Uh oh!

Uh oh!

nreese left a comment

Uh oh!

nreese Mar 10, 2026

Uh oh!

cqliu1 Mar 10, 2026 •

edited

Loading

Uh oh!

nreese Mar 10, 2026

Uh oh!

cqliu1 Mar 10, 2026

Uh oh!

elasticmachine commented Mar 10, 2026

Uh oh!

Uh oh!

kibanamachine commented Mar 11, 2026

Uh oh!

kibanamachine commented Mar 11, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Conversation

cqliu1 commented Feb 7, 2026 • edited by kibanamachine Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Checklist

Identify risks

Uh oh!

elasticmachine commented Feb 12, 2026

Uh oh!

Uh oh!

nreese left a comment

Choose a reason for hiding this comment

Uh oh!

nreese Mar 10, 2026

Choose a reason for hiding this comment

Uh oh!

cqliu1 Mar 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

nreese Mar 10, 2026

Choose a reason for hiding this comment

Uh oh!

cqliu1 Mar 10, 2026

Choose a reason for hiding this comment

Uh oh!

elasticmachine commented Mar 10, 2026

⏳ Build in-progress, with failures

Failed CI Steps

Test Failures

History

Uh oh!

Uh oh!

kibanamachine commented Mar 11, 2026

Uh oh!

kibanamachine commented Mar 11, 2026

💚 All backports created successfully

Questions ?

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

cqliu1 commented Feb 7, 2026 •

edited by kibanamachine

Loading

cqliu1 Mar 10, 2026 •

edited

Loading