jira-auto-assign

Assigns Jira tickets to Legal team members based on matter type, severity, and capacity rules.

Updated Apr 30, 2026
One-click install
npx skills add https://github.com/myPOStech/mps-legal-legalcopilot-ai --skill jira-auto-assign-mypostech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira-auto-assign
Source: https://github.com/myPOStech/mps-legal-legalcopilot-ai/tree/main/skills/jira-auto-assign
Command: npx skills add https://github.com/myPOStech/mps-legal-legalcopilot-ai --skill jira-auto-assign-mypostech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Legal teams triaging Jira tickets manually decide who should own each request, which is slow, inconsistent, and error-prone. This Skill automates lawyer selection by applying team routing rules, severity logic, and workload capacity checks, then sets the Jira assignee field directly. ## Core Features & Use Cases - Rule-based routing: Reads team roster, expertise map, and senior reviewer fallback from a team-editable routing file, so re-routing requires editing one document rather than code. - Severity-aware assignment: High-severity matters (claims, regulator flags, tight SLAs) oscillate between a designated senior pool, while normal matters route by matter-type expertise with secondary fallbacks. - Capacity protection: Counts each candidate's open LEGAL and AIRD tickets via JQL and skips overloaded lawyers, with the senior reviewer as an always-assignable last resort. - Use Case: After a triage skill classifies ticket LEGAL-4321 as an NDA review with medium confidence, this Skill picks the NDA primary lawyer, verifies they are under capacity, and sets them as assignee before the triage comment is posted. ## Quick Start Ask the assistant to assign ticket LEGAL-4321 to the right lawyer using the team routing rules after triage has produced a matter type and severity.

Frequently Asked Questions about jira-auto-assign

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

FAQPage Schema
How do I auto-assign Jira tickets to the right team member?

Pass the ticket key plus triage outputs (matter type, confidence, risk flags, priority, SLA) to the skill. It reads routing rules from team-routing.md, picks a candidate by expertise and severity, checks their open workload via JQL, and sets the assignee with editJiraIssue.

How does workload-based assignment work in Jira?

The skill runs a JQL query counting the candidate's open tickets in the LEGAL and AIRD projects. If the count meets or exceeds the soft capacity threshold, it walks the secondary lawyers in order, falling back to the senior reviewer who is exempt from capacity checks.

Can I change the routing rules without editing the skill?

Yes. The team roster, expertise map, high-severity pool, and capacity threshold all live in knowledge/team-routing.md (mirrored on SharePoint). Editing that file re-routes future assignments; the skill itself never modifies it.

What happens if the Jira assignment fails or the account lookup fails?

The skill retries once with the senior reviewer. If that also fails, it aborts and returns a structured reason rather than guessing an account ID or picking a random lawyer, since a bad assignment is treated as worse than none.

Why does the assignee get overwritten after transitioning a Jira ticket?

The LEGAL project's Start Progress post-function reassigns the ticket to the acting account. The skill requires transitions to happen before assignment and re-verifies the assignee afterwards, re-applying editJiraIssue once if it was overwritten.

Does the skill post comments or reassign tickets that already have an owner?

No. It never posts Jira comments; the assignee field is the only signal. It also refuses to reassign tickets that already have an assignee unless the caller explicitly passes force_reassign, used only by the triage-board last-replier logic.