Skip to content

[ML] Fixes broken Data Visualizer & AIOps navigation breadcrumbs / sidebar in solutions#248167

Merged
qn895 merged 19 commits intoelastic:mainfrom
qn895:fix-sidebar-nav
Jan 21, 2026
Merged

[ML] Fixes broken Data Visualizer & AIOps navigation breadcrumbs / sidebar in solutions#248167
qn895 merged 19 commits intoelastic:mainfrom
qn895:fix-sidebar-nav

Conversation

@qn895
Copy link
Member

@qn895 qn895 commented Jan 7, 2026 •
edited by kibanamachine
Loading

Summary

This PR addresses #245826. For reviewers, these are small changes with the sidebar to make the sure the names are consistent.

After:

Screen.Recording.2026-01-07.at.13.17.16.mov

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.
@qn895 qn895 self-assigned this Jan 7, 2026
@qn895
Copy link
Member Author

qn895 commented Jan 7, 2026

/ci
@qn895 qn895 marked this pull request as ready for review January 7, 2026 22:10
@qn895 qn895 requested review from a team as code owners January 7, 2026 22:10
@qn895 qn895 added bug Fixes for quality problems that affect the customer experience release_note:fix :ml backport:version Backport to applied version labels v9.3.0 labels Jan 7, 2026
@elasticmachine
Copy link
Contributor

elasticmachine commented Jan 7, 2026

Pinging @elastic/ml-ui (:ml)
@peteharverson peteharverson self-requested a review January 8, 2026 14:40
peteharverson
peteharverson reviewed Jan 8, 2026
View reviewed changes
@elasticmachine
Copy link
Contributor

elasticmachine commented Jan 8, 2026

Pinging @elastic/obs-ux-management-team (Team:obs-ux-management)
@github-actions
Copy link
Contributor

github-actions bot commented Jan 8, 2026

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

  • /oblt-deploy : Deploy a Kibana instance using the Observability test environments.
  • run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)
peteharverson
peteharverson reviewed Jan 9, 2026
View reviewed changes
@qn895 qn895 requested a review from a team as a code owner January 9, 2026 16:53
@elastic-vault-github-plugin-prod elastic-vault-github-plugin-prod bot requested a review from a team as a code owner January 14, 2026 22:56
@qn895
Copy link
Member Author

qn895 commented Jan 15, 2026

@elasticmachine merge upstream
@qn895 qn895 removed the request for review from a team January 15, 2026 14:58
benakansara
benakansara approved these changes Jan 15, 2026
View reviewed changes
Copy link
Contributor

@benakansara benakansara left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

actionable-obs changes LGTM
ashokaditya
ashokaditya approved these changes Jan 16, 2026
View reviewed changes
Copy link
Member

@ashokaditya ashokaditya left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the fix! I tested this out for oblt solutions nav and the breadcrumbs work as expected! 🚢 it!

However, I noticed that the classic oblt nav is jumpy on initial load. Looks like this is already present on main. I thought I'll mention it here. Here's a clip that shows loading of classic nav for security vs oblt.

Image
@qn895
Copy link
Member Author

qn895 commented Jan 16, 2026

@elasticmachine merge upstream
@qn895 qn895 requested review from TattdCodeMonkey and removed request for TattdCodeMonkey January 16, 2026 18:03
@qn895
Copy link
Member Author

qn895 commented Jan 21, 2026

@elasticmachine merge upstream
@qn895 qn895 enabled auto-merge (squash) January 21, 2026 15:02
@elasticmachine
Copy link
Contributor

elasticmachine commented Jan 21, 2026

⏳ Build in-progress

  • Buildkite Build
  • Commit: b486834
  • Kibana Serverless Image: docker.elastic.co/kibana-ci/kibana-serverless:pr-248167-b48683400726

History

cc @qn895
@qn895 qn895 merged commit d6f87d3 into elastic:main Jan 21, 2026
17 checks passed
@kibanamachine
Copy link
Contributor

kibanamachine commented Jan 21, 2026

Starting backport for target branches: 9.3

https://github.com/elastic/kibana/actions/runs/21218522615
@kibanamachine
Copy link
Contributor

kibanamachine commented Jan 21, 2026

💔 All backports failed

Status Branch Result
❌ 9.3 Backport failed because of merge conflicts

You might need to backport the following PRs to 9.3:
- [Scout reporter] Set area and owner fields to unknown if no mapping is found (#249837)
- [OTel Metrics exporter] Match export timeout and interval (#248807)
- [Obs AI] Use the Observability Agent in AI Insights and flyout config (#249776)
- [Security Solution] Installation review pagination: Frontend (#248259)
- [Global Search] validate the options.preference request parameter (#249787)
- [Markdown] Fix Reporting (#249644)
- [Streams][SigEvents] Prevent editing feature of significant event queries (#249716)
- [agent builder] telemetry updates + docs (#249820)

Manual backport

To create the backport manually run:

node scripts/backport --pr 248167

Questions ?

Please refer to the Backport tool documentation
@qn895 qn895 mentioned this pull request Jan 21, 2026
Merged
@qn895
Copy link
Member Author

qn895 commented Jan 21, 2026

💚 All backports created successfully

Status Branch Result
✅ 9.3

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

Questions ?

Please refer to the Backport tool documentation
qn895 added a commit to qn895/kibana that referenced this pull request Jan 22, 2026
@qn895 @elasticmachine @kibanamachine
[ML] Fix broken Data Visualizer & AIOps breadcrumbs / sidebar in solu…
08b5314 
…tions (elastic#248167)

## Summary

This PR addresses elastic#245826. For
reviewers, these are small changes with the sidebar to make the sure the
names are consistent.

After:


https://github.com/user-attachments/assets/f8f78190-1df6-48df-ba73-3d160ac3e186



### 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: Elastic Machine <elasticmachine@users.noreply.github.com>
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
dennis-tismenko pushed a commit to dennis-tismenko/kibana that referenced this pull request Jan 22, 2026
@qn895 @elasticmachine
@kibanamachine @dennis-tismenko
[ML] Fix broken Data Visualizer & AIOps breadcrumbs / sidebar in solu…
a72a1bc 
…tions (elastic#248167)

## Summary

This PR addresses elastic#245826. For
reviewers, these are small changes with the sidebar to make the sure the
names are consistent.

After:


https://github.com/user-attachments/assets/f8f78190-1df6-48df-ba73-3d160ac3e186



### 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: Elastic Machine <elasticmachine@users.noreply.github.com>
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
qn895 added a commit that referenced this pull request Jan 23, 2026
@qn895 @elasticmachine
[9.3] [ML] Fix broken Data Visualizer & AIOps breadcrumbs / sidebar i…
8849053 
…n solutions (#248167) (#249941)

# Backport

This will backport the following commits from `main` to `9.3`:
- [[ML] Fix broken Data Visualizer & AIOps breadcrumbs / sidebar in
solutions (#248167)](#248167)

<!--- Backport version: 10.2.0 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Quynh Nguyen
(Quinn)","email":"43350163+qn895@users.noreply.github.com"},"sourceCommit":{"committedDate":"2026-01-21T17:03:44Z","message":"[ML]
Fix broken Data Visualizer & AIOps breadcrumbs / sidebar in solutions
(#248167)\n\n## Summary\n\nThis PR addresses
#245826. For\nreviewers, these
are small changes with the sidebar to make the sure the\nnames are
consistent.\n\nAfter:\n\n\nhttps://github.com/user-attachments/assets/f8f78190-1df6-48df-ba73-3d160ac3e186\n\n\n\n###
Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers
should verify this PR satisfies this list as well.\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-
[ ] Review the
[backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand
apply applicable `backport:*` labels.\n\n### Identify risks\n\nDoes this
PR introduce any risks? For example, consider risks like hard\nto test
bugs, performance regression, potential of data loss.\n\nDescribe the
risk, its severity, and mitigation for each identified\nrisk. Invite
stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See
some
risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n-
[ ] ...\n\n---------\n\nCo-authored-by: Elastic Machine
<elasticmachine@users.noreply.github.com>\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"d6f87d3ed1321834de939db4e8a1dd891b72e35e","branchLabelMapping":{"^v9.4.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix",":ml","ci:project-deploy-observability","backport:version","v9.3.0","v9.4.0","Team:obs-ux-management"],"title":"[ML]
Fix broken Data Visualizer & AIOps breadcrumbs / sidebar in
solutions","number":248167,"url":"https://github.com/elastic/kibana/pull/248167","mergeCommit":{"message":"[ML]
Fix broken Data Visualizer & AIOps breadcrumbs / sidebar in solutions
(#248167)\n\n## Summary\n\nThis PR addresses
#245826. For\nreviewers, these
are small changes with the sidebar to make the sure the\nnames are
consistent.\n\nAfter:\n\n\nhttps://github.com/user-attachments/assets/f8f78190-1df6-48df-ba73-3d160ac3e186\n\n\n\n###
Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers
should verify this PR satisfies this list as well.\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-
[ ] Review the
[backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand
apply applicable `backport:*` labels.\n\n### Identify risks\n\nDoes this
PR introduce any risks? For example, consider risks like hard\nto test
bugs, performance regression, potential of data loss.\n\nDescribe the
risk, its severity, and mitigation for each identified\nrisk. Invite
stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See
some
risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n-
[ ] ...\n\n---------\n\nCo-authored-by: Elastic Machine
<elasticmachine@users.noreply.github.com>\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"d6f87d3ed1321834de939db4e8a1dd891b72e35e"}},"sourceBranch":"main","suggestedTargetBranches":["9.3"],"targetPullRequestStates":[{"branch":"9.3","label":"v9.3.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.4.0","branchLabelMappingKey":"^v9.4.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/248167","number":248167,"mergeCommit":{"message":"[ML]
Fix broken Data Visualizer & AIOps breadcrumbs / sidebar in solutions
(#248167)\n\n## Summary\n\nThis PR addresses
#245826. For\nreviewers, these
are small changes with the sidebar to make the sure the\nnames are
consistent.\n\nAfter:\n\n\nhttps://github.com/user-attachments/assets/f8f78190-1df6-48df-ba73-3d160ac3e186\n\n\n\n###
Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers
should verify this PR satisfies this list as well.\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-
[ ] Review the
[backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand
apply applicable `backport:*` labels.\n\n### Identify risks\n\nDoes this
PR introduce any risks? For example, consider risks like hard\nto test
bugs, performance regression, potential of data loss.\n\nDescribe the
risk, its severity, and mitigation for each identified\nrisk. Invite
stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See
some
risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n-
[ ] ...\n\n---------\n\nCo-authored-by: Elastic Machine
<elasticmachine@users.noreply.github.com>\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"d6f87d3ed1321834de939db4e8a1dd891b72e35e"}}]}]
BACKPORT-->

---------

Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
@peteharverson peteharverson changed the title [ML] Fix broken Data Visualizer & AIOps breadcrumbs / sidebar in solutions Jan 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport:version Backport to applied version labels bug Fixes for quality problems that affect the customer experience ci:project-deploy-observability Create an Observability project :ml release_note:fix Team:obs-ux-management v9.3.0 v9.4.0

10 participants

@qn895 @elasticmachine @kibanamachine @ashokaditya @TattdCodeMonkey @peteharverson @Dosant @PhilippeOberti @rmyz @benakansara