I believe audit log merges were corrected as part of CHD-435 and subsequently CHD-174. In any case when I verified the CHD-174 fix, I was able to verify they are being handled correctly now.
There was a leftover request buried in the comments asking that we find a way to clearly preserve which audit log entries came from which ticket through an ID or label system of sorts.
example from Steven Van Ingelgem in CHD-435:
* ABC received
* ABC replied
* ABC new message
* DEF received
* ABC merged with DEF
Note:
This request was originally defined in CHD-435 which was closed in favor of combining it with another larger merge fix in CHD-174. As part of resolving & closing CHD-174 I'm creating new issues out of buried comment requests. This is an odd one because CHD-435 for the most part had it covered. Unfortunately it had a lot of "baggage" requests in the comments that I want to strip away and would rather not delete them and add to the confusion.
If a ticket is deleted because it has been merged into another one would it be possible to have the audit log for the deleted ticket show something like "merged into ticket xyz by Fred Bloggs"?
I've just come across a ticket from a customer which is marked as deleted. I've looked at the requester history and can't see anything with a similar title so I can't work out if it was deleted by accident or merged into something else (and if so, what was it merged into!)
And how about a similar audit message on the "other" side of the merge? ie showing that a ticket was merged into this one.
Perhaps related to this, the current audit trail for a merged ticket seems to totally migrate to the new ticket. That means, from what I can see, the new ticket has entries like "closed = true, deleted = true" which applied to the merged ticket not the current one (ie the most recent event on the real ticket shows up as "deleted = true" and "closed = true"
even though the ticket is not deleted or closed)
New Feature
Open
[Activity Log] Label which entries came from which ticket after a merge
