Move a TO DO task between different projects

[gonztirado]

Maybe can be a nice feature if we can move a task to a different project.

For example, we have a project with a task, but finally, this task must be assigned to another team with a different kanban board.

[dqn9t2]

I think this is good, bc some project have the same tasks, it will save alot of time for us if we dont have to remake them all.

[marcelfolaron]

Yes, we need that. I assume we'd want the option to copy and move the todo/milestone?

[dqn9t2]

Yes. Copy from project to project, it will save time. Thank you for your work!

[jakimfett]

Having the ability to move and duplicate an individual item, be it a research hypothesis or an idea, would be rather useful, and would indeed save time during project setup.

Being able to move or duplicate an entire research board, or multiple to-do items, between projects or subprojects would also be rather nice.

[gonztirado]

I agree with @jakimfett. All the elements should be transferable or copied between projects

[YQGong]

Is there any progress on this feature? This could be very useful.

[MaraScott]

Looking forward to that feature

[compumatter]

I am in need of this feature as well. This is another one of those core needs that come up over and over again. You've created a project, some todo's and at some point the scope of the project changes and you need to move that Todo and its innards to another project / column. At present it's a painful copy / paste anytime that comes up and it comes up often.

I have added a video that makes the issue more clear but I suspect it is not needed since so many have commented on this post. I can see this is an old post though so maybe it will help bump it forward.

• https://www.youtube.com/watch?v=aIp8AQfxbdk

[romzeon]

Hey!
Any progress on this feature?
Thanks for your work!

[romzeon]

Hey! Any progress on this feature? Thanks for your work!

I've found some workaround using a database.
You find a project that you need to assign to a task in zp_projects table, get the project id.
Then you can update a field projectId in zp_tickets table with a new project id what you have got in prev. step.

It works for me.