-
Notifications
You must be signed in to change notification settings - Fork 8.6k
[Security Solution] Incorrect field count in Rule Upgrade flyout #200286
Copy link
Copy link
Closed
Labels
8.18 candidateFeature:Prebuilt Detection RulesSecurity Solution Prebuilt Detection Rules areaSecurity Solution Prebuilt Detection Rules areaTeam: SecuritySolutionSecurity Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.Team:Detection Rule ManagementSecurity Detection Rule Management TeamSecurity Detection Rule Management TeamTeam:Detections and RespSecurity Detection Response TeamSecurity Detection Response TeambugFixes for quality problems that affect the customer experienceFixes for quality problems that affect the customer experiencefixedimpact:lowAddressing this issue will have a low level of impact on the quality/strength of our product.Addressing this issue will have a low level of impact on the quality/strength of our product.v8.18.0
Metadata
Metadata
Assignees
Labels
8.18 candidateFeature:Prebuilt Detection RulesSecurity Solution Prebuilt Detection Rules areaSecurity Solution Prebuilt Detection Rules areaTeam: SecuritySolutionSecurity Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.Team:Detection Rule ManagementSecurity Detection Rule Management TeamSecurity Detection Rule Management TeamTeam:Detections and RespSecurity Detection Response TeamSecurity Detection Response TeambugFixes for quality problems that affect the customer experienceFixes for quality problems that affect the customer experiencefixedimpact:lowAddressing this issue will have a low level of impact on the quality/strength of our product.Addressing this issue will have a low level of impact on the quality/strength of our product.v8.18.0
Type
Fields
Give feedbackNo fields configured for Bug.
Related to: #200904
Summary
Describe the bug:
When reviewing rule updates in the Update Flyout, the conflict message incorrectly displays the total number of fields with update conflicts. The message consistently shows a count of Fields + 1, regardless of the actual number of conflicting fields.
Kibana/Elasticsearch Stack version:
8.x
Steps to reproduce:
Current behavior:
The conflict messages states:
Where X = Actual fields + 1.
Expected behavior:
The conflict message should accurately reflect the actual number of conflicting fields.
Screenshots