priority-analysis

Analyze urgency and impact to recommend JIRA ticket priority levels.

Updated Nov 22, 2025
One-click install
npx skills add https://github.com/terrazul-ai/tz-packages --skill priority-analysis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: priority-analysis
Source: https://github.com/terrazul-ai/tz-packages/tree/main/jira-triage/templates/claude/skills/priority-analysis
Command: npx skills add https://github.com/terrazul-ai/tz-packages --skill priority-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams determine the correct priority level for JIRA tickets by analyzing urgency signals, business and technical impact, and contextual factors like SLA and customer tier, enabling justified, consistent triage decisions.

Core Features & Use Cases

  • Urgency analysis: assess time-sensitivity and escalation signals to gauge how quickly a ticket needs attention.
  • Impact analysis: evaluate scope, affected users, revenue implications, and core vs. secondary functionality.
  • Priority matrix: map urgency and impact to a recommended JIRA priority with justification.
  • Contextual adjustments: incorporate SLA status, enterprise vs. standard customers, and historical patterns to refine prioritization.
  • Actionable output: produce a detailed recommendation with rationale and suggested response/resolution timelines.
  • Pattern detection: aggregate related tickets to identify systemic issues and adjust priorities accordingly.

Quick Start

Analyze a ticket's urgency and impact to generate a priority recommendation with justification.

Frequently Asked Questions about priority-analysis

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

FAQPage Schema
How do I determine the correct priority level for JIRA tickets?

To determine JIRA ticket priority, analyze urgency signals and business impact, then apply a rule-based priority matrix. This generates a structured recommendation with justification, accounting for SLA status and customer tier.

What is the best way to triage incidents and bugs based on urgency and impact?

Triage incidents and bugs by mapping urgency and impact through a priority matrix. Evaluate scope, affected users, and revenue implications to produce actionable recommendations with suggested response and resolution timelines.

Can I factor SLA status and customer tier into JIRA ticket prioritization?

Yes, you can incorporate SLA status and enterprise vs. standard customer tiers into JIRA prioritization. These contextual adjustments refine the rule-based priority matrix to justify triage decisions for SLA-bound requests.

How do I identify systemic issues when triaging a large volume of JIRA tickets?

Identify systemic issues by aggregating related JIRA tickets to detect patterns. Pattern detection analyzes urgency and impact across enterprise-scale work, adjusting priorities accordingly to highlight broader systemic problems.

Does JIRA priority analysis work for both individual tickets and broad triage patterns?

Yes, JIRA priority analysis scales from a single ticket to broad patterns. It assesses time-sensitivity and escalation signals across incidents, bugs, and SLA-bound requests to output structured recommendations with rationale.