Skip to content

[9.1] [Discover][Query Bar] Enable "Save Query" button after making changes in the save query menu (#229053)#229911

Merged
kibanamachine merged 1 commit intoelastic:9.1from
kibanamachine:backport/9.1/pr-229053
Jul 30, 2025
Merged

[9.1] [Discover][Query Bar] Enable "Save Query" button after making changes in the save query menu (#229053)#229911
kibanamachine merged 1 commit intoelastic:9.1from
kibanamachine:backport/9.1/pr-229053

Conversation

@kibanamachine
Copy link
Contributor

Backport

This will backport the following commits from main to 9.1:

Questions ?

Please refer to the Backport tool documentation

… in the save query menu (elastic#229053)

## Summary

This PR fixes an issue where the `Save Query` button was disabled after
making changes (e.g., adding filters) in the query menu. Currently, a
user is unable to click `Save Query` if they previously saved the query
with the `Include filters` field unchecked and then added new filters.

The problem occurred because we compare the filter state in the
useEffect hook. However, if the user saved the query without the
`Include filters` option, the in-memory object lacked the
`attributes.filters` property entirely. This prevented the comparison
from executing correctly and resulted in the logical test always
returning `false`.

To fix the issue, I removed the `savedQuery?.attributes.filters &&`
condition, and provided `[]` as a fallback value for
`savedQuery?.attributes.filters` if the filters were not defined.

Resolves: elastic#210948

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

(cherry picked from commit 43c1ea7)
@kibanamachine kibanamachine merged commit d84af85 into elastic:9.1 Jul 30, 2025
16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport This PR is a backport of another PR

2 participants