triage-issue

Search Jira with multi-angle JQL queries to detect duplicate issues.

4|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/baleen37/bstack --skill triage-issue-baleen37
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage-issue
Source: https://github.com/baleen37/bstack/tree/main/plugins/jira/skills/triage-issue
Command: npx skills add https://github.com/baleen37/bstack --skill triage-issue-baleen37

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Intelligently triage bug reports and error messages by searching Jira for duplicates and offering to create new issues or add comments to existing ones.

Core Features & Use Cases

  • Duplicate detection across Jira issues
  • Multi-angle search to find similar past issues and assess fix history
  • Guidance on whether to create a new bug or comment on an existing ticket
  • Contextual summaries to expedite triage decisions

Quick Start

Provide the bug details and let the system search Jira for duplicates, then it will suggest whether to create a new issue or comment on an existing one.

Frequently Asked Questions about triage-issue

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

FAQPage Schema
How do I automatically find duplicate bugs in Jira?

You can find duplicate Jira bugs automatically by running multi-angle JQL queries that search for similar issues, shared components, and fix history to assess whether a reported bug is new or a duplicate.

How does Jira bug triage automation work?

Jira bug triage automation works by searching for duplicates and similar past issues using multiple search patterns, evaluating fix history, then presenting clear recommendations to create a new issue or comment on an existing ticket.

What is the best way to add comments to existing Jira tickets instead of creating duplicate issues?

The best way to add comments to existing Jira tickets is to search for similar issues using multi-angle JQL queries, evaluate shared components and fix history, then execute the comment action on the matched ticket when confirmed.

Can I assess Jira fix history when triaging a new bug report?

Yes, you can assess Jira fix history when triaging a new bug report by evaluating multi-angle search results to identify similar past issues, shared components, and previous resolutions before deciding to create a new issue.

When should I not create a new Jira issue during bug triage?

You should not create a new Jira issue when there is insufficient context for the bug, or when multi-angle JQL search results identify existing duplicate or related tickets that you can comment on instead.