Clone and Move plugin / notifications

[Neal Applebaum]

We have a support project which often (unfortunately) leads to the creation of tickets in a development project. So, the clone and move plugin would be helpful in reducing the copy/paste activities by cloning the support ticket and moving it to the development project in one step. We had tried the original clone and move plugin for v3, and now the new one for v6, but both have the same problem for us: It does it all in two steps: first clone, then move. And the problem with this is that after step 1, the clone, a notification is created based on the reporter, so our client receives a notification e-mail about the issue being created when they did not in fact create one. So, I am just wondering if this is a use case faced by other consumers of this add-on.

Thanks.

[Laura Nelson]

When we first installed this plugin we did not receive the notifications when doing the clone and move, but with one of the recent updates the notifications are now being sent out and are creating issues with our Service Desk.

[Neal Applebaum]

So, if I understand your post correctly, you are having the same issue as I, where issues are being created in the service desk that you don't want?