Skip to main content

Why was my issue not assigned based on my path ownership rule?

Issue

I want to know why a new issue was not assigned from my path ownership rule (or was assigned from a different rule), even though Auto-assign to issue owner is enabled and a stack trace path looks like it should match.

Applies To

  • All plans

  • Issue Owners

Resolution

Path ownership rules use Unix-style glob patterns, not prefix or regex matching. Without a wildcard, the pattern has to match the stack-trace path exactly.

For example, this won’t match /path/to/file/name.js:

path:/path/to/file


Use a glob to match files inside the directory:

path:/path/to/file/*

Make sure you’re comparing the rule against the path shown in the Issue Details stack trace, not just the path in your repository.

If the path looks correct but assignment is still missing or incorrect:

  1. Make sure auto-assignment is set to Auto-assign to issue owner in the project’s Ownership Rules settings.

  2. Sentry uses the last matching rule across Code Owners and ownership rules. See What order are ownership rules applied in?.

  3. If the issue is already assigned, new events won’t re-assign it. Unassign the issue if you want auto-assignment to run again.

  4. Ownership matching uses in-app stack frames. If you’re using Code Owners, see Why was Code Owners not used to assign an issue?.

Ownership rules apply to error issues only. See Ownership Rules for more details.

Did this answer your question?