darcs

Issue 1919 automerge duplicate tickets

Title automerge duplicate tickets
Priority feature Status given-up
Milestone Resolved in
Superseder Nosy List Serware, dmitry.kurochkin, kowey
Assigned To
Topics BugTracker

Created on 2010-08-14.13:27:25 by kowey, last changed 2017-07-31.00:03:47 by gh.

Messages
msg12175 (view) Author: kowey Date: 2010-08-14.13:27:23
I think this could be handled by adding a status detector to tickets.  
Whenever you set status to duplicate, we could look at the superseders of 
this ticket and merge our nosy list into them.  We don't need to add a 
new message because the history will keep track of the merge  (unless we 
really want to be explicit about it).
History
Date User Action Args
2010-08-14 13:27:25koweycreate
2017-07-31 00:03:47ghsetstatus: needs-implementation -> given-up