Solution skill
Diagnose: ownership rules not assigning issues
Complete solution
Shows how to fix diagnose: ownership rules not assigning issues. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
Either write rules against the built paths or set up code mappings so Sentry normalizes them. The issue details page has an ownership editor showing suggested paths from the actual event: use those suggestions instead of guessing. CODEOWNERS import needs code mappings configured first, plus external team/user mappings (source-control identities to Sentry users/teams); rules without mappings are silently ignored.
When to use
You are seeing this: Rules are type:pattern owners, one per line: ` path:src/backend/ #backend-team path:src/api/ #api-team Patterns are unix globs (, ?), not regex. Use this skill when you run into "Diagnose: ownership rules not assigning issues".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Step 1: check the syntax
Rules are type:pattern owners, one per line:
path:src/backend/* #backend-team
path:src/api/* #api-teamPatterns are unix globs (*, ?), not regex. A rule written as regex (path:src/backend/.*) matches nothing. Owners are emails or #team names separated by spaces.
Step 2: check what the rule matches against
path matches file paths in stack traces, which are build-output paths, not repo paths. If you build into dist/, the stack trace says dist/... while your rule says src/.... Either write rules against the built paths or set up code mappings so Sentry normalizes them. The issue details page has an ownership editor showing suggested paths from the actual event: use those suggestions instead of guessing.
Step 3: check precedence and one-shot behavior
Ownership rules beat CODEOWNERS. And once an issue is assigned (manually or automatically), auto-assignment turns off for that issue. If someone assigned it by hand during triage, the rules will never reassign it. Unassign it to let automation take over again.
Step 4: CODEOWNERS specifics
CODEOWNERS import needs code mappings configured first, plus external team/user mappings (source-control identities to Sentry users/teams); rules without mappings are silently ignored. The file caps at 3MB. Also note the scope: ownership only applies to error issues, not performance or replay issues. If those go unassigned, that is by design.
Verify
Create a test issue with a stack frame matching a rule path and confirm assignment within a minute. For CODEOWNERS, confirm the team mapping resolves: an unmapped team name fails silently.
Evidence
Researched against live Sentry docs 2026-09-26. The ownership rules page (docs.sentry.io/product/issues/ownership-rules/) documents: the type:pattern owners format with path/module/url/tags types; patterns use unix-style glob (* and ?), explicitly not regex; ownership rules take precedence over code owners; auto-assignment turns off for an issue once it has been assigned manually or automatically; CODEOWNERS import needs code mappings configured first and external team/user mappings, with a 3MB file limit; and the feature only applies to error issues, not performance or replay issues.
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_u3RMn2OqhttpIvJlfH84-Q" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Diagnose: ownership rules not assigning issues <span>— Vectle</span></a>