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

[Dataset quality] [Doc] Migration of Dataset Quality Flyout to a Page #4149

Closed
achyutjhunjhunwala opened this issue Aug 14, 2024 · 0 comments · Fixed by #4199
Closed

[Dataset quality] [Doc] Migration of Dataset Quality Flyout to a Page #4149

achyutjhunjhunwala opened this issue Aug 14, 2024 · 0 comments · Fixed by #4199

Comments

@achyutjhunjhunwala
Copy link
Contributor

achyutjhunjhunwala commented Aug 14, 2024

Description

We have recently started working on migrating the Dataset Quality Flyout to a Dedicated page.
Hence it would be great to have our docs updated too.

Why are we doing this change - Since we will be introducing more functionalities to individual Datasets, like Fix It flow, it is not possible to do everything in a flyout. Hence a dedicated page

Resources

This feature was implemented as part of multiple PRs

This feature was scoped as part of one of prerequisites for https://github.com/elastic/observability-dev/issues/3232

Figma Design - 1st Row

Which documentation set does this change impact?

Stateful and Serverless

Feature differences

The feature is identical in both

What release is this request related to?

8.16

Collaboration model

The documentation team

Point of contact.

Main contact: @achyutjhunjhunwala

Stakeholders: @gbamparop @yngrdyn

@mdbirnstiehl mdbirnstiehl self-assigned this Aug 14, 2024
@achyutjhunjhunwala achyutjhunjhunwala changed the title [Dataset quality] Migration of Dataset Quality Flyout to a Page [Dataset quality] [Doc] Migration of Dataset Quality Flyout to a Page Aug 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants