issues-deduplication

Detect duplicate YouTrack issues and link them to a primary issue.

10.2k|811|Updated Mar 9, 2011
One-click install
npx skills add https://github.com/JetBrains/ideavim --skill issues-deduplication
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issues-deduplication
Source: https://github.com/JetBrains/ideavim/tree/main/.claude/skills/issues-deduplication
Command: npx skills add https://github.com/JetBrains/ideavim --skill issues-deduplication

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Organizes and cleans YouTrack issues by automatically identifying duplicates and consolidating related bug reports into a single primary issue to streamline trackers.

Core Features & Use Cases

  • Identify duplicates across projects and link them to a chosen primary issue.
  • Respect customer-tagged issues, avoid duplicating those for customer-tracking purposes.
  • Preserve unique information by transferring context (reproduction steps, logs) to the primary issue and leaving a courteous update on duplicates.

Quick Start

Identify related issues and link duplicates to a selected primary issue.

Frequently Asked Questions about issues-deduplication

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

FAQPage Schema
How do I deduplicate issues in YouTrack and consolidate related bug reports?

To deduplicate YouTrack issues, you identify related bug reports and link them as duplicates to a selected primary issue. This process consolidates context by transferring unique information like reproduction steps to the primary issue and leaving a courteous update on duplicates.

Can I detect duplicate issues across different YouTrack projects?

Yes, cross-project duplicate detection is supported. You can identify duplicates across different YouTrack projects and link them to a single primary issue, ensuring all related tickets are consolidated while preserving their unique context.

How are customer-tagged issues handled during YouTrack issue deduplication?

Customer-tagged issues are kept separate and are not merged during deduplication. This rule ensures that tickets specifically tagged for customer-tracking purposes maintain their independent visibility and are not linked as duplicates.

What happens to closed issues when streamlining YouTrack by deduplicating issues?

The deduplication process avoids merging closed issues. It enforces this constraint to prevent altering resolved ticket histories, focusing solely on consolidating active bug reports into a single primary issue.

How do I transfer unique context like reproduction steps when merging duplicate YouTrack tickets?

When linking duplicate issues, unique information such as reproduction steps and logs is transferred to the chosen primary issue. This preserves all valuable context while a courteous update is left on the duplicate tickets.

Does issue deduplication maintain a single primary issue when linking related tickets?

The process maintains a single primary issue for each set of duplicates. By enforcing this rule, it ensures that only one primary ticket exists, preventing circular linking and keeping the YouTrack tracker streamlined.