-
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 SOLUTIONS][Case Everywhere] Move All Case page #92423
Comments
Pinging @elastic/security-threat-hunting (Team:Threat Hunting) |
Pinging @elastic/security-solution (Team: SecuritySolution) |
This will also allows us to remove modal logic inside the all cases page. The modal should be built by smaller components and apply its logic when needed. |
Are they though? There is specific details on both of these pages, which has changed just about every release. We should make these components so everyone consuming the UI has the updates |
The component has been migrated to the cases plugin on our current feature branch: https://github.com/elastic/kibana/tree/cases_rac_ui
|
Closing as these changes were merged in as part of the larger cases-ui effort here: |
We need to move all the components of the all cases page inside of Case plugins and shared them through our case plugin. We are thinking to extract components one by one to allow different design if needed by solution who wants to integrate case.
AC:
###To discuss with engineer: ###
I do not think that we need to create specific component for
Edit external connection
and/orCreate Case
because these two component are all about re-routing to a specific pageTC:
The text was updated successfully, but these errors were encountered: