Menu
Patterns for detecting duplicate Jira tickets before creating new ones and handling existing duplicates.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Patterns for generating Gamma.app-compatible slide deck markdown from GitHub data for customer-facing account management presentations
Patterns for generating Gamma.app-compatible slide deck markdown from Linear data for customer-facing account management presentations
Patterns and templates for creating sprint/project retrospective reports from Jira data with time tracking and blocker analysis.
Multi-platform Electron build configuration - esbuild bundling, electron-builder setup, and distribution
Integrate external CLI tools (Claude, Node, npx) in Electron apps with proper PATH handling
Handle native Node.js modules in Electron - better-sqlite3, sharp, keytar packaging patterns
| name | jira-duplicate-detection |
| description | Patterns for detecting duplicate Jira tickets before creating new ones and handling existing duplicates. |
This skill provides patterns for detecting and handling duplicate tickets in Jira to maintain a clean backlog.
From the potential new ticket, identify:
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
For each potential match:
## 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
Best for bugs with specific error text:
project = PROJ AND
text ~ "TypeError: Cannot read property" AND
created >= -90d
ORDER BY created DESC
Best for feature requests:
project = PROJ AND
text ~ "notification" AND text ~ "email" AND
type in (Story, Task, Improvement)
ORDER BY created DESC
Best when you know the affected area:
project = PROJ AND
component = "User Management" AND
text ~ "password reset"
ORDER BY created DESC
Search for alternative descriptions:
# If searching for "slow performance"
project = PROJ AND (
text ~ "slow" OR
text ~ "performance" OR
text ~ "latency" OR
text ~ "timeout" OR
text ~ "hang"
)
Best for ongoing issues:
project = PROJ AND
labels in (checkout, payment) AND
created >= -14d
ORDER BY created DESC
Indicators:
Action: Recommend closing as duplicate
Indicators:
Action: Recommend linking as "relates to"
Indicators:
Action: Note similarity, proceed with new ticket
Additional report from [reporter]:
[New context, steps, or information not in original]
Confirming this is still an issue as of [date].
Good for searchability:
h2. Error Details
Error message: "TypeError: Cannot read property 'id' of undefined"
Error code: ERR_CHECKOUT_001
Affected endpoint: POST /api/checkout
h2. Steps to Reproduce
1. Add item to cart
2. Go to checkout
3. Click "Place Order"
4. Error appears
project = PROJ AND
created >= -7d AND
status = Open
ORDER BY created DESC
project = PROJ AND
(summary ~ "duplicate" OR description ~ "duplicate")
project = PROJ AND
component = [Component] AND
created >= -30d AND
issueLink IS EMPTY
ORDER BY created DESC
project = PROJ AND
resolution = Duplicate AND
resolved >= -90d
ORDER BY resolved DESC
Before creating a new ticket: