route-to-jira

Route classified IT support emails into Jira tickets with project, type, priority, and labels.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of IT support emails getting delayed or misrouted because they are not converted into properly categorized Jira tickets.

Core Features & Use Cases

  • Routes tickets to the correct Jira project and issue type using the email classification output (category + tier).
  • Maps priority and adds consistent labels (including automated identification labels like email-triage and auto-triaged).
  • Closes the loop with the requester by sending a routing acknowledgment that includes the Jira reference number and SLA estimate.

Use case example: A Tier 2 access-related request comes in as a classified email that cannot be auto-resolved; the skill creates the appropriate Jira issue with the right priority and labels and then replies to the requester with the ticket key and tracking link.

Quick Start

Tell the skill to route to jira and create a Jira ticket using the classified email details: message_id, subject, body, sender, category, priority, tier, and received timestamp.

Frequently Asked Questions about route-to-jira

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

FAQPage Schema
How do I automatically create Jira tickets from incoming IT support emails?

Automating Jira ticket creation from IT support emails involves classifying the message by category and tier, then routing the details to select the correct Jira project, issue type, priority, and labels for actionable work items.

What is the best way to route classified helpdesk emails to the correct Jira project?

Routing classified helpdesk emails to Jira requires using the email's category and tier to map the appropriate project, issue type, and priority, ensuring the email is marked as read only after the ticket is successfully created.

Does email triage to Jira require a specific API token for ticket creation?

Yes, email triage to Jira ticket creation requires a JIRA_API_TOKEN to execute the Jira API call for generating the issue and sending a routing acknowledgment with the Jira reference number to the requester.

Can I use Microsoft 365 emails to auto-generate Jira tickets with priority and labels?

Yes, Microsoft 365 emails can be auto-routed to generate Jira tickets. The process maps priority and adds consistent labels like auto-triaged based on the classified email's category and tier data.

How does the email requester get notified when a Jira ticket is created from their helpdesk request?

The requester receives an email acknowledgment containing the Jira reference number and SLA estimate immediately after the system successfully creates the Jira issue from their classified support email.

When should I avoid using automated email routing for Jira ticket creation?

You should avoid automated email routing to Jira for Tier 1 cases that can be self-serviced or auto-resolved, as this skill is specifically designed for helpdesk escalations that cannot be self-serviced.