triage-issue

Search Jira for duplicate bugs using error signatures from stack traces.

5|1|Updated Jun 20, 2026

Search Tags:#automation #jira #atlassian #duplicate detection #triage #bug tracking

Ready to run

npx skills add https://github.com/isukharev/atl --skill triage-issue-isukharev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: triage-issue
Source: https://github.com/isukharev/atl/tree/main/plugins/atl/skills/triage-issue
Command: npx skills add https://github.com/isukharev/atl --skill triage-issue-isukharev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents the creation of duplicate Jira tickets by enabling intelligent, search-based verification of existing issues before any new bug is reported.

Core Features & Use Cases

Error Signature Extraction: Automatically identifies key error patterns and removes volatile data to improve search accuracy.
Duplicate Detection: Executes parallel JQL queries to find related open or resolved issues based on error signatures.
Safe Workflow: Provides a structured path to comment on existing issues, link new bugs to regressions, or create new tickets only after verification.

Quick Start

Use the triage-issue skill to search for existing Jira tickets matching the error signature found in the provided stack trace.

Frequently Asked Questions about triage-issue

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

FAQPage Schema

How do I prevent filing duplicate Jira bugs when reporting an error?▼

To prevent filing duplicate Jira bugs, you can use automated triage to extract error signatures from stack traces and search existing Jira issues for matches. This skill isolates key error patterns by removing volatile data to improve search accuracy.

How does duplicate detection for Jira issues work using stack traces?▼

Duplicate detection works by extracting error signatures from a stack trace and executing parallel JQL queries against a Jira instance. It searches for both open and resolved issues that match the extracted error signature to identify potential duplicates.

Do I need the atl CLI tool to search for existing Atlassian Jira tickets?▼

Yes, you need the atl CLI tool configured with appropriate read-only access to your target Jira instance. This access allows the skill to execute JQL queries and search for existing bug reports within your Atlassian environment.

Can I link a new bug report to an existing regression in Jira?▼

Yes, you can link new bug reports to existing regressions in Jira. After searching for duplicates, the skill provides a structured workflow to comment on existing issues, link bugs to regressions, or create a new ticket only after verification.

What's the best way to triage potential software bugs in Jira?▼

The best way to triage potential software bugs in Jira is to automate error signature extraction and run parallel JQL queries to find related issues. This verifies if a bug already exists before creating a new ticket.

Why should I remove volatile data from error signatures before searching Jira?▼

Removing volatile data from error signatures before searching Jira improves search accuracy by isolating the core error patterns. This ensures the parallel JQL queries find genuinely matching issues rather than getting skewed by dynamic runtime information.