-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[Security Solution][RAC] Remove in-progress type guards once migration is complete #109030
Comments
Pinging @elastic/security-solution (Team: SecuritySolution) |
Pinging @elastic/security-threat-hunting (Team:Threat Hunting) |
@karanbirsingh-qasource please validate the following fix when BC1 is available. Thanks. |
|
I don't believe this has been fixed yet unless there's a been a PR submitted I don't know about, we still have the type guards in master |
Pinging @elastic/security-detections-response (Team:Detections and Resp) |
we have validated the linked pr fix on the 7.15.0 BC1 and below are there observations. Build Details:
[RAC] Enable workflow status filtering
Mentioned filter naming is there is Alert page , Individual Rule Page
Question : can you confirm below highlighted areas will have Workflow status or only status ❓
Question: Can you please share more details for above point , as per our observation same alert status seen on UI will be present in alert document , so how we will set each alert workflow status to "open" ❓ [Security Solution][Detection Alerts] Changes in-progress status to acknowledged
[RAC][Observability] Add status update actions in row menuBlocked 🟣 to test above ticket due to this issue #108164 |
Closing as discussed with @dplumlee - old alerts can still have |
With the RAC work being done, we have decided to accept both
in-progress
(old) andacknowledged
(new) values for thestatus
field on alerts. Once the RAC migrations have taken place we need to remove the unused type guards in the code listed in these PR's as well as any other loose, untracked uses.#108215
#107972
#108698
The text was updated successfully, but these errors were encountered: