Task Provisioning to Sharepoint Team Services

[Dan]

If after publishing an Enterprise Project, should we expect to see Project
Tasks published to the provisioned Team Services Web for the project? We
don't. In fact the Share Point Team Services web provisioned for the project
does not even have Tasks as an available list! Also, when we create tasks
for the project in Share Point Team Services we are not able to link it to a
Project Task as Share Point returns a message stating that "Tasks have not
been published, or permission has not been granted." Well, I am the
administrator so I'm wondering what we're doing wrong?

Regards,
Daniel Latrimurti

 

[Matt S.]

After publishing a project to the Project Server, a SharePoint subweb should
get created autmatically - if you have configured it to do so. But when the
subweb is created, you will not see any Project related tasks in the subweb.

SharePoint is a why to collaberate with other members of the team that are
assigned to that specific project plan. This gives them access to upload
documents, and add issues that are specific to the project plan. Then you
can link these documents and issues to each other or to tasks within the
project plan.

Typically when using SharePoint you want to be logged onto Project Web
Access as member that has been assigned tasks in the plan and the account
is using Windows authentication.

SharePoint Team Services is based off of Windows authentication. The
product will not accept Project Server accounts, and if you use project server
accounts you will encounter various errors when using SharePoint.

Matt S.
Project Server Specialist
(e-mail address removed)

 

[Dan]

Hi Matt,

Thanks for the reply. Our configuration is not to provision a project
sub-web at the time of project publication. We prefer to create the subwebs
from the SharePoint administration pages. This is mainly a timing
consideration.
Are there tradeoffs between the two methods?
As a commentary, I think Microsoft has missed the mark by not allowing tasks
to be published from Project to a provisioned Share Point Web. Just my
opinion, because from a users perspective, simplicity and ease of use is key
to getting participation, usage and support when deploying such a business
system, hence there is benefit in being able to provide "all" relevent team
data via a single web site and since Share Point is a, team based
collaboration application, it would make sense from a usability perspective
to use Project Server as the engine with SharePoint as the end user
interface. Anyway, just my opinion.


Given this is the recommended manner for integration simply to publish a
hyperlink on the Sharepoint web back to the project task list?
Also, though this may not be the forum, our Share Point Web does not have a
task list. Is this becuase it is provisioned and the assumption is that
tasks will be originating from Project Server?

After publishing a project to the Project Server, a SharePoint subweb should
get created autmatically - if you have configured it to do so. But when the
subweb is created, you will not see any Project related tasks in the subweb.

SharePoint is a why to collaberate with other members of the team that are
assigned to that specific project plan. This gives them access to upload
documents, and add issues that are specific to the project plan. Then you
can link these documents and issues to each other or to tasks within the
project plan.

Typically when using SharePoint you want to be logged onto Project Web
Access as member that has been assigned tasks in the plan and the account
is using Windows authentication.
We are using Windows authentication for Project Server and all Share Point
users are based on the same domain credentials.

SharePoint Team Services is based off of Windows authentication. The
product will not accept Project Server accounts, and if you use project
server
accounts you will encounter various errors when using SharePoint.

Matt S.
Project Server Specialist
(e-mail address removed)