It is necessary to set up automatic movement of a task from one project to another when an event occurs, so that attached files are copied.
Moving an issue is not a trivial action - the project and issue type are fundamental structural attributes of an issue and hence require a load of checks and usually updates in order to change the shape of the issue from the old to the new.
I would want to question why you are moving issues between projects. It can be a perfectly valid thing to do (mostly when housekeeping or correcting things raised in the wrong place), but if you are trying to do it as part of a standard process flow, then you have a broken process, and you should look to revise that so that you don't move issues.
@Nic Brough -Adaptavist- Thank you for your answer. We decided to revise our processes.
It looks like you're new here. Sign in or register to get started.
