-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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] Stale rule data is displayed in the upgrade flyout #202779
Closed
Tracked by
#201502
Labels
8.18 candidate
bug
Fixes for quality problems that affect the customer experience
Feature:Prebuilt Detection Rules
Security Solution Prebuilt Detection Rules area
Team:Detection Rule Management
Security Detection Rule Management Team
Team:Detections and Resp
Security Detection Response Team
Team: SecuritySolution
Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.
v8.18.0
Comments
xcrzx
added
8.18 candidate
bug
Fixes for quality problems that affect the customer experience
Feature:Prebuilt Detection Rules
Security Solution Prebuilt Detection Rules area
Team: SecuritySolution
Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.
Team:Detection Rule Management
Security Detection Rule Management Team
Team:Detections and Resp
Security Detection Response Team
triage_needed
labels
Dec 3, 2024
Pinging @elastic/security-detection-rule-management (Team:Detection Rule Management) |
Pinging @elastic/security-solution (Team: SecuritySolution) |
Pinging @elastic/security-detections-response (Team:Detections and Resp) |
This was referenced Dec 4, 2024
xcrzx
added a commit
that referenced
this issue
Dec 5, 2024
**Resolves: #202779 ## Summary Implemented proper cache invalidation after rule CRUD operations to prevent displaying stale data in rule upgrade flyouts. See the linked issue for more details. ### How to Test 1. Ensure rule customization is enabled 2. Navigate to the Rule Updates page 3. Locate any rule with updates 4. Make changes to the rule: - Edit the rule via the Rule Editing page - Use bulk actions - Delete the rule 5. Return to the Rule Updates page - All introduced changes should be reflected: - Modifications should be visible - If the rule was deleted, it should no longer appear on the page
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this issue
Dec 5, 2024
…ic#202969) **Resolves: elastic#202779 ## Summary Implemented proper cache invalidation after rule CRUD operations to prevent displaying stale data in rule upgrade flyouts. See the linked issue for more details. ### How to Test 1. Ensure rule customization is enabled 2. Navigate to the Rule Updates page 3. Locate any rule with updates 4. Make changes to the rule: - Edit the rule via the Rule Editing page - Use bulk actions - Delete the rule 5. Return to the Rule Updates page - All introduced changes should be reflected: - Modifications should be visible - If the rule was deleted, it should no longer appear on the page (cherry picked from commit 94c5614)
SoniaSanzV
pushed a commit
to SoniaSanzV/kibana
that referenced
this issue
Dec 9, 2024
…ic#202969) **Resolves: elastic#202779 ## Summary Implemented proper cache invalidation after rule CRUD operations to prevent displaying stale data in rule upgrade flyouts. See the linked issue for more details. ### How to Test 1. Ensure rule customization is enabled 2. Navigate to the Rule Updates page 3. Locate any rule with updates 4. Make changes to the rule: - Edit the rule via the Rule Editing page - Use bulk actions - Delete the rule 5. Return to the Rule Updates page - All introduced changes should be reflected: - Modifications should be visible - If the rule was deleted, it should no longer appear on the page
SoniaSanzV
pushed a commit
to SoniaSanzV/kibana
that referenced
this issue
Dec 9, 2024
…ic#202969) **Resolves: elastic#202779 ## Summary Implemented proper cache invalidation after rule CRUD operations to prevent displaying stale data in rule upgrade flyouts. See the linked issue for more details. ### How to Test 1. Ensure rule customization is enabled 2. Navigate to the Rule Updates page 3. Locate any rule with updates 4. Make changes to the rule: - Edit the rule via the Rule Editing page - Use bulk actions - Delete the rule 5. Return to the Rule Updates page - All introduced changes should be reflected: - Modifications should be visible - If the rule was deleted, it should no longer appear on the page
CAWilson94
pushed a commit
to CAWilson94/kibana
that referenced
this issue
Dec 9, 2024
…ic#202969) **Resolves: elastic#202779 ## Summary Implemented proper cache invalidation after rule CRUD operations to prevent displaying stale data in rule upgrade flyouts. See the linked issue for more details. ### How to Test 1. Ensure rule customization is enabled 2. Navigate to the Rule Updates page 3. Locate any rule with updates 4. Make changes to the rule: - Edit the rule via the Rule Editing page - Use bulk actions - Delete the rule 5. Return to the Rule Updates page - All introduced changes should be reflected: - Modifications should be visible - If the rule was deleted, it should no longer appear on the page
Samiul-TheSoccerFan
pushed a commit
to Samiul-TheSoccerFan/kibana
that referenced
this issue
Dec 10, 2024
…ic#202969) **Resolves: elastic#202779 ## Summary Implemented proper cache invalidation after rule CRUD operations to prevent displaying stale data in rule upgrade flyouts. See the linked issue for more details. ### How to Test 1. Ensure rule customization is enabled 2. Navigate to the Rule Updates page 3. Locate any rule with updates 4. Make changes to the rule: - Edit the rule via the Rule Editing page - Use bulk actions - Delete the rule 5. Return to the Rule Updates page - All introduced changes should be reflected: - Modifications should be visible - If the rule was deleted, it should no longer appear on the page
mykolaharmash
pushed a commit
to mykolaharmash/kibana
that referenced
this issue
Dec 11, 2024
…ic#202969) **Resolves: elastic#202779 ## Summary Implemented proper cache invalidation after rule CRUD operations to prevent displaying stale data in rule upgrade flyouts. See the linked issue for more details. ### How to Test 1. Ensure rule customization is enabled 2. Navigate to the Rule Updates page 3. Locate any rule with updates 4. Make changes to the rule: - Edit the rule via the Rule Editing page - Use bulk actions - Delete the rule 5. Return to the Rule Updates page - All introduced changes should be reflected: - Modifications should be visible - If the rule was deleted, it should no longer appear on the page
CAWilson94
pushed a commit
to CAWilson94/kibana
that referenced
this issue
Dec 12, 2024
…ic#202969) **Resolves: elastic#202779 ## Summary Implemented proper cache invalidation after rule CRUD operations to prevent displaying stale data in rule upgrade flyouts. See the linked issue for more details. ### How to Test 1. Ensure rule customization is enabled 2. Navigate to the Rule Updates page 3. Locate any rule with updates 4. Make changes to the rule: - Edit the rule via the Rule Editing page - Use bulk actions - Delete the rule 5. Return to the Rule Updates page - All introduced changes should be reflected: - Modifications should be visible - If the rule was deleted, it should no longer appear on the page
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
8.18 candidate
bug
Fixes for quality problems that affect the customer experience
Feature:Prebuilt Detection Rules
Security Solution Prebuilt Detection Rules area
Team:Detection Rule Management
Security Detection Rule Management Team
Team:Detections and Resp
Security Detection Response Team
Team: SecuritySolution
Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.
v8.18.0
Summary
Stale rule data is displayed in the rule upgrade flyout after a rule has been edited locally.
Steps to Reproduce
upgrade/_review
endpoint data is loaded locally.Expected Result
The rule update flyout reflects the changes introduced locally.
Actual Result
Stale rule data is displayed in the rule update flyout. Any attempt to update the rule results in an error due to a revision mismatch.
Note
This issue likely occurs because the
upgrade/_review
cache is not invalidated when a rule is edited. We need to ensure that every rule CRUD operation, including bulk operations, performed locally triggers cache invalidation for the review endpoint.The text was updated successfully, but these errors were encountered: