[Security Solution] Fields Displayed in Current Version Despite Being Removed

[pborgonovi]

Describe the bug:

When fields like Tags, Related Integrations, and MITRE ATT&CK are removed in the Customized version of a rule, they still appear in the Current version within the rule updates table.

Kibana/Elasticsearch Stack version:

8.x

Current branch: 8.x  
Latest commit: d0c9a2f1f52 - [8.x] [Stack Monitoring / Logs] Fix Stack Monitoring logs links (#200043) (#200227)  
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.):

Steps to reproduce:

1. Select a prebuilt rule which has an update available and customize it by removing all tags in the Tags, Related Integrations and MITRE ATT&CK fields.
2. Save the customized rule.
3. Open the Rule Updates table for the customized rule.
4. Observe the tags displayed under the Current version.

Current behavior:

Fields that were cleared (e.g., Tags, Related Integrations, MITRE ATT&CK) in the Customized version still appear with their previous values in the Current version within the rule updates table.

Expected behavior:

The Current version should correctly reflect the actual customized state of the rule. For fields like Tags, Related Integrations, or MITRE ATT&CK, if all values are removed during customization, the Current version should display an empty state or indicate that the field is cleared.

Screenshots (if relevant):

Screen.Recording.2024-11-14.at.3.57.45.PM.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-detections-response (Team:Detections and Resp)

[elasticmachine]

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