[Security Solution]User able to set History window size to zero under New Term Rule

[ghost]

Describe the bug:
User able to set History window size to zero under New Term Rule

Kibana/Elasticsearch Stack version
Version: 8.10.0 BC2
Commit: fa3473f
Build: 66107

Browser and Browser OS Version:
Firefox for windows OS
Version: 116.0.3(64-bit)

Elastic Endpoint Version:
v8.10.2

Original install method:
Build summary: https://staging.elastic.co/8.10.0-049269aa/summary-8.10.0.html

Functional Area:
New Term Rule

Initial Setup:

• None

Steps to reproduce

• Navigate to Rule page and create rule
• fill in the required details of step 1
• set zero minutes as history window size ( you can also set zero days and seconds too)
• Observed that user is able to set the size to Zero which is incorrect

Additional Observation

• User is not able to save the Rule with zero minutes/day/second in history window size

Current behavior

• History window size field can be set to zero minutes/days/second

Expected behavior:

• History window size field should not be set to zero minutes/days/second

Screen-cast:

Create.new.rule.-.Kibana.Mozilla.Firefox.2023-08-23.11-46-23.mp4

Errors in browser console:
N/A

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

N/A

[elasticmachine]

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

[ghost]

@amolnater-qasource please review

[amolnater-qasource]

Reviewed & assigned to @MadameSheema

[elasticmachine]

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

[MadameSheema]

@karanbirsingh-qasource can the same issue be replicated on 8.9.x? Thanks!

[ghost]

yes @MadameSheema there also it is occuring.

8.9.1

[yctercero]

Hey team! I think it's ok to add this to the backlog for the moment being. For now the user is still blocked from creating the rule so they won't be saving a bad state.

[pborgonovi]

Validated on latest BC 8.15:

User is able to get passed step 1 with History Window Size == 0:

However, the user gets an error if tries to save the rule with the given params:

@yctercero I'm downgrading the impact to low and keeping this one opened so we can discuss if we should have a validation on Window Size field and not allow the users to proceed with invalid values.

[arvindersingh-qasource]

Hi @yctercero

Thanks for the updates.

We have validated this ticket on latest kibana v8.16.0 snapshot build and found that this issue is now fixed.

Please find the below observations

VERSION: 8.16.0
BUILD: 78938
COMMIT: 7b832691e8b07c67b411da95b0398a04711da864

Observations

• Error History window size must be greater than 0. is visible as soon as user enters 0 as value under History Window Size field.

Hence, we are closing this ticket as QA Approved.

Thanks.