Skip to content
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.13] [8.13] Data Quality persistence (backport #4953) #4984

Merged
merged 1 commit into from
Mar 25, 2024

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Mar 25, 2024

Fixes #4807 by updating the data quality dashboard doc to inform users about the updates which make the data quality information persist between sessions and across users.

Preview: Data quality dashboard


This is an automatic backport of pull request #4953 done by Mergify.

* describes data quality persistence

* updates screenshots with new UI elements

* Update docs/dashboards/data-quality-dashboard.asciidoc

Co-authored-by: Nastasha Solomon <[email protected]>

* Update docs/dashboards/data-quality-dashboard.asciidoc

Co-authored-by: Nastasha Solomon <[email protected]>

* adds detail about where data is saved

* adds definition of a space

* Update docs/dashboards/data-quality-dashboard.asciidoc

Co-authored-by: Sergi Massaneda <[email protected]>

* Update data-quality-dashboard.asciidoc

grammar change

* incorporate's dhru's feedback minus screenshot work

* updates images with Dhru's feedback

* incorporates Joe's feedback

---------

Co-authored-by: Nastasha Solomon <[email protected]>
Co-authored-by: Sergi Massaneda <[email protected]>
Co-authored-by: Dhrumil Patel <[email protected]>
(cherry picked from commit 83437a8)
@mergify mergify bot requested a review from a team as a code owner March 25, 2024 17:16
@mergify mergify bot added the backport label Mar 25, 2024
Copy link

A documentation preview will be available soon.

Request a new doc build by commenting
  • Rebuild this PR: run docs-build
  • Rebuild this PR and all Elastic docs: run docs-build rebuild

run docs-build is much faster than run docs-build rebuild. A rebuild should only be needed in rare situations.

If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here.

@benironside benironside merged commit 5b80b2f into 8.13 Mar 25, 2024
4 checks passed
@mergify mergify bot deleted the mergify/bp/8.13/pr-4953 branch March 25, 2024 20:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant