[Security Solution] Changes in Final Column Persist After Dismissal but Are Lost Upon Navigating Tabs

[pborgonovi]

Describe the bug:

Changes made to the Final column in the rule update flyout persist after clicking the “Dismiss” button. However, these changes are lost if the user navigates to another tab and then returns to the Updates tab.

Kibana/Elasticsearch Stack version:

8.x

Current branch: 8.x  
Latest commit: f3da0dccd45 - [8.x] [Automatic Import] Add base for ftr api tests (#200169) (#202752)  
Remote tracking: origin/8.x  
Status relative to remote: up to date (no pending commits)  

Server OS version:

Browser and Browser OS versions:

Elastic Endpoint version:

Original install method (e.g. download page, yum, from source, etc.):

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

Pre requisites:

1. Feature flag prebuiltRulesCustomizationEnabled is ON
2. Rules are installed
3. Rules updates are available

Steps to reproduce:

1. Navigate to the Updates tab and open one rule update flyout.
2. Edit any field in the Final column.
3. Click the Dismiss button to close the flyout.
4. Navigate to another tab (e.g. Installed Rules).
5. Return to the Updates tab and reopen the flyout.

Current behavior:

• Changes made to the Final column persist when the flyout is dismissed and reopened without leaving the Updates tab.
• Changes are lost after navigating to another tab and returning to the Updates tab.

Expected behavior:

Either persist the changes consistently, even after navigating to other tabs or discard all unsaved changes upon clicking Dismiss, ensuring a reset state.

Screenshots (if relevant):

Screen.Recording.2024-12-03.at.10.54.30.AM.mov

Errors in browser console (if relevant):

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

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

[elasticmachine]

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

[elasticmachine]

Pinging @elastic/security-detection-rule-management (Team:Detection Rule Management)

[elasticmachine]

Pinging @elastic/security-detections-response (Team:Detections and Resp)

[banderror]

@pborgonovi I agree that it's not an ideal behavior. We'll fix it later. Since it's low-impact it goes to Milestone 4.