search

elastic / kibana

Your window into the Elastic Stack
https://www.elastic.co/products/kibana
Other
19.75k stars 8.15k forks source link

[Security Solution]User is not able to add maximum value supported into Additional look-back time field. #142959

Open sukhwindersingh-qasource opened 1 year ago

sukhwindersingh-qasource commented 1 year ago

Describe the bug: User is not able to add maximum value supported into Additional look-back time field.

Build Details:

VERSION: 8.5.0
BUILD: 56932
COMMIT: 1bb0d052c8d6842b88665c8c489f3a2d4cf4b46a

Preconditions

  1. Kibana should be running.
  2. Custom rule should be created.

Steps to Reproduce

  1. Navigate to security in kibana.
  2. Select custom created rule and click on bulk action.
  3. Click on update rules schedules.
  4. Enter Max value supported .

Actual Result User is not able to add maximum value supported into Additional look-back time field.

Expected Result User should be able to add maximum value supported into Additional look-back time field.

Screen-Recording:

https://user-images.githubusercontent.com/108654988/194828432-568cde03-5b7d-4366-9de2-745764d957dd.mp4

elasticmachine commented 1 year ago

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

sukhwindersingh-qasource commented 1 year ago

@deepikakeshav-qasource Please review this.

elasticmachine commented 1 year ago

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

cybersecdiva commented 1 year ago

Tested in current 8.7.0 deployment:

Preconditions:

Steps to reproduce behavior:

  1. Navigate to Security -> Manage -> Rules
  2. Select the custom rule and click on Bulk actions dropdown list 🔽 and select Update rule schedules
  3. In the Runs every and Additional look-back time fields enter the maximum value supported
  4. Click Save
  5. Click on the custom rule and view the Rule details
  6. In the Schedule section view the Additional look-back time field value

Results: The Additional look-back time field does not display the maximum value entered by the user

Expected results: The Additional look-back time field displays the maximum value entered by the user

Screen video capture:

https://user-images.githubusercontent.com/35679937/231261480-8508f9a7-8936-4bdb-b068-2c7bc4aae685.mp4

Observations:

Screenshots:

Additional look-back time showing NaNs as the field value:

Screenshot 2023-04-11 at 2 41 53 PM

Additional look-back time showing 0 as the field value in Rule Preview:

Screenshot 2023-04-11 at 2 42 26 PM

Conclusion:

Validated this is still a bug 🐛 in the UI for 8.7.0

cc: @MadameSheema Update FYI Observations

cybersecdiva commented 1 year ago

Tested in current 8.9.0 deployment:

Build Details:
VERSION: 8.9.0 BC5
BUILD: 64715
COMMIT: beb56356c5c037441f89264361302513ff5bd9f8

Preconditions:

Steps to reproduce behavior:

  1. Navigate to Security -> Manage -> Rules
  2. Select the custom rule and click on Bulk actions dropdown list 🔽 and select Update rule schedules
  3. In the Runs every and Additional look-back time fields enter the maximum value supported
  4. Click Save
  5. Click on the custom rule and view the Rule details
  6. In the Schedule section view the Additional look-back time field value

Results: The Additional look-back time field does not display the maximum value entered by the user

Expected results: The Additional look-back time field displays the maximum value entered by the user

Screen video capture:

https://github.com/elastic/kibana/assets/35679937/99a34412-3e7d-44e2-8102-9e8dcc443e0b

Observations:

Screenshots:

Additional look-back time showing NaNs as the field value:

Screenshot 2023-08-10 at 6 16 05 PM

Additional look-back time showing 0 as the field value in Rule Preview:

Screenshot 2023-08-10 at 6 18 37 PM

Conclusion:

Validated this is still a bug 🐛 in the UI for 8.9.0

cc: @MadameSheema Updated FYI Observations

pborgonovi commented 1 month ago

Validated the behavior on latest 8.15 BC and boundary issue is still valid:

https://github.com/user-attachments/assets/fbab74fc-a5e9-4dd1-aaa4-591a607cacc5