Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Security Solution] Alert Page Filters do not respect the local storage values across upgrades #211027

Open
logeekal opened this issue Feb 13, 2025 · 2 comments
Labels
bug Fixes for quality problems that affect the customer experience Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. triage_needed

Comments

@logeekal
Copy link
Contributor

Describe the bug:

Alert Page Filters do not respect the local storage values across upgrades. This has happened because of changes in this line in this PR

Kibana/Elasticsearch Stack version:

8.18.0

Functional Area (e.g. Endpoint management, timelines, resolver, etc.):

Alert Page

Steps to reproduce:

  1. Go to a version before 8.15 say 8.10.
  2. Load up some Alert data.
  3. Go to Alert page and customize alert page filters
  4. Upgrade to 8.18.0.
  5. Changes in Alert Page filters will be lost and reset as default.

Current behavior:
Changes in Alert Page filters are lost and reset as default. A new localstorage key is created ignoring the previous one.

Expected behavior:
Old local storage data should be migrated to the new format so the old user saved can be retained.

Screenshots (if relevant):

Errors in browser console (if relevant):

Provide logs and/or server output (if relevant):

Any additional context (logs, chat logs, magical formulas, etc.):

@logeekal logeekal added bug Fixes for quality problems that affect the customer experience Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) triage_needed labels Feb 13, 2025
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-solution (Team: SecuritySolution)

@elasticmachine
Copy link
Contributor

Pinging @elastic/response-ops (Team:ResponseOps)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. triage_needed
Projects
None yet
Development

No branches or pull requests

2 participants