Monitor and triage GitHub issues by severity and route to Jira
Read new GitHub issues, classify by severity, and create Jira tickets with the right priority
Overview
Triaging GitHub issues manually means reading each one, deciding what type it is, and creating the right Jira ticket—friction that adds up fast. This template reads new issues, classifies them, and routes them to Jira with the correct priority so your team can focus on fixing instead of sorting.
How it works
- Finds GitHub issues opened in the past 24 hours without labels
- Reads the title and body of each issue
- Classifies each as Critical Bug, Minor Bug, Feature Request, or Documentation
- Creates a Jira ticket with the appropriate issue type and priority
- Includes the original GitHub issue URL in the ticket description
Who this is for
Engineering leads managing open-source projects or internal repos who want incoming issues triaged and routed without manual review.
Suggested prompt
Look at all GitHub issues opened in the [1. Repo name] repository in the past 24 hours that havent been labeled yet. For each issue, read the title and body and classify it as one of: Critical Bug, Minor Bug, Feature Request, or Documentation. Then create a corresponding Jira ticket in the [2. Project key] project with the appropriate issue type, set the priority based on classification (Critical Bug = Highest, Minor Bug = Medium, Feature Request = Low, Documentation = Low), and include the original GitHub issue URL in the ticket description.
Frequently asked questions
Can I customize the classification categories?
Yes, modify the prompt to use your teams issue types and severity levels.
Can I change the time window?
Yes, adjust past 24 hours to any interval that fits your triage cadence.
What if I use Linear instead of Jira?
Swap Jira for Linear in the prompt and connect Linear to your MCP server.
Can I also label the GitHub issue after triaging?
Yes, add an instruction to apply a label to the GitHub issue once the Jira ticket is created.