Replying to a request's notification after that request has been moved will create a new request instead

Issue Summary

When portal customers receive a notification from their request, they can reply it to add a new comment via email.

But, if you move that same request to a different JSD project, and the customer replies to a notification after that, the customer's email will generate a new request in the original project instead of adding a comment to the issue that was moved.

Steps to Reproduce

• Create a request as a portal customer in project A;
• As a JSD agent, add a comment to request A so the customer will receive a notification;
• As the agent, move the request A to a different JSD project;
• As the portal customer, reply to the previous request A's notification (the comment added by the agent).

Expected Results

The email reply from the portal customer will be added as a new comment in request A.

Actual Results

A new request B is created in the first project.

Workaround

If you add a new comment on request A after you move it to a different JSD project, the customer will receive a notification and a new thread will start.

You can also use Project automation to do that automatically when the requests are moved to the second project: