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.
Atlas Camp is our developer event which will take place in Barcelona, Spain from the 6th -7th of September . This is a great opportunity to meet other developers and get n...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG