Jira Ticket Triage
Project Manager Official v1.0.16Pulls Jira tickets via MCP, categorizes by status and priority, and generates a triage report or sprint summary
by skrptiq
Sign in to import this skrpt into your workspace.
Sign inWhat's included 10 nodes
Jira Ticket Triage
Fetches Jira tickets via MCP, runs priority triage and workload analysis, and generates an actionable triage report
Priority Triage
Assesses ticket urgency and recommends triage actions — escalate, schedule, defer, or close
Triage Synthesis
Combines priority triage and workload analysis into a stakeholder-ready triage report
Workload Analysis
Analyzes ticket distribution across assignees — identifies overload, gaps, and imbalances
Analyze Workload
Analyzes ticket distribution across team members
Fetch Jira Tickets
Retrieves and structures Jira tickets via MCP using JQL
Polish Triage
Final language polish on the triage report
Synthesize Triage
Combines priority triage and workload analysis into a triage report
Triage Priorities
Assesses ticket urgency and recommends triage actions
Jira MCP
Jira MCP server for reading issues, sprints, and project data via Atlassian Cloud
Requirements 2 services, 2 permissions
- LLM Service
- jira-mcp
- network:atlassian.net
- network:id.atlassian.com
Security Passed
Detected
- Services: llm-service
- Permissions: network:id.atlassian.com
- Data Handling:
Version history 13 releases
GH#845 — republish with American English (en-US) content, completing the source-only GH#805 flip that never reached the Hub. Copy only — no functional or behaviour change.
GH#745 — declare per-step `output: {name, type}` on every execution step (tickets/text, priorities/text, workload/text, triage_report/text, polished_triage/text). Lights up the #744 rich flow-map. Content-only. (Completes the #745 sweep for this skrpt after the #754 error fix.)
Fix-forward after Row 3b v1.0.12 publish failure. The v1.0.12 per-skrpt CI's "Register version with Hub API" step failed because the consumer's source `manifest.id` (069d2091…) did not match the D1 catalogue row's id (87b76f93…) — a legacy drift from before Action 6 (`0bcc5ae0`) made publish-skrpt.mjs Step 2 INSERT use `manifest.id` for the D1 id column. v1.0.13 reconciles the source `manifest.id` to the catalogue authoritative value (Row-5-equivalent for consumers) and republishes. Per Adj-1: no re-tag of v1.0.12; the orphaned GitHub release artefact stays inert (no D1 versions row, no consumer pinned it).
Wave 2: re-signed with canonical engine signing pipeline.
Signature fix — RELEASE_NOTES.md now included in integrity checksum.
Initial catalogue release with full structural and content-quality validation. All scanner checks pass.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
More from Project Manager
View all →Risk Review Process
Identifies risks, scores them, and produces a register update
Retrospective Pipeline
Collects feedback, analyzes themes, and produces action items
Sprint Summary Pipeline
Pulls sprint tickets from Linear via MCP, analyzes velocity and status, and generates a stakeholder-ready sprint report