In fact what I meant in that thread is that when you merge 2 tickets, you loose the audit log of 1 of the tickets.
It's better to also merge the audit logs (maybe with the ticket ID so you can see which ticket had what ID before & after).

example:
* ABC received
* ABC replied
* ABC new message
* DEF received
* ABC merged with DEF

Yeah, that's what I was trying to convey, Steven, I just failed miserably at it... ;-)

The actual bug to fix is that the audit logs need merged, and it's a possibility that we may want to indicate which original ticket id each log entry was referring to.

Since the audit log is a plugin, and 'merge' is in core, we just need to create an event point for merge that the logging plugin can observe. I've added this to my usability list.

We might want to update the ticket updated date and include the fact a merge took place in the audit log when we perform the merge as well. Mirko pointed out that the updated date doesn't change in this forum thread: http://www.cerb4.com/forums/showthread.php?p=3237

Mirko (from forum link mentioned above) would prefer that the ticket update date be changed to the most recent update date of the tickets being merged, rather than the time the merge actually took place.

Consolidating Merge issues. CHD-435 is about Audit Logs needing to be merged, and how that merge should take place. See: http://www.cerb4.com/forums/showthread.php?t=401

Comments:
=======================
  Comment by Steven Van Ingelgem [03/Jan/08 01:06 PM] Delete
[ Permlink ]
In fact what I meant in that thread is that when you merge 2 tickets, you loose the audit log of 1 of the tickets.
It's better to also merge the audit logs (maybe with the ticket ID so you can see which ticket had what ID before & after).

example:
* ABC received
* ABC replied
* ABC new message
* DEF received
* ABC merged with DEF

Comment by Dan Hildebrandt [03/Jan/08 01:32 PM] Delete
[ Permlink ]
Yeah, that's what I was trying to convey, Steven, I just failed miserably at it... ;-)

The actual bug to fix is that the audit logs need merged, and it's a possibility that we may want to indicate which original ticket id each log entry was referring to.

Comment by Jeff Standen [03/Jan/08 11:47 PM] Delete
[ Permlink ]
Since the audit log is a plugin, and 'merge' is in core, we just need to create an event point for merge that the logging plugin can observe. I've added this to my usability list.

Comment by Mike Fogg [21/Feb/08 03:00 PM] Delete
[ Permlink ]
We might want to update the ticket updated date and include the fact a merge took place in the audit log when we perform the merge as well. Mirko pointed out that the updated date doesn't change in this forum thread: http://www.cerb4.com/forums/showthread.php?p=3237

Comment by Mike Fogg [28/Feb/08 03:01 PM] Delete
[ Permlink ]
Mirko (from forum link mentioned above) would prefer that the ticket update date be changed to the most recent update date of the tickets being merged, rather than the time the merge actually took place.

Please watch CHD-174 for updates