move task from one project to another

[hassanalsafi]

Good morning ...

I  have two projects (Reports and Accounts) when the task reach the done stages I want to move it from the Report project to the Accounts Project with all the data but when I try to moving it I don't receive any data just the task with Empty fields , and in the same time I don't want the task to disappear from the the Reports project anyone know how to do that ??

[Jack Brickey]

Hi @hassanalsafi , assuming you have all of the same fields in both projects then moving an issue between the two should retain all field data, comments and attachments. Any missing fields will result in that data being lost obviously. As for keeping the issue in the original report that is only possible if the report filter includes the new project.

stepping back here, it would be great to understand why you were doing the move. Understanding this bit of data might help me provide a alternate suggestion, if warranted.

[Ste Wright]

Hi @hassanalsafi 

Can you walk us through the steps of how you are moving the issue between Projects? What do you see in the move screen?

And...

• Are the Projects different project types (Team-managed or Company-managed)? Or the same?
• Are the Projects from different products (Software, Work Management, Service Management)? Or the same?
• Are the designs the same between the two Projects? In particular, the Screens and Fields?

---

It would also be great to understand your process here; why are you moving the issue between Projects, rather than having one end-to-end workflow? Or cloning the issue into the new Project and retaining the closure in the first?

Ste

[Sreenivasaraju P]

Hi @hassanalsafi ,

Instead of moving the ticket, you can create an automation rule to create new ticket in your Accounts project (when your ticket in the reports project moved to Done status).  So the ticket in Reports project will remain.

[Joe Pitt]

As @Sreenivasaraju P said, create a rule. An issue can't exist in multiple projects