From 2529b199c5ca8412b53bcbd58b03d628d90d20a2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?L=C3=A9o=20MELKI?= Date: Fri, 31 Jul 2026 14:02:23 +0200 Subject: [PATCH 1/2] Fix inaccurate team ownership priority claim Correct the Overview section: team attribute and CODEOWNERS are prioritized against each other, while service ownership is a separate, always-applied, dynamic mechanism. --- content/en/error_tracking/issue_team_ownership.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/content/en/error_tracking/issue_team_ownership.md b/content/en/error_tracking/issue_team_ownership.md index 4bd533aa6cd..2c6ed33c3ab 100644 --- a/content/en/error_tracking/issue_team_ownership.md +++ b/content/en/error_tracking/issue_team_ownership.md @@ -12,11 +12,12 @@ further_reading: ## Overview -Issue Team Ownership automates your triaging work by assigning issues to the right teams. There are three independent ways to infer team ownership, in order of priority: +Issue Team Ownership automates your triaging work by assigning issues to the right teams. Datadog infers team ownership from two prioritized sources and one additional, always-applied source: -1. [Team attribute](#team-attribute): based on the `team` attribute set on the error event at runtime. -2. [CODEOWNERS](#codeowners-file): based on the top-level stack frame of the issue according to GitHub `CODEOWNERS`. -3. [Service ownership](#service-ownership): based on the owner of the service where the issue happens. +1. [Team attribute](#team-attribute): based on the `team` attribute set on the error event at runtime. This takes priority over CODEOWNERS. +2. [CODEOWNERS](#codeowners-file): based on the top-level stack frame of the issue according to GitHub `CODEOWNERS`. This is used when no `team` attribute is set. + +In addition, [service ownership](#service-ownership) is always applied, based on the owner of the service where the issue happens. Unlike the other two sources, service ownership is dynamic and stays up to date with your service ownership configuration, even after the issue is created. ## Team attribute From 61b120c73b42bef2b1d1d21bd74937a47aa2e61d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?L=C3=A9o=20MELKI?= Date: Fri, 31 Jul 2026 14:25:39 +0200 Subject: [PATCH 2/2] Clarify sources of team ownership in documentation --- content/en/error_tracking/issue_team_ownership.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/error_tracking/issue_team_ownership.md b/content/en/error_tracking/issue_team_ownership.md index 2c6ed33c3ab..89ce8ff412e 100644 --- a/content/en/error_tracking/issue_team_ownership.md +++ b/content/en/error_tracking/issue_team_ownership.md @@ -12,9 +12,9 @@ further_reading: ## Overview -Issue Team Ownership automates your triaging work by assigning issues to the right teams. Datadog infers team ownership from two prioritized sources and one additional, always-applied source: +Issue Team Ownership automates your triaging work by assigning issues to the right teams. Datadog infers team ownership from the following sources, in priority order: -1. [Team attribute](#team-attribute): based on the `team` attribute set on the error event at runtime. This takes priority over CODEOWNERS. +1. [Team attribute](#team-attribute): based on the `team` attribute set on the error event at runtime. 2. [CODEOWNERS](#codeowners-file): based on the top-level stack frame of the issue according to GitHub `CODEOWNERS`. This is used when no `team` attribute is set. In addition, [service ownership](#service-ownership) is always applied, based on the owner of the service where the issue happens. Unlike the other two sources, service ownership is dynamic and stays up to date with your service ownership configuration, even after the issue is created.