Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[RAM][Security Solution]User is able to schedule the snooze in the past time with timezone conversion. #158534

Open
sukhwindersingh-qasource opened this issue May 26, 2023 · 5 comments
Open

[RAM][Security Solution]User is able to schedule the snooze in the past time with timezone conversion. #158534

sukhwindersingh-qasource opened this issue May 26, 2023 · 5 comments
Assignees
@JiaweiWu
Labels
bug Fixes for quality problems that affect the customer experience Feature:Alerting/RulesManagement Issues related to the Rules Management UX Feature:Rule Management Security Solution Detection Rule Management area impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. response-ops-mx-backlog ResponseOps MX backlog Team:Detection Rule Management Security Detection Rule Management Team Team:Detections and Resp Security Detection Response Team Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.

Comments

@sukhwindersingh-qasource
Copy link

Describe the bug:

  • User is able to schedule the snooze in the past time with timezone conversion.

Build Details:

VERSION: 8.8.0 BC8
BUILD: 63142
COMMIT: 2973fcc10d985e4ab94e5eeef976aad0046c6cce

Preconditions

  • Kibana should be running.

Browser

  • Firefox

Steps to Reproduce

  • Navigate to rules detail page of any rule.
  • Now schedule a rule snooze with current time in timezone which are ahead of our timezone.
  • i.e my timezone is asia/kolkata and selected asia/singapore
  • And observe that time conversion is overriding the scheduling basic functionality which is we can not schedule the snooze in the past i.e if now is May 22nd 4:00pm then we can not add scheduling behind May 22nd 4:00pm. But by the time conversion we are able to achieve this thing.

Actual Result

  • User is able to schedule the snooze in the past time with timezone conversion.

Expected Result

  • User should not able to schedule the snooze in the past time with timezone conversion.

Screen-Recording

Trying to add time which is in past
we are not able to add the scheduling in the past.

Rules.-.Kibana.Mozilla.Firefox.2023-05-22.16-19-47.mp4

We can add time which is in past with the help of scheduling
we are able to add scheduling in the past. Just select the timezone which are ahead of our timezone.

Rules.-.Kibana.Mozilla.Firefox.2023-05-22.16-18-42.mp4
@sukhwindersingh-qasource sukhwindersingh-qasource added bug Fixes for quality problems that affect the customer experience triage_needed impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. labels May 26, 2023
@elasticmachine
Copy link
Contributor

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

Closed
@MadameSheema MadameSheema added Team:Detections and Resp Security Detection Response Team Team:Detection Rule Management Security Detection Rule Management Team labels May 26, 2023
@elasticmachine
Copy link
Contributor

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

@MadameSheema MadameSheema assigned banderror and unassigned ghost May 26, 2023
@banderror banderror changed the title [Security Solution]User is able to schedule the snooze in the past time with timezone conversion. [RAM][Security Solution]User is able to schedule the snooze in the past time with timezone conversion. May 26, 2023
@banderror banderror added Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) Feature:Rule Management Security Solution Detection Rule Management area Feature:Alerting/RulesManagement Issues related to the Rules Management UX and removed triage_needed labels May 26, 2023
@elasticmachine
Copy link
Contributor

Pinging @elastic/response-ops (Team:ResponseOps)

@banderror banderror removed their assignment May 26, 2023
@banderror
Copy link
Contributor

cc @elastic/response-ops-ram @XavierM

@pborgonovi
Copy link
Contributor

pborgonovi commented Jul 30, 2024 •
edited
Loading

Validated on 8.14 BC:

image

@cnasikas cnasikas added the response-ops-mx-backlog ResponseOps MX backlog label Oct 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@JiaweiWu JiaweiWu

Labels
bug Fixes for quality problems that affect the customer experience Feature:Alerting/RulesManagement Issues related to the Rules Management UX Feature:Rule Management Security Solution Detection Rule Management area impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. response-ops-mx-backlog ResponseOps MX backlog Team:Detection Rule Management Security Detection Rule Management Team Team:Detections and Resp Security Detection Response Team Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.
Projects
No open projects
AppEx: ResponseOps - Rules & Alerts Management
Status: No status
Milestone
No milestone
Development

No branches or pull requests
7 participants
@banderror @cnasikas @elasticmachine @MadameSheema @JiaweiWu @sukhwindersingh-qasource @pborgonovi