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.

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

[8.8] [Security Solution] Able to add Same Start Time and End Time in Schedule for Snooze Notifications of Rule (#158565) #159331

Merged
merged 1 commit into from
Jun 8, 2023

Conversation

kibanamachine
Copy link
Contributor

Backport

This will backport the following commits from main to 8.8:

Questions ?

Please refer to the Backport tool documentation

…ule for Snooze Notifications of Rule (elastic#158565)

## What does this PR do?
* It doesn't allows the user to pick the same date and time in the
schedule component.

## Issue References
* Client: elastic#157865

## Video/Screenshot Demo

###### FIX:
https://www.loom.com/share/fc4a43eba71f485384621ecec457ce1a

---
This code was written and reviewed by GitStart Community. Growing great
engineers, one PR at a time.

Co-authored-by: KlingerMatheus <[email protected]>
Co-authored-by: gitstart_bot <[email protected]>
(cherry picked from commit d9eff3f)
@kibana-ci
Copy link
Collaborator

💚 Build Succeeded

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id before after diff
triggersActionsUi 1.4MB 1.4MB +22.0B
Unknown metric groups

ESLint disabled line counts

id before after diff
enterpriseSearch 17 19 +2
securitySolution 400 404 +4
total +6

Total ESLint disabled count

id before after diff
enterpriseSearch 18 20 +2
securitySolution 480 484 +4
total +6

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

@kibanamachine kibanamachine merged commit 97bb42c into elastic:8.8 Jun 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants