move task to another project

[dendo151]

I have a project plan already started with some resource time. I'm asked to
split the project into three seperate plans. How can I do this and carry
foward some of the resources time?

 

[Marc Soester]

Hi dendo151,

There is no functionality which wouild allow you this, but you may want to
copy the project 3 times and amend each project the way you want to run the
projects from now on.

 

[dendo151]

Marc,

Thanks for the info.

I am able to copy the project multiple time. However, I cannot remove any
task that has time applied. Is there an workaround for this? Also, how does
this affect the resources that now have new tasks that show applied time? Or
does Project Server know that they all reference the same timesheet entry?

Thanks,

Dave

 

[Marc Soester]

Hi Dendo151,

You should still be able to delete tasks that have actuals.

The System now assumes that the resource is allocated to the 3 projects. You
will need to make sure ( possibly via leveling) that the resources are not
overallocated

I hope this helps

 

[dendo151]

Marc,

When I attempt to delete a tast on the newly copied project plan, I get the
following message: "Cannot delete or reassign tasks or assignments with
protected actuals. This task/assignment has protected actuals so it cannont
be deleted/reassigned."

Thoughts?

Thanks,

Dave

 

[Marc Soester]

hi Dendo151,

I see.....You guys are using the PWA timesheet. Not sure if my "method"
works in this case. I will test some things and if I find something will get
back to you
sorry

 

[Gary L. Chefetz [MVP]]

Dendo:

I'll jump in here with some strong opinions about cloning projects. I
believe that cloning non-template projects that have been published to
Project Server is something that users should never do, except when saving a
project off the server for the purpose of replacing the original one on the
server in a one-to-one swap. This is particularly troublesome in a Managed
time period environment but a bad idea overall because there's data in the
project binary record that can/will cause problems down the road.

The correct way to handle your plan split challenge is a bit time consuming
and explaining it in great detail is probably going to take more time than I
have at the moment. Essentially, you need to close out assignments in the
original plan and recreate them in the new plans. Do not copy complete tasks
rows from one project to another during the process. This can cause Unique
ID problems in the database. It's safe to copy the task names. If your
planning is based on duration, it's safe to copy those values as well. If
your planning is based on effort, you can copy work values and paste them.
Just stay away from full row copying.

 

[dendo151]

Gary,

Thanks for insight. I wondered what the repercussions would be if I did
copy a project and how it would impact the references between the project
tasks and work tables.

So if I close the initial project and create new projects and reenter the
tasks, how do I compensate for the hours already applied to those task that
have time? Is there a way to insert or retain a fixed “pre duration†time
spent on a new task?

Thanks,

Dave

 

[Marc Soester]

Thanks Gary, that is something I did not know. I have "cloned" Projects in
the past, but not based on PWA timsheeting.

 

[Gary L. Chefetz [MVP]]

Dave:

With managed time periods, and in the interest of preserving the historic
records, you should leave the actual work where it is. If you agree with
that, then you have at least two choices: complete all started tasks in the
original plan, or close them out and continue them in the new plans. For the
latter scenario, I'd probably use links between the task parts between the
plans. Where you have tasks split between plans, you may have to live with
having to look at both plans to determine the aggregate duration and
aggregate total of work hours.