-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[RAM] Cases bulk actions & column improvements #151761
Conversation
923b2f5
to
794081d
Compare
close: () => void; | ||
}; | ||
|
||
export interface CasesService { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When a case package is created these types will be imported from the package.
@@ -0,0 +1,35 @@ | |||
/* |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I created an issue to create a package with Cases mocks to remove this file and import the Case UI Service mock from the package.
@elasticmachine merge upstream |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, tested locally and works fine!
@elasticmachine merge upstream |
@elasticmachine merge upstream |
@elasticmachine merge upstream |
@elasticmachine merge upstream |
@elasticmachine merge upstream |
@elasticmachine merge upstream |
@elasticmachine run elasticsearch-ci/docs |
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]Module Count
Async chunks
Public APIs missing exports
Page load bundle
Unknown metric groupsESLint disabled line counts
Total ESLint disabled count
History
To update your PR or re-run it, just comment with: cc @cnasikas |
## Summary This PR: - Moves the case bulk actions from the solutions to the alert table - Refetch when using the case row actions & the case bulk actions. - Renames the `kibana.alert.case_ids` label to `Cases` - Unskip the `alerts_table.test.tsx` test file and skip the individual flaky tests. I run the test file 60 times in the CI without any issues (elastic@9efed89) - Renames the cases flyout and modal hook from `get*` to `use*` Fixes: elastic#151688 ## Userflow ## Testing ### Alerts table - The alerts table does not show the Cases column by default - You can choose the case column from the fields modal. Type `Case` to find the cases column - The label of the column is `Cases` - The label of the field in the fields modal is `Cases` - You can bulk attach alerts to a new case - You can bulk attach alerts to an existing case - When bulk attaching alerts to a case the alerts table re-fetches the data - When attaching an alert to a case from the row actions the alerts table re-fetches the data ### Case integrations outside the alerts table - Ensure that you can attach your data to a case (existing and new) ### Checklist Delete any items that are not applicable to this PR. - [x] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md) - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios ### For maintainers - [x] This was checked for breaking API changes and was [labeled appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) --------- Co-authored-by: Kibana Machine <[email protected]>
Summary
This PR:
kibana.alert.case_ids
label toCases
alerts_table.test.tsx
test file and skip the individual flaky tests. I run the test file 60 times in the CI without any issues (9efed89)get*
touse*
Fixes: #151688
Userflow
Testing
Alerts table
Case
to find the cases columnCases
Cases
Case integrations outside the alerts table
Checklist
Delete any items that are not applicable to this PR.
For maintainers