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

Persist filter from asset list view when clicking into lineage view #21665

Open
brandonpeebles opened this issue May 6, 2024 · 0 comments
Open
Labels
area: UI/UX Related to User Interface and User Experience type: feature-request

Comments

@brandonpeebles
Copy link
Contributor

What's the use case?

The new Catalog view page is really user-friendly and makes it even faster to navigate our assets. I often prefer to use the lineage view when exploring assets. This would enable users who prefer this view of their DAG to make better use of the Catalog landing page.

Ideas of implementation

Main implementation idea:
It would be great if when I click on a filter (such as the dbt compute kind tag below), and then click on the "View global asset lineage" that it persists the same filter. Currently, I have to apply any filtering after navigating into this view.
image

Alternative idea or additional feature:
Add a User setting that lets us decide whether we want to default to the list view or lineage view when clicking into the Catalog tab. For example, if toggled to default to lineage view, then when I click on the dbt compute tag above I would immediately be taken to the global asset lineage page with that filter applied. At the top right could then be a button/link that takes you back to the list view with the same filter applied.

Additional information

No response

Message from the maintainers

Impacted by this issue? Give it a 👍! We factor engagement into prioritization.

@garethbrickman garethbrickman added the area: UI/UX Related to User Interface and User Experience label May 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: UI/UX Related to User Interface and User Experience type: feature-request
Projects
Status: Later
Development

No branches or pull requests

2 participants