Reimplement #29226 for Airflow 3 UI | Filter tasks to Upstream and/or Downstream

[r-richmond]

Description

In the Airflow 2 UI #29226 added a feature where users could filter dags to be upstream and/or downstream from a specific task. This was very useful when debugging large dags.

However, in the heavy lift that was the new UI / Airflow 3.x this feature was dropped. This ticket is for the re-implementation of this feature in the Airflow 3 ui.

Screen shot of the feature in Airflow 2

Before Filter

After Filter (notice tasks limited to just those upstream & downstream of targeted task)

Note: Please add affected_version_3.0 label

Use case/motivation

A powerful / clean way to filter dags to specific tasks & their parents and/or children.

Related issues

Previous Issue: #28847
Previous Implementation: #29226

Are you willing to submit a PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[vikramkoka]

cc: @pierrejeambrun, @bbovenzi

Is this a duplicate with one of the "filter tasks created for the UI" created a couple of weeks ago?

[r-richmond]

Is this a duplicate with one of the "filter tasks created for the UI" created a couple of weeks ago?

I'm assuming you're referring to #53051 & #53048.

IMO I'd consider this ticket more of an additional requirement / separate. AKA I could see the above tickets being closed if filters for task_id, state, duration, etc were added. However, that wouldn't address this ticket's ask.

This ticket is specifically asking for the old functionality of filter to downstream and/or upstream of a specific task_instance to be added back to Airflow 3 the way it was present in Airflow 2.

[pierrejeambrun]

Yes, that would be nice to have that back in the next minor release. Marking for 3.1.0 hoping that someone would have time to take a look at this.

[Prasanth345]

Hi @r-richmond and @pierrejeambrun,

I’d like to work on this issue and reimplement the upstream/downstream task filter for the Airflow 3 UI.
I’ll start by reviewing the previous implementation from #29226 in Airflow 2.x and explore how it can be adapted to the current UI codebase.

Please let me know if there are any specific guidelines or considerations before I proceed.

[pierrejeambrun]

@Prasanth345 Please go ahead, you're assigned.