K
Karl Hungus
Three of our Project Managers have experienced
this issue. They will import a newly created local project to the
server using the enterprise import tool. They are also listed as the
resource for some of the tasks. All is well until they go to the Tasks
page in PWA. Instead of the new tasks being listed under the newly
imported project name, tasks lists the project name as "NA". If they
import a second project, the second project's task are then merged
under the same "NA" listing in Tasks.
This only seems to be happening to the publisher of the project. The
other resources see the tasks listed properly in Tasks with the correct
project name header.
Has anyone else experienced this issue before? I can not seem to find
any information relating to this issue.
this issue. They will import a newly created local project to the
server using the enterprise import tool. They are also listed as the
resource for some of the tasks. All is well until they go to the Tasks
page in PWA. Instead of the new tasks being listed under the newly
imported project name, tasks lists the project name as "NA". If they
import a second project, the second project's task are then merged
under the same "NA" listing in Tasks.
This only seems to be happening to the publisher of the project. The
other resources see the tasks listed properly in Tasks with the correct
project name header.
Has anyone else experienced this issue before? I can not seem to find
any information relating to this issue.