-
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
Failing test: Jest Tests.x-pack/plugins/triggers_actions_ui/public/application/sections/alerts_table - AlertsTable Alerts table UI actions column row loading state on action should show the row loader when callback triggered #151688
Labels
failed-test
A test failure on a tracked branch, potentially flaky-test
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
Comments
kibanamachine
added
the
failed-test
A test failure on a tracked branch, potentially flaky-test
label
Feb 21, 2023
kibanamachine
added
the
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
label
Feb 21, 2023
Pinging @elastic/response-ops (Team:ResponseOps) |
New failure: CI Build - main |
New failure: CI Build - main |
New failure: CI Build - main |
jbudz
added a commit
that referenced
this issue
Feb 21, 2023
Skipped main: 144df81 |
New failure: CI Build - main |
New failure: CI Build - main |
3 tasks
cnasikas
added a commit
that referenced
this issue
Mar 29, 2023
## 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 (9efed89) - Renames the cases flyout and modal hook from `get*` to `use*` Fixes: #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]>
jgowdyelastic
pushed a commit
to jgowdyelastic/kibana
that referenced
this issue
Mar 30, 2023
## 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]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
failed-test
A test failure on a tracked branch, potentially flaky-test
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
A test failed on a tracked branch
First failure: CI Build - main
The text was updated successfully, but these errors were encountered: