jira-duplicate-detection

# Jira Duplicate Detection Skill

This skill provides patterns for detecting and handling duplicate tickets in Jira to maintain a clean backlog.

## Why Duplicate Detection Matters

- Prevents wasted effort on already-reported issues
- Consolidates discussion and context
- Improves reporting accuracy
- Reduces backlog clutter
- Ensures fixes address all related reports

---

## Detection Process

### Step 1: Extract Key Terms

From the potential new ticket, identify:
- Core functionality/feature area
- Error messages or codes
- Affected components
- User actions/scenarios

### Step 2: Build Search Queries

Create multiple JQL queries with different approaches:

**Exact phrase search**:
```
project = PROJ AND text ~ "exact error message"
```

**Keyword combination**:
```
project = PROJ AND text ~ "payment" AND text ~ "timeout"
```

**Component-based**:
```
project = PROJ AND component = Checkout AND text ~ "error"
```

**Reporter-based** (same person might report twice):
```
project = PROJ AND reporter = currentUser() AND created >= -30d
```

### Step 3: Review Results

For each potential match:
- Compare descriptions in detail
- Check acceptance criteria overlap
- Review comments for additional context
- Consider different descriptions of same issue

### Step 4: Present Findings

```markdown
## Potential Duplicates Found

### High Confidence (likely same issue)
| Key | Summary | Created | Status | Similarity |
|-----|---------|---------|--------|------------|
| PROJ-123 | Payment timeout on large orders | 2024-01-10 | Open | 90% |

### Medium Confidence (possibly related)
| Key | Summary | Created | Status | Similarity |
|-----|---------|---------|--------|------------|
| PROJ-456 | Checkout errors intermittently | 2024-01-05 | In Progress | 60% |

### Recommendation
PROJ-123 appears to describe the same issue. Recommend:
1. Add any new context to PROJ-123 as a comment
2. Link your report as a duplicate
3. Watch PROJ-123 for updates
```

---

## Search Strategies

#