Issue
I want to know why an issue wasn’t assigned even though a Code Owners rule matched the stack trace path.
Applies To
All SaaS Customers
Business and Enterprise plans
Code Owners / Ownership Rules
Resolution
That’s correct. The key distinction is that CODEOWNERS assignment is driven by in-app stack frames, not simply by the presence of a matching file in the repository.
A practical troubleshooting order is:
Check the issue’s stack trace and verify that the relevant frame is marked in-app.
If it isn’t, configure the SDK - for example, Python’s
in_app_include- or use Stack Trace Rules to classify the frame as in-app. Stack Trace RulesCheck Ownership Rules and make sure automatic assignment is enabled. An issue that is already assigned won’t be automatically reassigned until it is unassigned. Ownership Rules
Verify that the repository has working code mappings, and that the CODEOWNERS teams/users are correctly mapped to Sentry teams/users. Code Owners documentation
If all of those are correct, check Sentry’s troubleshooting guide for additional CODEOWNERS assignment failure modes. Why are some issues not being assigned via my CODEOWNERS rules?
The most common gotcha: a stack frame can have the right filename/path but still not participate in CODEOWNERS matching because Sentry considers it out-of-app.