Repository navigation
UI: Add team column and filter to the XComs list - #72158
Merged
Merged
Conversation
When multi-team mode is enabled, operators inspecting cross-task communication across teams need to see which team owns each XCom entry and to scope the list to a single team while investigating that team's Dags. 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
requested review from
bbovenzi,
bugraoz93,
choo121600,
dheerajturaga,
ephraimbuddy,
guan404ming,
henry3260,
jason810496,
pierrejeambrun,
potiuk,
rawwar,
ryanahamilton,
shubhamraj-git and
vatsrahul1001
as code owners
August 27, 2026 14:51
boring-cyborg
Bot
added
area:airflow-ctl
area:API
eladkal
approved these changes
Aug 31, 2026
bbovenzi
approved these changes
Aug 31, 2026
Contributor
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 c685468 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. |
imrichardwu
pushed a commit
to imrichardwu/airflow
that referenced
this pull request
Sep 11, 2026
When multi-team mode is enabled, operators inspecting cross-task communication across teams need to see which team owns each XCom entry and to scope the list to a single team while investigating that team's Dags. 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.
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 inspecting cross-task communication across teams need to see which team owns each XCom entry and to scope the list to a single team while investigating that team's Dags.
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.