-
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
[8.0][RAC] 117686 replace alert workflow status in alerts view #118723
[8.0][RAC] 117686 replace alert workflow status in alerts view #118723
Conversation
a8a8e8f
to
553dc0c
Compare
553dc0c
to
b17d8db
Compare
2c609ef
to
80132a3
Compare
@elasticmachine merge upstream |
@elasticmachine merge upstream |
merge conflict between base and head |
@@ -330,7 +320,7 @@ const FIELDS_WITHOUT_CELL_ACTIONS = [ | |||
]; | |||
|
|||
export function AlertsTableTGrid(props: AlertsTableTGridProps) { | |||
const { indexNames, rangeFrom, rangeTo, kuery, workflowStatus, setRefetch, addToQuery } = props; | |||
const { indexNames, rangeFrom, rangeTo, kuery, workflowStatus, setRefetch } = props; |
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.
@fkanout We should delete workflowStatus
from here. There are probably a few more places that workflowStatus might need to be deleted as well. This is not needed, since we are not filtering by workflowStatus anymore in the UI. That's why we still see workflowStatus:open
in the urlbar when we first load the page. This is not needed anymore
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.
Same as here:
#118723 (comment)
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.
Removing workflowStatus
It will blocked by TGridStandaloneCompProps
requires filterStatus
. Because the value of filterStatus
is workflowStatus
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.
@fkanout filterStatus at the moment has value workflowStatus
, but nothing prevents us by changing it back to alert status. This change was introduced as part of this PR #109817, so we could pair together to manually revert some workflows status leftover that is not needed
Let's get this PR merged for now. I summarized later on in a comment what we discussed during our sync up.
@fkanout Great work on that PR and thanks a lot for the detailed use cases! I like how you synced the search bar with the url bar. I still see I understand that you left a few parts in the code on purpose, in case we bring back workflow status filtering. Let's quickly sync up tomorrow regarding what things can stay and what could be removed (for example workflowStatus from the urlbar). |
@ersin-erdal I totally agree. Could you maybe create a ticket to track down this code improvement you suggested? We could add the label |
Btw FYI here's the PR that replaced status filtering with workflow status filtering https://github.com/elastic/kibana/pull/109817/files. And now we are replacing it again. Maybe this is a hint that we should have an AlertsFilter container as @ersin-erdal suggested |
@elasticmachine merge upstream |
@elasticmachine merge upstream |
💚 Build Succeeded
Metrics [docs]Module Count
Async chunks
Page load bundle
History
To update your PR or re-run it, just comment with: cc @fkanout |
@fkanout As discussed we can merge this PR. I summarize what we discussed:
|
After team discussion, a separate issue will be created to clean up the workflow code. |
Friendly reminder: Looks like this PR hasn’t been backported yet. |
…ic#118723) * Add AlertStatus types * Add alert status filter component * Remove Filter in action from the t grid table * Update group buttons to applied Alert status filter instead of Workflow status * Keep the Alert status button in sync when typing and first page load * Fix data test object name and translation keys label * Add possibility to hide the bulk actions * Update how hide the bulk actions * Fix showCheckboxes hardcoded "true". Instead use the leadingControlColumns props * Hide the leading checkboxes in the T Grid with the bulk actions * Update showCheckboxes to false * Fix test as the leading checkboxes are hidden * Update tests * Get back disabledCellActions as it's required by T Grid * Update tests to skip test related to Workflow action buttons * Skip workflow tests * Revert fix showCheckboxes * Remove unused imports * Revert the o11y tests as the checkBoxes fix is reverted * Reactive the tests effected by checkBoxes * Skip alert workflow status * [Code review] use predefined types * Remove unused prop * Use the alert-data index name in the RegEx * Detect * in KQL as "show al"l alert filter Co-authored-by: Kibana Machine <[email protected]>
…) (#120198) * Add AlertStatus types * Add alert status filter component * Remove Filter in action from the t grid table * Update group buttons to applied Alert status filter instead of Workflow status * Keep the Alert status button in sync when typing and first page load * Fix data test object name and translation keys label * Add possibility to hide the bulk actions * Update how hide the bulk actions * Fix showCheckboxes hardcoded "true". Instead use the leadingControlColumns props * Hide the leading checkboxes in the T Grid with the bulk actions * Update showCheckboxes to false * Fix test as the leading checkboxes are hidden * Update tests * Get back disabledCellActions as it's required by T Grid * Update tests to skip test related to Workflow action buttons * Skip workflow tests * Revert fix showCheckboxes * Remove unused imports * Revert the o11y tests as the checkBoxes fix is reverted * Reactive the tests effected by checkBoxes * Skip alert workflow status * [Code review] use predefined types * Remove unused prop * Use the alert-data index name in the RegEx * Detect * in KQL as "show al"l alert filter Co-authored-by: Kibana Machine <[email protected]> Co-authored-by: Kibana Machine <[email protected]>
…ic#118723) * Add AlertStatus types * Add alert status filter component * Remove Filter in action from the t grid table * Update group buttons to applied Alert status filter instead of Workflow status * Keep the Alert status button in sync when typing and first page load * Fix data test object name and translation keys label * Add possibility to hide the bulk actions * Update how hide the bulk actions * Fix showCheckboxes hardcoded "true". Instead use the leadingControlColumns props * Hide the leading checkboxes in the T Grid with the bulk actions * Update showCheckboxes to false * Fix test as the leading checkboxes are hidden * Update tests * Get back disabledCellActions as it's required by T Grid * Update tests to skip test related to Workflow action buttons * Skip workflow tests * Revert fix showCheckboxes * Remove unused imports * Revert the o11y tests as the checkBoxes fix is reverted * Reactive the tests effected by checkBoxes * Skip alert workflow status * [Code review] use predefined types * Remove unused prop * Use the alert-data index name in the RegEx * Detect * in KQL as "show al"l alert filter Co-authored-by: Kibana Machine <[email protected]>
Summary
This PR fixes #118078, fixes #117686 by:
EuiButtonGroup
to show "Alert status" instead. i.e. "Open / Acknowledged / Closed", we'll have "Show all / Active / Recovered" instead.Hide "Mark as Acknowledged", "Mark as Closed", and "Mark as Open" from the action list in the alerts table.
Hide the alerts' leading checkboxes that provide bulk actions with "Mark as Acknowledged", "Mark as Closed", and "Mark as Open".This PR can't fulfill "hide the alerts' leading checkboxes" requirements, as there is a bug in the T Grid. (please check this issue for more details).
Keep sync the selected alert filter buttons with the rest of the Alerts page (see the expected behavior section).
Expected behavior:
To ease the PR test for the reviewer, here are the use cases that could be tested:
Checklist
Delete any items that are not applicable to this PR.
Risk Matrix
Delete this section if it is not applicable to this PR.
Before closing this PR, invite QA, stakeholders, and other developers to identify risks that should be tested prior to the change/feature release.
When forming the risk matrix, consider some of the following examples and how they may potentially impact the change:
For maintainers