vincbeck opened a new pull request, #71446: URL: https://github.com/apache/airflow/pull/71446
Tracing data lineage across a multi-team deployment means jumping between assets and the Dags and tasks that produce or schedule them, without any signal of who owns each one. Surfacing the owning team directly in the "Scheduled Dags" and "Producing Tasks" popovers on the assets list makes ownership obvious while following those links, so operators know who to reach without opening each Dag. The team is resolved in a single batched lookup and only when multi-team support is enabled, so single-team deployments issue no extra query and see no change. ## Screenshots ### Dags <img width="1845" height="217" alt="Screenshot 2026-08-11 at 12 23 05 PM" src="https://github.com/user-attachments/assets/081a6c96-1895-4c8c-9366-becca1fb1cac"; /> ### Tasks <img width="1834" height="214" alt="Screenshot 2026-08-11 at 12 23 13 PM" src="https://github.com/user-attachments/assets/39cc7e42-6191-4d5f-b439-1823a5c2fe2d"; /> <!-- SPDX-License-Identifier: Apache-2.0 https://www.apache.org/licenses/LICENSE-2.0 --> <!-- Thank you for contributing! Please provide above a brief description of the changes made in this pull request. Write a good git commit message following this guide: https://chris.beams.io/posts/git-commit/ Please make sure that your code changes are covered with tests. And in case of new features or big changes remember to adjust the documentation. For user-facing UI changes, please attach before/after screenshots (or a short screen recording) so reviewers can assess the visual impact. Feel free to ping (in general) for the review if you do not see reaction for a few days (72 Hours is the minimum reaction time you can expect from volunteers) - we sometimes miss notifications. In case of an existing issue, reference it using one of the following: * closes: #ISSUE * related: #ISSUE --> --- ##### Was generative AI tooling used to co-author this PR? <!-- If generative AI tooling has been used in the process of authoring this PR, please change below checkbox to `[X]` followed by the name of the tool, uncomment the "Generated-by". --> - [ ] Yes (please specify the tool below) <!-- Generated-by: [Tool Name] following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions) --> --- * Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)** for more information. Note: commit author/co-author name and email in commits become permanently public when merged. * For fundamental code changes, an Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals)) is needed. * When adding dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x). * For significant user-facing changes create newsfragment: `{pr_number}.significant.rst`, in [airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments). You can add this file in a follow-up commit after the PR is created so you know the PR number. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
