Skip to main content

How to set a fallback Issue Owner in Sentry?

Issue

I want a fallback owner for a whole project, so issues still get assigned when no more specific ownership rule matches.
​

Applies To

  • All SaaS Customers and Self-Hosted Users

  • Ownership Rules

  • Error Monitoring

Resolution

Add a catch-all ownership rule at the top of your project’s ownership rules. Sentry evaluates rules top to bottom and uses the last matching rule, so more specific rules listed below still win when they match.

  1. Open Settings → Projects → [your project] → Ownership Rules.

  2. Under Issue Owners, turn on auto-assignment. Use Auto-assign to issue owner, or Auto-assign to suspect commits if you want suspect commits first and ownership rules as the fallback.

  3. Click Edit Rules.

  4. Add this rule as the first line. Use a team with # plus the team slug, or a user email:

    path:** #backend-team

    path:** [email protected]

  5. Keep your more specific rules below that line. Example:

    path:** #backend-team
    path:src/auth/* #auth-team
    path:src/api/* #api-team

  6. Save the rules.

When an event matches only path:**, Sentry assigns the fallback owner. When a more specific rule also matches, that later rule is used instead.

Notes:

  • Ownership auto-assignment applies to error issues. It does not apply to performance or replay issues.

  • path rules match file paths on in-app stack frames. If an event has no in-app frames, path:** will not match. Use a url: or tags.TAG_NAME: rule for those cases, or see How do I use CODEOWNERS for issues that have no stack trace?.

  • Teams and users in the rule must have access to the project, or the rule will not save.

  • Already-assigned issues are not reassigned by new events.

For match order details, see Ownership Rules and What order are ownership rules applied in?.

Related Articles
Did this answer your question?