Skip to content

[Data set quality] Allow edit failure store#233858

Merged
SoniaSanzV merged 8 commits intoelastic:mainfrom
SoniaSanzV:data_quality/allow_edit_failure_store
Sep 5, 2025
Merged

[Data set quality] Allow edit failure store#233858
SoniaSanzV merged 8 commits intoelastic:mainfrom
SoniaSanzV:data_quality/allow_edit_failure_store

Conversation

@SoniaSanzV
Copy link
Contributor

@SoniaSanzV SoniaSanzV commented Sep 3, 2025

Closes #231848

Summary

With #231846 we introduced the possibility for the users to enabling failure store from the data quality plugin, but they couldn't edit or disable it from there. With this PR, we introduce the option of editing failure store from data set quality.

How to test

  • Go to data quality plugin
  • Select a data set
  • Enable the failure store if disabled
  • Click the failure store card
  • Click the new pen icon
  • Verify the failure store modal opens
  • Verify that you can edit data and disable the failure store

Note: Despite that in the mocks the icon is on the left, I add it to the right so the discover button is consisten with the one that the other card enables.

Mocks

image

@SoniaSanzV SoniaSanzV requested a review from a team as a code owner September 3, 2025 13:00
@SoniaSanzV SoniaSanzV self-assigned this Sep 3, 2025
@SoniaSanzV SoniaSanzV added Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more t// release_note:skip Skip the PR/issue when compiling release notes backport:skip This PR does not require backporting Feature:Streams This is the label for the Streams Project labels Sep 3, 2025
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-management (Team:Kibana Management)

@yngrdyn yngrdyn self-requested a review September 4, 2025 09:59
/>
</EuiToolTip>
)}
{displayEditFailureStore && canUserReadFailureStore && (
Copy link
Contributor

@yngrdyn yngrdyn Sep 4, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would canUserReadFailureStore be enough for enabling/disabling/updating failure store?
afaik we have read_failure_store and manage_failure_store, shouldn't all these actions tight to manage_failure_store?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Addressed in cc1804d

lastReloadTime={lastReloadTime}
displayCreateRuleButton={selectedQualityCard === 'degraded'}
openAlertFlyout={openAlertFlyout}
displayEditFailureStore={selectedQualityCard === 'failed'}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[nit] we could group the display features into one property, e.g.

actions: {
   createRule,
   editFailureStore,
}

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Addressed in cc1804d

@SoniaSanzV SoniaSanzV force-pushed the data_quality/allow_edit_failure_store branch from 57479c5 to cc1804d Compare September 4, 2025 15:17
Copilot AI review requested due to automatic review settings September 5, 2025 06:11
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR enables editing and disabling of failure store functionality from the dataset quality plugin. Previously, users could only enable failure store from the plugin but couldn't modify or disable it.

Key changes:

  • Introduces a new canManageFailureStore privilege to control edit permissions
  • Adds an edit button (pencil icon) to the failure store card in the document trends section
  • Creates a reusable failure store modal hook for managing modal state and operations

Reviewed Changes

Copilot reviewed 19 out of 19 changed files in this pull request and generated 2 comments.

Show a summary per file
File Description
x-pack/platform/plugins/shared/dataset_quality/common/constants.ts Adds new MANAGE_FAILURE_STORE_PRIVILEGE constant
x-pack/platform/plugins/shared/dataset_quality/common/api_types.ts Updates API types to include canManageFailureStore privilege
x-pack/platform/plugins/shared/dataset_quality/server/services/privileges.ts Updates privilege service to check manage failure store permissions
x-pack/platform/plugins/shared/dataset_quality/server/routes/data_streams/ Updates data stream routes to include manage failure store privilege
x-pack/platform/plugins/shared/dataset_quality/public/hooks/use_failure_store_modal.ts New hook for managing failure store modal state and operations
x-pack/platform/plugins/shared/dataset_quality/public/components/dataset_quality_details/overview/ Updates UI components to display edit button and use new modal hook
x-pack/platform/plugins/shared/dataset_quality/public/state_machines/ Fixes condition check for failure store updates
Test files Adds comprehensive test coverage for the new edit functionality

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id before after diff
datasetQuality 842 843 +1

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id before after diff
datasetQuality 437.3KB 438.6KB +1.3KB

History

cc @SoniaSanzV

Copy link
Contributor

@yngrdyn yngrdyn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good job 🔥

@SoniaSanzV SoniaSanzV enabled auto-merge (squash) September 5, 2025 19:09
@SoniaSanzV SoniaSanzV merged commit b01b9a9 into elastic:main Sep 5, 2025
12 checks passed
shahargl pushed a commit to shahargl/kibana that referenced this pull request Sep 7, 2025
Closes elastic#231848

## Summary
With elastic#231846 we introduced the
possibility for the users to enabling failure store from the data
quality plugin, but they couldn't edit or disable it from there. With
this PR, we introduce the option of editing failure store from data set
quality.

### How to test
* Go to data quality plugin
* Select a data set
* Enable the failure store if disabled
* Click the failure store card
* Click the new pen icon
* Verify the failure store modal opens
* Verify that you can edit data and disable the failure store

Note: Despite that in the mocks the icon is on the left, I add it to the
right so the discover button is consisten with the one that the other
card enables.

### Mocks
<img width="1846" height="690" alt="image"
src="https://github.com/user-attachments/assets/3069ae8c-b276-487a-9104-106f4adfa948"
/>

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
KodeRad pushed a commit to KodeRad/kibana that referenced this pull request Sep 15, 2025
Closes elastic#231848

## Summary
With elastic#231846 we introduced the
possibility for the users to enabling failure store from the data
quality plugin, but they couldn't edit or disable it from there. With
this PR, we introduce the option of editing failure store from data set
quality.

### How to test
* Go to data quality plugin
* Select a data set
* Enable the failure store if disabled
* Click the failure store card
* Click the new pen icon
* Verify the failure store modal opens
* Verify that you can edit data and disable the failure store

Note: Despite that in the mocks the icon is on the left, I add it to the
right so the discover button is consisten with the one that the other
card enables.

### Mocks
<img width="1846" height="690" alt="image"
src="https://github.com/user-attachments/assets/3069ae8c-b276-487a-9104-106f4adfa948"
/>

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
CAWilson94 pushed a commit to CAWilson94/kibana that referenced this pull request Sep 24, 2025
Closes elastic#231848

## Summary
With elastic#231846 we introduced the
possibility for the users to enabling failure store from the data
quality plugin, but they couldn't edit or disable it from there. With
this PR, we introduce the option of editing failure store from data set
quality.

### How to test
* Go to data quality plugin
* Select a data set
* Enable the failure store if disabled
* Click the failure store card
* Click the new pen icon
* Verify the failure store modal opens
* Verify that you can edit data and disable the failure store

Note: Despite that in the mocks the icon is on the left, I add it to the
right so the discover button is consisten with the one that the other
card enables.

### Mocks
<img width="1846" height="690" alt="image"
src="https://github.com/user-attachments/assets/3069ae8c-b276-487a-9104-106f4adfa948"
/>

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
niros1 pushed a commit that referenced this pull request Sep 30, 2025
Closes #231848

## Summary
With #231846 we introduced the
possibility for the users to enabling failure store from the data
quality plugin, but they couldn't edit or disable it from there. With
this PR, we introduce the option of editing failure store from data set
quality.

### How to test
* Go to data quality plugin
* Select a data set
* Enable the failure store if disabled
* Click the failure store card
* Click the new pen icon
* Verify the failure store modal opens
* Verify that you can edit data and disable the failure store

Note: Despite that in the mocks the icon is on the left, I add it to the
right so the discover button is consisten with the one that the other
card enables.

### Mocks
<img width="1846" height="690" alt="image"
src="https://github.com/user-attachments/assets/3069ae8c-b276-487a-9104-106f4adfa948"
/>

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
@SoniaSanzV SoniaSanzV deleted the data_quality/allow_edit_failure_store branch October 1, 2025 12:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport:skip This PR does not require backporting Feature:Streams This is the label for the Streams Project release_note:skip Skip the PR/issue when compiling release notes Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more t// v9.2.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Streams] Edit failure store button

5 participants