Repository navigation
UI: Add team column and filter to the deadlines list - #72060
Merged
Merged
Conversation
vincbeck
requested review from
bbovenzi,
bugraoz93,
choo121600,
ephraimbuddy,
guan404ming,
henry3260,
jason810496,
pierrejeambrun,
rawwar,
ryanahamilton,
shubhamraj-git and
vatsrahul1001
as code owners
August 25, 2026 14:35
boring-cyborg
Bot
added
area:API
ferruzzi
reviewed
Aug 26, 2026
ferruzzi
left a comment
ferruzzi
left a comment
Contributor
There was a problem hiding this comment.
A couple non-blocking questions, otherwise LGTM from a backend side. I'm still not confident enough with front-end to approve that side.
When multi-team mode is enabled, operators watching deadlines across teams need to see which team owns each deadline and to scope the list to a single team when triaging that team's misses. The column and the filter render only when the `multi_team` configuration is enabled, and no team data is loaded when it is off, so single-team deployments are unaffected.
vincbeck
force-pushed
the
vincbeck/team-column-deadlines
branch
from
August 27, 2026 14:21
56a04a3 to
c73ca68
Compare
ferruzzi
approved these changes
Aug 27, 2026
ramitkataria
approved these changes
Aug 28, 2026
attach_dag_to_team commits its bundle and team before yielding, so a test run interrupted inside that context manager leaves the rows behind. On a persistent database every later run then failed with a duplicate-key error until the rows were deleted by hand.
imrichardwu
pushed a commit
to imrichardwu/airflow
that referenced
this pull request
Sep 11, 2026
* UI: Add team column and filter to the deadlines list When multi-team mode is enabled, operators watching deadlines across teams need to see which team owns each deadline and to scope the list to a single team when triaging that team's misses. The column and the filter render only when the `multi_team` configuration is enabled, and no team data is loaded when it is off, so single-team deployments are unaffected. * Make deadlines UI tests recover from leftover team rows attach_dag_to_team commits its bundle and team before yielding, so a test run interrupted inside that context manager leaves the rows behind. On a persistent database every later run then failed with a duplicate-key error until the rows were deleted by hand.
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
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.
When multi-team mode is enabled, operators watching deadlines across teams need to see which team owns each deadline and to scope the list to a single team when triaging that team's misses.
The column and the filter render only when the
multi_teamconfiguration is enabled, and no team data is loaded when it is off, so single-team deployments are unaffected.Screenshot
Was generative AI tooling used to co-author this PR?
{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.