JustAnalytics/Documentation

Issue Ownership & Assignment

Automatically route errors to the right team using ownership rules, CODEOWNERS files, and suggested assignees.

Issue Ownership & Assignment

JustAnalytics automatically routes errors to the right person using three complementary systems: ownership rules, CODEOWNERS file support, and AI-suggested assignees.

Ownership Rules#

Ownership rules match error properties against glob patterns to auto-assign errors to specific team members.

Rule Types#

Path Rules — Match against the file path in the error stack trace:

src/payments/**/*.ts → payments-team@company.com
src/api/auth/** → security@company.com

URL Rules — Match against the page URL where the error occurred:

/checkout/* → checkout-team@company.com
/api/v2/** → api-team@company.com

Tag Rules — Match against error tags (key:value format):

service:payments → payments-lead@company.com
environment:production → oncall@company.com

Creating Ownership Rules#

  1. Navigate to your Site Settings page
  2. Scroll to Ownership Rules section
  3. Click Add Rule
  4. Select match type (Path, URL, or Tag)
  5. Enter the glob pattern
  6. Enter the owner email address
  7. Toggle Active to enable

Rule Priority#

Rules are evaluated in priority order (top to bottom). The first matching rule wins. Drag rules up/down to reorder priority.

How Auto-Assignment Works#

When a new error group is created (first occurrence), JustAnalytics:

  1. Extracts the filename, URL, and tags from the error
  2. Evaluates ownership rules in priority order
  3. Sets assignedTo on the error group to the first matching owner
  4. The assignment appears immediately in the error list and detail page

Rules are cached for 60 seconds for performance.

CODEOWNERS File Support#

If your repository uses a .github/CODEOWNERS file, JustAnalytics can parse it to suggest assignees based on stack trace file paths.

Uploading CODEOWNERS#

  1. Go to Site Settings > Code Owners section
  2. Paste the file contents or upload the file
  3. JustAnalytics parses and validates the entries

CODEOWNERS Format#

# Default owner
* @default-team

# Frontend
src/components/** @frontend-team
src/pages/** @frontend-team

# Backend API
src/api/** @backend-team @api-lead

# Database
src/db/** @dba-team
migrations/** @dba-team

Last-Match-Wins Semantics#

Following the CODEOWNERS specification, the last matching pattern takes precedence. This allows broad defaults at the top and specific overrides below.

Suggested Assignees#

When viewing an error detail page, JustAnalytics suggests an assignee based on:

  1. CODEOWNERS — Checked first, stack trace file paths matched against entries
  2. Ownership Rules — Fallback if no CODEOWNERS match
  3. No suggestion — If neither system finds a match

The suggestion appears as a chip below the assignee field with a one-click Assign button.

Issue Linking#

Link error groups to external trackers for bidirectional status sync:

  • GitHub Issues — Auto-detected from github.com URLs
  • Jira — Auto-detected from atlassian.net URLs
  • Linear — Auto-detected from linear.app URLs
  • Other — Any URL can be linked manually

When the linked external issue is closed, JustAnalytics automatically resolves the error group via webhook sync.

Best Practices#

  1. Start with broad ownership rules, then add specific ones
  2. Upload CODEOWNERS if your repo uses it for the most accurate suggestions
  3. Combine both systems — CODEOWNERS for file-level, rules for URL/tag patterns
  4. Use tag rules for services — route server-side errors by service name
  5. Review auto-assignments periodically as code evolves

Next Steps#