UI: Add team column and filter to Dag Run and Task Instance lists - #70241
Conversation
boring-cyborg
Bot
added
area:airflow-ctl
area:API
bugraoz93
left a comment
bugraoz93
left a comment
There was a problem hiding this comment.
Looks good to me on API and CTL side, would be great to get additional eyes for the UI
bbovenzi
left a comment
bbovenzi
left a comment
There was a problem hiding this comment.
looks good just two nits
6aefd04 to
a3b9b46
Compare
When multi-team mode is enabled, operators triaging failures across teams need to see which team owns each Dag Run and Task Instance, and scope the lists to a single team. This adds: - A "Team" column on the Dag Run list (after Run Type) and the Task Instance list (after State), each linking to the Dag list filtered by that team - A team filter in the existing filter bar on both pages - Backend support: a nullable `team_name` field on `DAGRunResponse` and `TaskInstanceResponse`, populated (via bundle association) only when multi-team is enabled, plus a `teams` query parameter on the list endpoints that scopes results by team The column and filter render only when the `multi_team` configuration is enabled, so single-team deployments are unaffected.
a3b9b46 to
50f47c0
Compare
Backport failed to create: airflow-ctl/v0-1-test. View the failure log Run detailsNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
You can attempt to backport this manually by running: cherry_picker 94b9fe3 airflow-ctl/v0-1-testThis should apply the commit to the airflow-ctl/v0-1-test branch and leave the commit in conflict state marking After you have resolved the conflicts, you can continue the backport process by running: cherry_picker --continueIf you don't have cherry-picker installed, see the installation guide. |
Anything I should do @bugraoz93 ? |
We don't need backport of generated models, let me remove the label too so we won't check while releasing if check needed. Thanks for checking Vincent! |
|
Let me also check boring cyborg config to exclude the generated part only |
We need to create according to state of support during release while fast forwarding |
3 participants
When multi-team mode is enabled, operators triaging failures across teams need to see which team owns each Dag Run and Task Instance, and scope the lists to a single team. This adds:
team_namefield onDAGRunResponseandTaskInstanceResponse, populated (via bundle association) only when multi-team is enabled, plus ateamsquery parameter on the list endpoints that scopes results by teamThe column and filter render only when the
multi_teamconfiguration is enabled, so single-team deployments are unaffected.Screenshots
Dag runs list
Task instances list
Filter
Was generative AI tooling used to co-author this PR?
Claude (Opus 4.8)
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.