jira-duplicate-detection

Detect duplicate Jira tickets using JQL search strategies and similarity guidelines.

8|2|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/bradtaylorsf/alphaagent-team --skill jira-duplicate-detection
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira-duplicate-detection
Source: https://github.com/bradtaylorsf/alphaagent-team/tree/main/plugins/aai-pm-jira/skills/jira-duplicate-detection
Command: npx skills add https://github.com/bradtaylorsf/alphaagent-team --skill jira-duplicate-detection

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps prevent the creation of duplicate Jira tickets by providing strategies and queries to detect similar issues before a new ticket is submitted, ensuring a cleaner and more efficient backlog.

Core Features & Use Cases

  • Duplicate Detection Strategies: Offers various JQL query patterns for searching existing tickets based on keywords, error messages, components, and reporters.
  • Similarity Assessment: Provides guidelines for evaluating the confidence level of potential duplicates.
  • Handling Duplicates: Outlines steps for linking, commenting on, and closing duplicate tickets, as well as for handling related but not identical issues.
  • Use Case: Before submitting a bug report, use this skill's search queries to check if a similar issue has already been reported, saving you and your team time.

Quick Start

Use the jira-duplicate-detection skill to search for potential duplicate Jira tickets related to 'payment errors' in the 'PROJ' project.

Frequently Asked Questions about jira-duplicate-detection

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

FAQPage Schema
How do I find duplicate Jira tickets in my backlog?

To find duplicate Jira tickets, use targeted JQL search strategies to query existing issues by keywords, error messages, components, and reporters. This systematic search identifies potential redundant issues before submitting new bug reports.

What is the best way to prevent duplicate issue reporting in Jira?

Preventing duplicate issue reporting in Jira requires searching for existing similar issues using JQL queries before ticket submission. This proactive detection approach maintains a clean backlog by consolidating redundant issue information early.

How do I assess the similarity of potential duplicate Jira tickets?

Assessing similarity of potential duplicate Jira tickets involves evaluating the confidence level of matches using provided guidelines. These criteria help determine whether issues are exact duplicates or just related but distinct problems.

What steps should I take to handle and close duplicate Jira issues?

Handling duplicate Jira issues involves linking the redundant tickets, adding comments to document the duplication, and closing the unnecessary ticket. This consolidation process ensures all issue information remains centralized.

Can I use JQL to search for similar Jira tickets based on error messages?

Yes, you can use JQL to search for similar Jira tickets by querying specific error messages, components, and keywords. These query patterns help surface existing reports that match the issue you are about to submit.

When should I link related Jira tickets instead of closing them as duplicates?

You should link related Jira tickets instead of closing them as duplicates when similarity assessment guidelines indicate the issues are related but not identical. This distinction preserves distinct problem contexts while maintaining backlog visibility.