triage-issue

Triages bug reports by searching Jira for duplicates and generating structured issues.

949|119|Updated Aug 1, 2025
One-click install
npx skills add https://github.com/atlassian/atlassian-mcp-server --skill triage-issue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage-issue
Source: https://github.com/atlassian/atlassian-mcp-server/tree/main/skills/triage-issue
Command: npx skills add https://github.com/atlassian/atlassian-mcp-server --skill triage-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Developers and support teams spend significant time manually triaging bug reports, often creating duplicate issues or missing historical context. This skill automates the process of identifying, analyzing, and acting on bug reports, saving time and improving issue tracking accuracy.

Core Features & Use Cases

  • Duplicate Detection: Automatically search Jira for similar or duplicate issues based on error messages, stack traces, and contextual information.
  • Contextual Triage: Analyze fix history and related issues to provide informed recommendations (e.g., add comment to existing issue, create new, flag as possible regression).
  • Structured Bug Reporting: Create new, well-formatted Jira bug tickets with all necessary details (environment, reproduction steps, impact) or add context to existing ones.
  • Use Case: A user reports a "Connection timeout" error. Instead of manually searching Jira, the AI uses this skill to find an existing, open ticket for the same issue, and offers to add the new report as a comment, preventing duplicate work and centralizing information.

Quick Start

Triage this error: "Users getting 'Connection timeout' error when trying to login on mobile app". Is this a duplicate bug? Error: NullPointerException in PaymentProcessor.processRefund() line 245.

Frequently Asked Questions about triage-issue

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

FAQPage Schema
How do I detect duplicate bug reports in Jira automatically?

Duplicate detection searches Jira for similar issues using error messages, stack traces, and contextual information like component and environment. The skill analyzes these signals across multiple query angles to surface existing open tickets matching the new report, preventing redundant work and centralizing information in one place.

Can I automate bug triage for error reports from production environments?

Yes, bug triage works across production, staging, and development environments. It extracts error signatures, reproduction context, and environment details from reports, then queries Jira to recommend whether to create a new issue, add context to an existing one, or flag a possible regression.

What information should I include when reporting a bug for triage?

Include the error message or stack trace, affected component, environment (production, staging, development), reproduction steps, and any user actions leading to the error. The skill uses these details to search Jira comprehensively and generate structured bug tickets with all necessary context.

How does the skill handle similar issues with different error messages?

The skill implements multi-angle Jira queries based on error signatures, component context, and symptom patterns rather than exact matches. This approach surfaces related issues that may have different error text but stem from the same underlying problem or component.

What's the best way to manage duplicate issues when multiple reports arrive?

Instead of creating duplicates, the skill identifies existing issues and recommends adding the new report as a comment to centralize information. This preserves issue history, prevents fragmentation, and ensures all context for a bug lives in one ticket for faster resolution.