You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
pm close should support --duplicate-of flag for proper duplicate item tracking #183
When closing duplicate PM items, there is no standardized way to track which item is the canonical/original. The close reason text is freeform, making it impossible to programmatically trace duplicate chains.
Current Behavior
pm close pm-xyz2 'Duplicate of pm-abc1'
This creates a close entry in history but doesn't establish a machine-readable link between the duplicate and the original.
Desired Behavior
pm close pm-xyz2 --duplicate-of pm-abc1
This should:
Set a duplicate_of reference field on the closed item
Generate standardized close reason: 'Duplicate of pm-abc1'
Add a comment on the original item: 'pm-xyz2 closed as duplicate'
Support pm deps to trace duplicate relationships
Validate that the target item exists and is not itself a duplicate
Impact
In our audit we found 2 duplicate items and there is no structured way to mark them. Across 1075 items, duplicate detection and tracking is essential for PM hygiene.
Activity
fix(diagnostics): suggest structured --duplicate-of in duplicate-issu…
unbraind commentedon Jul 11, 2026
pm tracker item:
pm-xnkd— pm close --duplicate-of: structured duplicate tracking with auto-populated closure fields (pm close should support --duplicate-of flag for proper duplicate item tracking #183, Bug: pm close validation warnings for resolution fields on items that are straightforward duplicates #160)