What is the best way to include task updates when copying or moving task to another project?

[catherineh70969]

We need to move items from a very lengthy timeline in one project to a new project. Because some pieces of this work are in flight currently, we need to retain all updates, documents, status, % complete data though. I'm finding an issue with migrating Updates when either Copy or Move is used, though. Only the project-level updates are carried over, but all other data we need is in place.

Is there another approach, or something we are missing, that would retain all task or issue-based Updates from the original project when these objects are moved to a new project?

Thanks in advance! 😎

[Doug_Den_Hoed__AtAppStore]

Hi Catherine,

I wonder if not preserving Updates "under" a Task when a Task is moved is As Designed (for some reason, such as "when the updates were made, contextually, the Task was part of the former Project, so the updates belong with that Project"), or is actually a bug. Either way, I'd suggest you raise a help desk ticket to find out, and am interested to hear what you learn.

That aside...

If you can create a NOTES report that retrieves the updates in question before you move a Task, if you export them to Excel, then after you move the Task, you could also then adjust the Excel spreadsheet and either kickstart or use our Excel Updater solution to reinstate those NOTES under the moved Task, for context...noting (having done so) that because the Entry Date and Entered By are immutable (e.g. "today" and "you", respectively), that it is helpful to add a suffix to the Note Text with the original values (e.g. "[On yyyy-mm-dd hh:nn by username]...").

Regards,

Doug