Project
YouTrack
Priority
Major
Type
Feature
State
Duplicate
Assignee
Unassigned
Subsystem
Workflow
Fix versions
3.1, Energy-Bugfix
Fixed in builds
No Fixed in build
Affected versions
No Affected versions
Browser
Any Browser
OS
Any OS
Verified in build
Not verified
Verified by
Nobody
Affected builds
No affected builds
Reviewed by
No reviewed by
Story points
Undefined
Value
Undefined
Marketing value
No marketing value
  • Created by   Andrei Oprea
    4 years ago (17 Apr 2008 18:34)
  • Updated by   Vadim Gurov
    9 months ago (22 Aug 2011 15:16)
 
JT-56 Proper Linking of duplicates
7
Issue is visible to: All Users
  The issue is visible to the selected user group only
Instead of just marking a duplicate issue as solved, link the two together in a smarter fashion:
  • keep the status of the duplicating issue in sync with the duplicated issue (so the duplicating issue goes through the same transitions)
  • use the notifications rules on the duplicating issue for messages/events on the one it duplicates.

From a user's point of view, the issue is not "fixed" just because there's another one talking about the same problem. All the activity notifications should keep flowing without the user having to manually set watches for the new issue.
Comments (3)
 
History
  
Linked Issues (?)
 
Vadim Gurov
  Vadim Gurov
28 May 2009 15:17
2 years ago
Yegor Yarko
  Yegor Yarko
14 Oct 2009 16:22
2 years ago
See also JT-2148: should probably add voters and watchers of duplicated issues to the remaining (and on removing duplicate link - remove voters/watchers)
Roman Starkov
  Roman Starkov
01 May 2010 11:59
2 years ago
I think it should be optional. It really depends on how you use YouTrack. If it's completely public then I would much rather close the duplicate to give a strong indication that further contributions are discouraged and should instead go to the "main" issue. Also, what about searching - if I search for all open issues I really don't want to see the open duplicates.