UI: Add timetable type filter to Dag list - #69728
Merged
bbovenzi merged 6 commits intoJul 29, 2026
Merged
Conversation
boring-cyborg
Bot
added
area:API
2 tasks
shivaam
force-pushed
the
codex/airflow-investigate-issue-53738
branch
from
July 10, 2026 17:27
6218138 to
4841870
Compare
shivaam
marked this pull request as ready for review
July 10, 2026 21:26
shivaam
requested review from
bbovenzi,
bugraoz93,
choo121600,
ephraimbuddy,
guan404ming,
henry3260,
jason810496,
pierrejeambrun,
rawwar,
ryanahamilton,
shubhamraj-git and
vatsrahul1001
as code owners
July 10, 2026 21:26
potiuk
added
the
ready for maintainer review
shivaam
marked this pull request as draft
July 13, 2026 08:21
bbovenzi
reviewed
Jul 13, 2026
Contributor
Author
Hello! I will update the PR by tomorrow morning. Working on it today |
Contributor
Author
f1.movHere is an example of how it will look like. If you agree with the design, I will move ahead with the implementation. I have fixed the favorites to the right as we resize the window so they dont move around on smaller screens |
shivaam
marked this pull request as ready for review
July 24, 2026 17:44
shivaam
force-pushed
the
codex/airflow-investigate-issue-53738
branch
from
July 25, 2026 04:15
3a2493c to
c5dacaf
Compare
Contributor
|
If we are filtering by timetable then I think we should also show timetable with the schedule in the card and list. Can be a separate PR. |
bbovenzi
reviewed
Jul 27, 2026
bbovenzi
approved these changes
Jul 28, 2026
Contributor
|
LGTM let's just rerun the autogenerated API docs. Its probably from my PR to shorten all of the string match descriptions. |
Users could filter by timetable type through the public API, but the Dag list uses the private UI endpoint. This makes the same capability available from the page users actually use.
Keeping these text inputs on one implementation prevents their debounce, clearing, and URL synchronization behavior from drifting.
Dags can use built-in or plugin timetables whose persisted type names are not discoverable from free text alone. Exposing readable values lets users narrow large Dag lists without knowing the exact class path.
Allow selecting multiple timetable types with OR semantics and share the tag-style select presentation between tag and timetable filters.
shivaam
force-pushed
the
codex/airflow-investigate-issue-53738
branch
from
July 29, 2026 06:51
7aab91a to
e108334
Compare
1 task
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds timetable type filtering to the Dag list UI.
The public API already supports filtering Dags by
timetable_type, but the Dag list page uses the private/ui/dagsendpoint. This wires the same filter through the private endpoint, generated UI client, and Dag list filters.The timetable filter uses a discoverable, server-backed typeahead and supports selecting multiple timetable types with OR semantics. The timetable and tag controls use a small shared filter-select component so their chips, clearing, option handling, and styling stay consistent. Other compatible filters can migrate to this shared component incrementally, giving filter controls consistent behavior across Airflow UI pages without broadening this PR into an unrelated UI rewrite.
closes: #53738
Testing:
Was generative AI tooling used to co-author this PR?
Generated-by: OpenAI Codex following the guidelines