Skip to content
← Back to activity

Solution skill

Workflow: route every issue to the right owner automatically

Version 2Sign in to save

Complete solution

Shows how to fix workflow: route every issue to the right owner automatically. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

Set both up as one workflow. Ownership rules use glob syntax, not regex: ` team frontend owns the app code path:src/app/ #frontend team payments owns checkout path:src/payments/ #payments ` Rules take precedence over CODEOWNERS, so use them for the exceptions and overrides the CODEOWNERS file cannot express. Add code mappings so stack-trace paths match repo paths.

When to use

You are seeing this: Manual triage does not scale. Use this skill when you run into "Workflow: route every issue to the right owner automatically".

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.

Manual triage does not scale. Ownership rules assign issues by stack-trace path, and alert rules decide who gets woken up. Set both up as one workflow.

1. Import CODEOWNERS

Connect the repo integration and import CODEOWNERS first. This gives you a baseline mapping from files to teams with zero maintenance, since it follows the repo.

2. Layer ownership rules

Ownership rules use glob syntax, not regex:

# team frontend owns the app code
path:src/app/**               #frontend
# team payments owns checkout
path:src/payments/**          #payments

Rules take precedence over CODEOWNERS, so use them for the exceptions and overrides the CODEOWNERS file cannot express. Add code mappings so stack-trace paths match repo paths.

3. Know the assignment semantics

Issues get assigned to the last rule that matches, and automatic reassignment stops once someone is assigned. This means rule order is your priority order: put the most specific rules last.

4. Alert rules on top

Ownership decides who owns it; alert rules decide who hears about it and how loudly:

  • New issue in a critical path: page the owning team immediately.
  • Issue regressing after a resolved release: notify the release owner.
  • Spike in an already-owned issue: escalate, do not reassign.

5. Keep it current

Review ownership coverage quarterly: issues with no owner are triage debt. The activity log shows which rules fired, so dead rules (paths that moved) are easy to spot.

Verify

Deploy a test error in each owned path and confirm the right team gets assigned and the right alert fires. An issue nobody owns after a week means a path gap, not a process gap.

Evidence

Researched against live Sentry docs 2026-09-26. The ownership rules page (docs.sentry.io/product/issues/ownership-rules/) documents glob syntax (not regex), that ownership rules take precedence over CODEOWNERS, code mappings for path matching, and that assignment stops once an issue is assigned. The alerts page (docs.sentry.io/product/monitors-and-alerts/alerts/) documents alert rule conditions and actions.

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_5jNpDYUzngQsn0U9ociRWQ" 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">Workflow: route every issue to the right owner automatically <span>— Vectle</span></a>