[RAM] Update Rule Status - UI Changes#144466
Conversation
…-ref HEAD~1..HEAD --fix'
…-ref HEAD~1..HEAD --fix'
|
Initial tests don't reveal anything yet. Just confirming some tests are underway. :) |
x-pack/plugins/triggers_actions_ui/public/application/lib/rule_api/map_filters_to_kuery_node.ts
Show resolved
Hide resolved
...ctions_ui/public/application/sections/rule_details/components/rule_event_log_list_status.tsx
Outdated
Show resolved
Hide resolved
...s/triggers_actions_ui/public/application/sections/rules_list/components/rules_list_table.tsx
Outdated
Show resolved
Hide resolved
...ctions_ui/public/application/sections/rules_list/components/rule_last_run_outcome_filter.tsx
Show resolved
Hide resolved
...plugins/triggers_actions_ui/public/application/sections/rules_list/components/rules_list.tsx
Outdated
Show resolved
Hide resolved
...riggers_actions_ui/public/application/sections/rules_list/components/rules_list_statuses.tsx
Outdated
Show resolved
Hide resolved
This comment was marked as resolved.
This comment was marked as resolved.
| if (!prevValue) { | ||
| const rulesToExpand = rulesState.data.reduce((acc, ruleItem) => { | ||
| if (ruleItem.executionStatus.status === 'error') { | ||
| if (ruleItem.lastRun?.outcome === RuleLastRunOutcomeValues[2]) { |
There was a problem hiding this comment.
Should we check the feature flag and have two conditions instead of one or just a OR
x-pack/plugins/triggers_actions_ui/public/common/lib/rule_status_helpers.ts
Show resolved
Hide resolved
| }); | ||
| await refreshAlertsList(); | ||
| await find.waitForDeletedByCssSelector('.euiBasicTable-loading'); | ||
| await testSubjects.click('ruleExecutionStatusFilterButton'); |
There was a problem hiding this comment.
@JiaweiWu and I talked more about it and we think we should add a new config file to allow this test working when the feature flag is off. We will create an issue to add back this test until the feature flag exists
|
While testing the experimental flags I noticed we have a small bug in our experimental features getters. I will create an issue and work on that immediately after FF (#145300) |
|
@elasticmachine merge upstream |
XavierM
left a comment
There was a problem hiding this comment.
LGTM, so glad to see this PR getting merged! Thanks a lot for your help on this one!
|
@elasticmachine merge upstream |
|
@elasticmachine merge upstream |
💚 Build Succeeded
Metrics [docs]Module Count
Async chunks
Page load bundle
Unknown metric groupsESLint disabled in files
ESLint disabled line counts
Total ESLint disabled count
History
To update your PR or re-run it, just comment with: |
## Summary In the PR that updated and consolidated rule status (#144466). The new helper that was added had references to translations, which increased the `triggers_actions_ui` bundle size by quite a bit. This PR refactors the helper so we're passing in the translations. It seems like a good compromise to allow some logic reuse but without the massive bundle increase. ### Checklist - [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 Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Summary
Parent issue for updating rule status: #136039
Frontend issue: #145191
Backend PR: #140882
Updates the rules list and rules details page to support the new consolidated statuses. With E2E and unit testing.
Rules list:
Rule details:
Checklist