Skip to content

Feat: Adding task-level filters to DAG view in graph tab#64271

Open
itayweb wants to merge 26 commits intoapache:mainfrom
itayweb:add-task-level-filters
Open

Feat: Adding task-level filters to DAG view in graph tab#64271
itayweb wants to merge 26 commits intoapache:mainfrom
itayweb:add-task-level-filters

Conversation

@itayweb
Copy link
Copy Markdown
Contributor

@itayweb itayweb commented Mar 26, 2026

Adding new task-level filters to use on DAG view graph tab

task level filters demo

Was generative AI tooling used to co-author this PR?
  • Yes (please specify the tool below)

Generated-by: Claude Code following the guidelines

@bbovenzi
Copy link
Copy Markdown
Contributor

The other filters in this dropdown are backend. So let's not mix the two.

I wonder if this would be better to detect the ctrl-f hotkey, give these search params and a user can tab through the matching tasks

@bbovenzi bbovenzi added this to the Airflow 3.3.0 milestone Mar 31, 2026
@itayweb
Copy link
Copy Markdown
Contributor Author

itayweb commented Mar 31, 2026

The other filters in this dropdown are backend. So let's not mix the two.

I wonder if this would be better to detect the ctrl-f hotkey, give these search params and a user can tab through the matching tasks

Oh I see.. do you prefer I'll move the new filters I've added to the options button?
Regarding the ctrl-f, you meant user can search operators/status/etc.. and it will auto filter the dag view?

@bbovenzi
Copy link
Copy Markdown
Contributor

bbovenzi commented Mar 31, 2026

The other filters in this dropdown are backend. So let's not mix the two.
I wonder if this would be better to detect the ctrl-f hotkey, give these search params and a user can tab through the matching tasks

Oh I see.. do you prefer I'll move the new filters I've added to the options button? Regarding the ctrl-f, you meant user can search operators/status/etc.. and it will auto filter the dag view?

I don't want to throw more in the setting dropdown. I think we need to rethink the UX given all the features to navigate both the grid, gantt and graph are now. This could be its own Search Icon button perhaps?

And yes, if you already focused on the graph view then ctrl-f will also open that search

@potiuk potiuk added the ready for maintainer review Set after triaging when all criteria pass. label Apr 1, 2026
@kaxil kaxil requested a review from Copilot April 2, 2026 00:43
@itayweb
Copy link
Copy Markdown
Contributor Author

itayweb commented Apr 5, 2026

The other filters in this dropdown are backend. So let's not mix the two.
I wonder if this would be better to detect the ctrl-f hotkey, give these search params and a user can tab through the matching tasks

Oh I see.. do you prefer I'll move the new filters I've added to the options button? Regarding the ctrl-f, you meant user can search operators/status/etc.. and it will auto filter the dag view?

I don't want to throw more in the setting dropdown. I think we need to rethink the UX given all the features to navigate both the grid, gantt and graph are now. This could be its own Search Icon button perhaps?

And yes, if you already focused on the graph view then ctrl-f will also open that search

Done 👍

Copy link
Copy Markdown
Contributor

@bbovenzi bbovenzi left a comment

Choose a reason for hiding this comment

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

Can you also update the screenshot to reflect the latest changes? Also, I'd love to see a video or gif.

Copy link
Copy Markdown
Contributor

@bbovenzi bbovenzi left a comment

Choose a reason for hiding this comment

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

A bunch of small edits. But the major change I would like to see is to reduce the number of times we are walking through the dag structure's nested NodeResponse. We already do it for useOpenGroups. The best approach is probably to rename that useGroups() and have that hook handle all of these actions, because then we could have the same functionality happen in the grid view too.

@bbovenzi
Copy link
Copy Markdown
Contributor

bbovenzi commented Apr 9, 2026

Actually the performance looks fine for now while we need to do virtualization for the graph view.

In manual testing, the only issue I noticed was that the filters were also filtering the task instances list on the right hand side of the page. We should make the search param keys different. Maybe later we can make this all integrated but that is much more work.

Copy link
Copy Markdown
Contributor

@bbovenzi bbovenzi left a comment

Choose a reason for hiding this comment

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

Looking better. Two comments

@kaxil kaxil requested a review from Copilot April 10, 2026 19:55
Copy link
Copy Markdown
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.

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:translations area:UI Related to UI/UX. For Frontend Developers. ready for maintainer review Set after triaging when all criteria pass. translation:default translation:he

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Filters] Add task-level filters to DAG View - Graph tab

5 participants