moving issues with a redirection rather than simple close and duplicate
Release notes
Actually, when you move an issue in another project, it is duplicated in this other project and closed in its initial project.
This can lead to confusion as the discussion can continue in the first closed issue. Really easily in fact as you can answer or clic on the link in your emails from notifications of the first issue.
Also, any links to the first issue are then disturbing, as you see then as closed, but the duplicated issue can still be open.
This leads in a very confusing state.
Problem to solve
A moved issue is duplicated, that can lead to confusion.
Intended users
Anyone.
User experience goal
Proposal
Moving an issue really moves the issue in another project, and the url of the issues in the previous project is stil working with an automatic redirection to the new issue.
Any links to the url from the initial project will still be ok, and its status too (open/closed).
The only possible drawback is the old issue won't be longer visible in the initial project list. But is it really a problem? It is closed anyway, so not really useful in a board, and on the contrary, if you move an issue, isn't it not to see it where it was any longer?