I believe this was tangentially fixed by CHD-1191.

I don't think this was actually fixed for custom fields or auto-responses. Same problem as before, the final custom field setting will not replace the first one, and the new ticket auto-response from the final destination group is not sent.

I'm going to leave this resolved and check one more time when the next version is released into SVN. That's just to make sure I'm not accidentally using an older build in Git.

Ok, I just checked on the latest Dev SVN checkout, where all the rest of the lingering resolves were verified, and no it's still not fixed.

See my last comment.

This is the difference between 'Mail Routing' and 'Inbox Filtering'. The parser runs routing rules when new mail comes in and uses that logic to determine what auto-reply to send. Asynchronously, the mail filters for that routing destination may move the ticket into another group.

The problems with sending that final group as the auto-reply (at the moment) are:
(1) It's asynchronous, we don't know from the parser when that event is firing
(2) The 'move' event is generic and doesn't know that it's triggered from the parser or if it's triggered from workers moving mail manually. We probably don't want to send multiple autoreplies to people every time their ticket moves in the helpdesk, so this is something we need to think about.

I'm going to push this to the next milestone since it's a pretty significant change for the tail end of the 4.2 #1 release.

99% sure this is the same problem, make sure you update this thread when completed.
http://www.cerb4.com/forums/showpost.php?p=10618&postcount=1

Also confident this is the same issue. Update this thread if and when we change anything.
http://www.cerb4.com/forums/showpost.php?p=11943&postcount=6

VA work differently and no longer have this issue.

Thanks
Robert