Skip to content

Fix inaccurate issue team ownership priority claim #38635

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
leomelki wants to merge 2 commits into
base: master
Choose a base branch
from
+4 −3
Open

Fix inaccurate issue team ownership priority claim #38635

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2529b19
Fix inaccurate team ownership priority claim
leomelki Jul 31, 2026
61b120c
Clarify sources of team ownership in documentation
leomelki Jul 31, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions content/en/error_tracking/issue_team_ownership.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 the following sources, in priority order:

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.
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

Expand Down
Loading