apache / apache/airflow

Add tab for asset groups and add allow filtering for asset tags and URIs

Open
#50,779 11 comments 0 reactions 0 assignees View on GitHub
area:UI kind:feature
Dominant language
Python
Stars
46.9k
Forks
17.8k
Avg merge
2d 7h
Merged PRs (30d)
484

Description

### Description

I think it would be useful to add a tab for asset groups which could be used to drill down into assets in the UI:

![Image](https://github.com/user-attachments/assets/58f496f1-c829-4fc3-ab3e-f63072dc5ad1)

For example, I could click on "gitlab" and then see a list of each asset in that group and ideally a dependency graph.

![Image](https://github.com/user-attachments/assets/be55b56d-6bc9-40d4-92f3-b308298b1d63)

Similar to the `DAGs` tab, the Asset Groups would show groups recently updated (and the status if possible?). The Asset page would be similar to what it is now and act as the `Task Instances` tab for individual asset updates.

1. Asset Group tab
2. Filter tags
3. Filter for URI

### Use case/motivation

I am heavily using asset-based scheduling right now but one thing which is lacking is a view into a data source as a whole. A single data source might consist of several assets (and DAGs) so it is not easy to understand exactly how many sources we are processing or the status of each source.

In the example above, there are assets for several layers of data which could be organized into a single asset group (I would rename the group to "gitlab_commits" so I could support additional endpoints like "gitlab_issues", "gitlab_users", etc). I would be able to see "gitab_commits" recently ran and the status of each asset was successful. With a filter for tags I could filter for "gitlab" to see all unique sources.

### Related issues

_No response_

### Are you willing to submit a PR?

- [ ] Yes I am willing to submit a PR!

### Code of Conduct

- [x] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the existing DAGs tab and Asset page, then map how asset groups, tags, URIs, statuses, and dependency graphs should fit together. Done means an Asset Groups tab supports drilling into grouped assets, tag and URI filtering, and the requested recent status view.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
data-engineering, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.