[Data set quality] Implement FS modal in data quality table#239916
[Data set quality] Implement FS modal in data quality table#239916SoniaSanzV merged 9 commits intoelastic:mainfrom
Conversation
SoniaSanzV
added
Team:Kibana Management
|
Pinging @elastic/kibana-management (Team:Kibana Management) |
| name: failedDocsColumnName, | ||
| 'data-test-subj': 'datasetQualityFailedPercentageColumn', |
There was a problem hiding this comment.
Not directly related with this issue but it has been changed to avoid this console error:
Warning: validateDOMNesting(...): Text nodes cannot appear as a child of <tr>.
| name: degradedDocsColumnName, | ||
| 'data-test-subj': 'datasetQualityPercentageColumn', |
There was a problem hiding this comment.
Not directly related with this issue but it has been changed to avoid this console error:
Warning: validateDOMNesting(...): Text nodes cannot appear as a child of <tr>.
| name: datasetQualityColumnName, | ||
| 'data-test-subj': 'datasetQualityQualityColumn', |
There was a problem hiding this comment.
Not directly related with this issue but it has been changed to avoid this console error:
Warning: validateDOMNesting(...): Text nodes cannot appear as a child of <tr>.
| name: sizeColumnName, | ||
| 'data-test-subj': 'datasetQualitySizeColumn', |
There was a problem hiding this comment.
Not directly related with this issue but it has been changed to avoid this console error:
Warning: validateDOMNesting(...): Text nodes cannot appear as a child of <tr>.
| name: nameColumnName, | ||
| 'data-test-subj': 'datasetQualityNameColumn', |
There was a problem hiding this comment.
Not directly related with this issue but it has been changed to avoid this console error:
Warning: validateDOMNesting(...): Text nodes cannot appear as a child of <tr>.
| name: namespaceColumnName, | ||
| 'data-test-subj': 'datasetQualityNamespaceColumn', |
There was a problem hiding this comment.
Not directly related with this issue but it has been changed to avoid this console error:
Warning: validateDOMNesting(...): Text nodes cannot appear as a child of <tr>.
|
Not sure if we should backport this at all, @LucaWintergerst, @flash1293 @gbamparop wdyt? |
|
/oblt-deploy |
|
I don't think we need to backport, but curious if Joe or Giorgos think differently |
|
Starting backport for target branches: 9.2 https://github.com/elastic/kibana/actions/runs/19338448694 |
💚 Build Succeeded
Metrics [docs]Module Count
Public APIs missing comments
Async chunks
Public APIs missing exports
Page load bundle
History
cc @SoniaSanzV |
…239916) Closes elastic#232736 ## Summary In elastic#231846 we implemented the failure store modal in the Data set detail page but the main page still redirects to Index Management.This PR implements new modal also in the Data quality main page. https://github.com/user-attachments/assets/93d5ae87-ad5b-4f18-b271-185c05691ddb --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> (cherry picked from commit b625245)
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
SoniaSanzV
added
backport:skip
…239916) Closes elastic#232736 ## Summary In elastic#231846 we implemented the failure store modal in the Data set detail page but the main page still redirects to Index Management.This PR implements new modal also in the Data quality main page. https://github.com/user-attachments/assets/93d5ae87-ad5b-4f18-b271-185c05691ddb --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
5 participants
Closes #232736
Summary
In #231846 we implemented the failure store modal in the Data set detail page but the main page still redirects to Index Management.This PR implements new modal also in the Data quality main page.
Screen.Recording.2025-10-21.at.15.27.01.mov