You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are tracking an inconsistency in how saved searches behave in the Discover plugin. Users are experiencing different results depending on how they access their saved searches.
Please help us understand the impact by adding a 👍🏼 reaction if you're experiencing this issue.
STATUS: Under active investigation WORKAROUND: No current workaround available PREREQUISITES:
-query:enhancements:enabled must be set to true in Advanced Settings
or
- snapshot URL created from with a saved search
Known Impact
Impacts direct/indirect loading of saved searches.
Direct Loading: When accessing a saved search through OpenSearch's standard navigation paths (Discover menu, saved objects list, dashboard panels) where the application has full context of the saved search configuration
example: User clicks on a saved search titled "Error Logs" from the Discover sidebar expected: Saved search should load with all configured filters, and field selections intact
Indirect Loading: Accessing a saved search through external paths where the application needs to rebuild the search context (shared URLs, browser navigation, session restore)
example: User opens a shared saved search snapshot URL in a new browser tab expected: Saved search should maintain the updates made by the user at the time of the snapshot url was created
Issues
Inconsistent (direct/indirect) loading of the following:
Query
Saved filters
Selected columns
Snapshot URL prioritizing saved search over snapshot updates
Affected Versions
^2.16.0
Please comment if you're seeing this in other versions
Additional Context
If you're experiencing this issue, it would be helpful to include in comments:
Your access method (direct/indirect)
OSD version
Browser type and version
Steps to reproduce the inconsistency
Please react with 👍🏼 to help us track impact. Please add a comment with your specific use case if it differs from the examples
We'll update this issue as we make progress on the investigation.
The text was updated successfully, but these errors were encountered:
kavilla
changed the title
[BUG][meta] Saved Search: Inconsistent Loading Behavior in Discover
[BUG][tracking] Saved Search: Inconsistent Loading Behavior in Discover
Mar 1, 2025
Description
We are tracking an inconsistency in how saved searches behave in the Discover plugin. Users are experiencing different results depending on how they access their saved searches.
Please help us understand the impact by adding a 👍🏼 reaction if you're experiencing this issue.
STATUS:
Under active investigation
WORKAROUND:
No current workaround available
PREREQUISITES:
-
query:enhancements:enabled
must be set totrue
in Advanced Settingsor
- snapshot URL created from with a saved search
Known Impact
Impacts direct/indirect loading of saved searches.
Direct Loading: When accessing a saved search through OpenSearch's standard navigation paths (Discover menu, saved objects list, dashboard panels) where the application has full context of the saved search configuration
Indirect Loading: Accessing a saved search through external paths where the application needs to rebuild the search context (shared URLs, browser navigation, session restore)
Issues
Affected Versions
^2.16.0
Additional Context
If you're experiencing this issue, it would be helpful to include in comments:
Please react with 👍🏼 to help us track impact. Please add a comment with your specific use case if it differs from the examples
We'll update this issue as we make progress on the investigation.
The text was updated successfully, but these errors were encountered: