incident-ingesting

Ingest Jira incident tickets into a standardized intake package for triage.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/wizeline/sdlc-agents --skill incident-ingesting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: incident-ingesting
Source: https://github.com/wizeline/sdlc-agents/tree/main/aicores/incident-resolution-agent/skills/incident-ingesting
Command: npx skills add https://github.com/wizeline/sdlc-agents --skill incident-ingesting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill bridges existing Jira tickets describing production incidents to the Incident Commander's response flow, ensuring all necessary context is captured without requiring developers to repeat information.

Core Features & Use Cases

  • Jira Ticket Contextualization: Automatically fetches and structures all relevant details from a Jira ticket (summary, description, comments, attachments, linked issues).
  • Standardized Intake Package: Generates a Triage-ready context block compatible with the incident response pipeline.
  • Use Case: When a developer posts a Jira ticket key like "OPS-412 is a P1", this Skill ingests the ticket's details and presents them to the Incident Commander, ready for immediate triage.

Quick Start

Use the incident-ingesting skill to process the Jira ticket with key PROD-88.

Frequently Asked Questions about incident-ingesting

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

FAQPage Schema
How do I ingest Jira tickets into an incident response flow?

You can ingest Jira tickets into an incident response flow by automatically extracting summary, description, priority, status, comments, and attachments to generate a standardized incident intake package for the Incident Commander.

What Jira data is needed for production incident triage?

Production incident triage requires Jira ticket context including summary, description, priority, status, comments, and attachments. This Skill automatically fetches these details and maps them to a standardized incident intake package ready for immediate triage.

Do I need Atlassian MCP to automate Jira incident intake?

Yes, automating Jira incident intake requires Atlassian MCP with getJiraIssue and getJiraIssueRemoteIssueLinks capabilities to fetch ticket details and linked issues for the incident response pipeline.

Can I use Jira incident tickets for on-call triage without manual data entry?

Yes, this Skill bridges existing Jira tickets directly to the Incident Commander's response flow, capturing all necessary context automatically so developers do not need to repeat information during on-call triage.

What's the best way to extract context from a Jira ticket for incident management?

The best way to extract Jira ticket context for incident management is to automatically fetch and structure all relevant details from the ticket, mapping them to a triage-ready context block compatible with the incident response pipeline.

Are there limitations when using Jira tickets for incident response automation?

Incident response automation with Jira tickets depends on Atlassian MCP capabilities for fetching ticket details and linked issues, requiring the MCP to support both getJiraIssue and getJiraIssueRemoteIssueLinks functions to properly map data to the intake package.