Skip to main content

Why are some issues not being assigned via my CODEOWNERS rules?

Issue

I want to know why CODEOWNERS assigns some issues but leaves others unassigned.

Applies To

  • Github Integration users

  • CODEOWNERS users
    ​

Resolution

CODEOWNERS assignment relies on working code mappings, in-app stack frames, auto-assignment, and mapped owners. It only applies to error issues.

A few things to check:

  1. Auto-assignment - In Project Settings → Ownership Rules, enable Auto-assign to issue owner (or suspect commits, which falls back to owners). If the issue is already assigned, unassign it so auto-assignment can run again.

  2. Code mappings - These are required to map stack paths to your repo. Without them, CODEOWNERS won’t match. See Code Owners setup.

  3. In-app frames - CODEOWNERS only matches in-app frames. If there aren’t any, mark the relevant frames with the SDK or Stack Trace Rules.

  4. Paths without / - Paths like main.py may not map correctly. Use ownership rules for these cases.

  5. Team/user mappings - GitHub/GitLab owners need to be mapped to Sentry teams/users under Settings → Integrations → GitHub/GitLab → Team/User Mappings.

  6. No stack trace - CODEOWNERS can’t assign issues without a stack trace, so use ownership rules instead.

One thing to keep in mind: Ownership Rules run after CODEOWNERS and can override the CODEOWNERS assignment.

See Ownership Rules for the full setup.

Related Articles
Did this answer your question?