You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Add Support for Filtering DAGs by Timetable Type #53738
Add the ability to filter DAGs based on their Timetable type (e.g., CronTriggerTimetable, AssetOrTimeSchedule) in both the UI and public DAG APIs.
Proposed Solution
Add a new query parameter timetable_type to the DAG listing endpoints that allows filtering DAGs based on their timetable type.
Use case/motivation
Currently, while the DAG model stores timetable information in the timetable_summary field, there is no API support to filter DAGs based on their timetable type. Users cannot easily find all DAGs that use a specific type of timetable. This functionality is crucial to fix #53041. Once this is implemented, the UI filter functionality will be built on top of this.
I noticed another ticket linked to this one and saw some activity. Just checking — have you already started working on it, or would it be okay for me to pick it up?
The public DAG endpoint( '/api/v2/dags' ) already supports timetable_type, but the DAG list page appears to use the UI-specific /ui/dags endpoint. That endpoint does not currently expose timetable_type in its OpenAPI/generated client.
( public DAG endpoint api implementation : #58852 )
Would the expected approach be to add timetable_type to /ui/dags as well, regenerate the UI client, and then wire a filter input on the DAG list page to that parameter?
Hi! I am working on this and opened a draft PR: #69728.
The draft wires the existing timetable_type backend support through the private /ui/dags endpoint and the Dag list UI filter. I will keep it as draft while I finish the remaining PR polish, including screenshots/recording.
@baha-bouali yes it's still open. There was this PR #69728 to fix it but it looks like it's stale.
Feel free to open a PR to fix this.
@baha-bouali Sorry for the delay. I will update my draft by tomorrow. Might be better to avoid duplicate work. If I cant get to it this weekend, I will let you take over.
Activity
shreyaskj-0710 commentedon Aug 6, 2025
I’ll work on this issue—let me know if it’s already been picked up by someone else.
shreyaskj-0710 commentedon Aug 7, 2025
Hi @AryanK1511 ,
I noticed another ticket linked to this one and saw some activity. Just checking — have you already started working on it, or would it be okay for me to pick it up?
phanikumv commentedon Aug 7, 2025
Assigned to you @shreyaskj-0710
vatsrahul1001 commentedon Aug 10, 2025
@shreyaskj-0710 how are we progressing on this?
shreyaskj-0710 commentedon Aug 10, 2025
Hi @vatsrahul1001 ,
API-related changes have been completed, and I will be raising the pull request tomorrow.
11 remaining items
jinoo7099 commentedon May 14, 2026
@pierrejeambrun
Hi, I started looking into this.
The public DAG endpoint( '/api/v2/dags' ) already supports
timetable_type, but the DAG list page appears to use the UI-specific/ui/dagsendpoint. That endpoint does not currently exposetimetable_typein its OpenAPI/generated client.( public DAG endpoint api implementation : #58852 )
Would the expected approach be to add
timetable_typeto/ui/dagsas well, regenerate the UI client, and then wire a filter input on the DAG list page to that parameter?pierrejeambrun commentedon May 19, 2026
@jinoo7099 Yes, that sounds like a good plan :)
shivaam commentedon Jul 10, 2026
Hi! I am working on this and opened a draft PR: #69728.
The draft wires the existing
timetable_typebackend support through the private/ui/dagsendpoint and the Dag list UI filter. I will keep it as draft while I finish the remaining PR polish, including screenshots/recording.baha-bouali commentedon Jul 22, 2026
Is this issue still open? I would like to work on this.
pierrejeambrun commentedon Jul 24, 2026
@baha-bouali yes it's still open. There was this PR #69728 to fix it but it looks like it's stale.
Feel free to open a PR to fix this.
shivaam commentedon Jul 24, 2026
@baha-bouali Sorry for the delay. I will update my draft by tomorrow. Might be better to avoid duplicate work. If I cant get to it this weekend, I will let you take over.
vatsrahul1001 commentedon Jul 28, 2026
Moving to 3.3.2 as it see we still do not have a ready PR
baha-bouali commentedon Jul 28, 2026
I think #69728 is waiting for review. If it doesn't end up resolving this issue, I'd be happy to pick it up.