Skip to content

[Search] Navigation Updates#224755

Merged
TattdCodeMonkey merged 8 commits intoelastic:mainfrom
TattdCodeMonkey:search/solution-nav-updates
Jun 25, 2025
Merged

[Search] Navigation Updates#224755
TattdCodeMonkey merged 8 commits intoelastic:mainfrom
TattdCodeMonkey:search/solution-nav-updates

Conversation

@TattdCodeMonkey
Copy link
Contributor

@TattdCodeMonkey TattdCodeMonkey commented Jun 20, 2025

Summary

Updates to streamline the search solution navigation:

image

Classic Nav:
image

Classic Global Flyout
image

Checklist

Release note

Updated the Elasticsearch solution navigations and elasticsearch classic navigation items available.

@TattdCodeMonkey TattdCodeMonkey requested a review from a team as a code owner June 20, 2025 19:28
@TattdCodeMonkey TattdCodeMonkey force-pushed the search/solution-nav-updates branch 5 times, most recently from 0a91097 to 0fdddc2 Compare June 23, 2025 21:36
@TattdCodeMonkey TattdCodeMonkey changed the title [Search] update solution navigation Jun 23, 2025
Copy link
Contributor

@pgayvallet pgayvallet left a comment

Choose a reason for hiding this comment

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

Solution nav is a fine piece of engineering (repeating this 100 times didn't help)

@TattdCodeMonkey TattdCodeMonkey force-pushed the search/solution-nav-updates branch from afae326 to bb68838 Compare June 24, 2025 19:32
@TattdCodeMonkey TattdCodeMonkey enabled auto-merge (squash) June 24, 2025 21:04
@TattdCodeMonkey TattdCodeMonkey force-pushed the search/solution-nav-updates branch from c0ee322 to 3b7085e Compare June 24, 2025 23:26
@TattdCodeMonkey TattdCodeMonkey merged commit 1faad68 into elastic:main Jun 25, 2025
10 checks passed
@elasticmachine
Copy link
Contributor

💛 Build succeeded, but was flaky

Failed CI Steps

Test Failures

  • [job] [logs] FTR Configs #126 / task_manager with update by query task claimer task manager metrics task claim should increment task claim success/total counters

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id before after diff
enterpriseSearch 1.2MB 1.2MB -384.0B
searchIndices 193.5KB 193.5KB -46.0B
searchNavigation 2.9KB 2.0KB -940.0B
total -1.3KB

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id before after diff
enterpriseSearch 39.1KB 39.1KB +41.0B
searchIndices 9.1KB 9.4KB +210.0B
searchInferenceEndpoints 7.1KB 7.2KB +68.0B
searchQueryRules 5.7KB 5.9KB +213.0B
searchSynonyms 5.5KB 5.7KB +212.0B
total +744.0B

History

akowalska622 pushed a commit to akowalska622/kibana that referenced this pull request Jun 25, 2025
## Summary

Updates to streamline the search solution navigation:


![image](https://github.com/user-attachments/assets/6ae1fdb8-924a-4e06-87ff-5f898db6f6a8)

Classic Nav:
<img width="700" alt="image"
src="https://github.com/user-attachments/assets/530c1f22-b69d-46f7-89ce-053f85f13d8a"
/>

Classic Global Flyout
<img width="295" alt="image"
src="https://github.com/user-attachments/assets/c9822f47-b9e4-4fad-997c-13356b2fc46a"
/>


### 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
- [ ] [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)

## Release note

Updated the Elasticsearch solution navigations items.
saikatsarkar056 added a commit that referenced this pull request Jun 30, 2025
… active page (#225902)

## Summary

This PR adds FTR tests to verify that the Home page is correctly marked
as active. Previously, when a user was on the Home page, it wasn’t
highlighted in the side navigation. This
[PR](#224755) addresses and
resolves that issue.


### 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.
- [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)
- [x] 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)
- [ ] ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

3 participants