Conversation
|
Pinging @elastic/kibana-presentation (Team:Presentation) |
|
@cqliu1 |
@kowalczyk-krzysztof It shouldn't break your write-restricted dashboards functionality, but I am moving the |
Thanks for looking into this @cqliu1! @SiddharthMantri @jeramysoucy This PR will most likely get merged first but not before I go on PTO. Please make sure to reach out to @cqliu1 if you run into any issues with resolving conflicts. |
173730d to
b0cbc86
Compare
f3f2b7c to
3372080
Compare
ddfeb82 to
189659b
Compare
davismcphee
left a comment
There was a problem hiding this comment.
Code-only review, Data Discovery changes LGTM 👍 Just minor changes to the split button package.
…rd/top-nav-save-menu
kowalczyk-krzysztof
left a comment
There was a problem hiding this comment.
SharedUX code changes LGTM 🚀
I also tried integrating this into my write-restricted dashboards PR and it went surprisingly smoothly.
andreadelrio
left a comment
There was a problem hiding this comment.
@cqliu1 Design changes LGTM! Nicely done!
nreese
left a comment
There was a problem hiding this comment.
kibana-presentation changes LGTM
code review and tested in chrome
|
@elasticmachine merge upstream |
⏳ Build in-progress
History
|
## Summary Closes elastic#192630. Closes [elastic#237210](elastic#237210). This moves the `Save as` and `Reset` top nav actions into a split button menu next to the `Save` button in edit mode. <img width="1188" height="777" alt="Screenshot 2025-10-29 at 10 18 39 AM" src="https://github.com/user-attachments/assets/06ac1310-e3f7-4251-ade0-3b94eeb5d8d2" /> #### With unsaved changes <img width="624" height="164" alt="Screenshot 2025-10-29 at 10 20 33 AM" src="https://github.com/user-attachments/assets/4e42212f-b7f1-4b29-9525-6b2b6ee6f207" /> #### View mode The duplicate and reset actions remain in the top nav in view mode. <img width="428" height="168" alt="Screenshot 2025-10-29 at 10 21 29 AM" src="https://github.com/user-attachments/assets/3d70796f-c2f6-4312-b017-3dc5f0461388" /> #### Editing a new dashboard The save button returns to a normal button with no additional save options. <img width="456" height="124" alt="Screenshot 2025-10-29 at 10 22 13 AM" src="https://github.com/user-attachments/assets/7c0ca3e6-e567-43d2-9a4e-6c25fd9e03f2" /> I also cleaned up styles for the add menu <img width="440" height="526" alt="Screenshot 2025-10-29 at 10 12 57 AM" src="https://github.com/user-attachments/assets/e8117793-14da-472a-9aaf-ebc3d55e94f0" /> ### 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> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
Summary
Closes #192630.
Closes #237210.
This moves the
Save asandResettop nav actions into a split button menu next to theSavebutton in edit mode.With unsaved changes
View mode
The duplicate and reset actions remain in the top nav in view mode.
Editing a new dashboard
The save button returns to a normal button with no additional save options.

I also cleaned up styles for the add menu
Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
release_note:breakinglabel should be applied in these situations.release_note:*label is applied per the guidelinesbackport:*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.