Losing messages when resubmitting from DLQ.

Resubmitted DLQ messages are lost. I have customer that would like to "retry" messages and have same behaviour as the fix in https://issues.apache.org/jira/browse/AMQ-3405

Here's customers comment and business case for this request:

Doing a Copy/Delete wouldn't be practical for some of the issues I deal with where the end point is down and thousands of messages get put into the DLQ. In those cases, doing a copy and then making sure they all succeeded and then only deleting those messages which were successful (and not the ones that failed again, because I assume the copied ones would not replace the existing, but have their own uniqueness in the DLQ)

How can I go about requesting a change for 'retry message' which has the same fix as https://issues.apache.org/jira/browse/AMQ-3405?

Current workaround:
Workaround is to actually do a Move, which this one indicates was fixed to work: https://issues.apache.org/jira/browse/AMQ-3405
It is the retry which causes the issue.
So, I do have a workaround with the Move action.