assign-route

Classify Jira tickets and propose Chelsea Piers IT owners before assignment.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/afoxnyc3/chelsea-piers-itops --skill assign-route
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: assign-route
Source: https://github.com/afoxnyc3/chelsea-piers-itops/tree/main/plugins/jira-pm/skills/assign-route
Command: npx skills add https://github.com/afoxnyc3/chelsea-piers-itops --skill assign-route

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill prevents Jira tickets from getting stuck unassigned or landing with the wrong team by intelligently classifying the issue and proposing the correct Chelsea Piers IT owner.

Core Features & Use Cases

  • Jira-based classification: Categorizes tickets using summary, description, labels, and components, then applies the Chelsea Piers IT taxonomy.
  • Rule-based routing with guardrails: Applies routing rules including P1/critical overrides and escalates items unassigned for more than 7 days to IT Ops Lead review.
  • Human-in-the-loop assignment: Resolves the target Jira account ID and shows a reasoning-rich proposal before any write/assignment occurs.
  • Cross-team dependency awareness: Detects cross-team scope and proposes secondary notifications plus an optional routing comment.

Quick Start

Use assign-route to route Jira issue CPOPS-123 by classifying it, proposing the correct owner with reasoning, and asking for confirmation before assigning.

Frequently Asked Questions about assign-route

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically route Jira tickets to the correct IT owner?

Jira ticket routing classifies issues using summary, description, labels, and components, then applies routing rules to propose the correct owner with reasoning before assignment. This approach prevents tickets from getting stuck unassigned or landing with the wrong team.

How are critical priority issues handled during ticket assignment?

Critical priority issues trigger P1 outage overrides during Jira ticket routing, bypassing standard classification to ensure immediate assignment. The system applies specific routing rules to escalate these high-priority items to the appropriate IT owner.

What happens to unassigned Jira tickets that have been in the backlog for a long time?

Unassigned Jira backlog items exceeding 7 days are automatically escalated for IT Ops Lead review during the routing process. This escalation ensures stale tickets receive proper classification and assignment rather than remaining unassigned.

Does Jira ticket routing require the Atlassian MCP server?

Yes, Jira ticket routing requires the Atlassian MCP server to resolve Jira account IDs via lookupJiraAccountId and perform editJiraIssue operations. The MCP server provides the necessary API integration for classification and assignment.

Can I review the proposed assignment before a Jira ticket is actually assigned?

Yes, the routing process resolves the target Jira account ID and shows a reasoning-rich proposal with explicit user confirmation before any write or assignment occurs. This human-in-the-loop guardrail ensures accurate ticket routing.

How are cross-team dependencies detected during Jira ticket routing?

Cross-team scope is detected during ticket classification by analyzing issue components and labels, which then proposes secondary notifications and an optional routing comment. This awareness prevents misrouting tickets that span multiple IT teams.