Title We should be able to merge issues
Type feature Module tracker
Severity inconvenience Platform N/A
Keywords issue edit Nosy List stephen
These controls should only be changed by committers and tracker administrators.
Status assigned   Reason
Priority normal   Assigned To

Created on 2008-01-11.09:08:16 by stephen, last changed 2009-02-28.06:48:05 by stephen.

msg1049 [hidden] ([hidden]) Date: 2009-02-28.06:48:05
Reverting merges is going to be hard without implementing a full VCS backend.  But then what 
happens to the RDBMS?  This case should be rare.  So I think the right thing to do is make "Make 
a copy" work.
msg661 [hidden] ([hidden]) Date: 2008-04-05.04:49:55
  Message-ID: <>
And we should be able to revert the merge action later if
something wrong in merge or they should not be merged at all.
msg38 [hidden] ([hidden]) Date: 2008-01-11.09:08:16
1.  Superseded issues should actually become part of the superseding
issue in many cases.  Does this happen?  If not think about making
it so.

2.  When multiple issues are superseded, they should become a single issue.
Date User Action Args
2009-02-28 06:48:05stephensetstatus: new -> assigned
messages: + msg1049
2008-04-05 04:49:55FKtPpsetmessages: + msg661
2008-01-22 18:26:52stephensetplatform: + N/A, - N/A
keyword: + issue edit
2008-01-11 09:08:16stephencreate