S
Steven Douglass
Project Pro 2007/Project Server 2007
Topic: Deliverables linked to tasks
Details
I've added deliverables to my project plans via Project Pro 2007 and
published them to WSS, that seems to work nicely. The issue that I am having
is managing those deliverables because they seem to get out-of-sync with the
task they are linked to.
Let me provide an example scenario. I create a project that has several
tasks, organized by summary tasks. I then add new deliverables (via Project
Pro 2007) and LINK them to summary tasks. I do this for each summary task
because each is a deliverable for this project. I publish and we move on.
Issue #1
Now, when I am back in Project Pro 2007 and updating/editing tasks of a
summary task (no resource assignment), the summary task finish date can move
out due to increased work but the deliverable finish date does not. I end
having a deliverable that finishes before the summary task finishes - should
they not be in sync? I'm assuming that I missed something here because this
seems like an odd behavior, especially since the deliverable is LINKED to the
summary task, I would expect that it moves with the LINKED task. Perhaps
there are a couple of syncing steps that I've missed along the way here. I
manage these deliverables and task/project updates via Project Pro 2007, we
do not have timesheets enabled yet.
Issue #2
So, thinking that I simply have to RE-LINK the deliverable to the summary
task, I edit the deliverable in Project Pro 2007 by going to Collaborate ->
Manage Deliverables -> [select deliverable] -> Edit Deliverable. I see that
the dates are not in sync with the summary task and the Link to selected task
is ENABLED. This is a result of Issue #1 I assume. But what gets me is that
when I click the 'Go to linked task' it sets focus on the incorrect task. The
task ID in the deliverable is properly identified but for reasons that I
can't explain, focus ends up on a task that is exactly 17 "tasks" below. This
is the same behavior for all LINKED deliverables/tasks.
Note: I did not add any more tasks to the project plan so I can't explain
why it would jump down by this many for all linked tasks.
As always, help is appreciated. Thanks.
Topic: Deliverables linked to tasks
Details
I've added deliverables to my project plans via Project Pro 2007 and
published them to WSS, that seems to work nicely. The issue that I am having
is managing those deliverables because they seem to get out-of-sync with the
task they are linked to.
Let me provide an example scenario. I create a project that has several
tasks, organized by summary tasks. I then add new deliverables (via Project
Pro 2007) and LINK them to summary tasks. I do this for each summary task
because each is a deliverable for this project. I publish and we move on.
Issue #1
Now, when I am back in Project Pro 2007 and updating/editing tasks of a
summary task (no resource assignment), the summary task finish date can move
out due to increased work but the deliverable finish date does not. I end
having a deliverable that finishes before the summary task finishes - should
they not be in sync? I'm assuming that I missed something here because this
seems like an odd behavior, especially since the deliverable is LINKED to the
summary task, I would expect that it moves with the LINKED task. Perhaps
there are a couple of syncing steps that I've missed along the way here. I
manage these deliverables and task/project updates via Project Pro 2007, we
do not have timesheets enabled yet.
Issue #2
So, thinking that I simply have to RE-LINK the deliverable to the summary
task, I edit the deliverable in Project Pro 2007 by going to Collaborate ->
Manage Deliverables -> [select deliverable] -> Edit Deliverable. I see that
the dates are not in sync with the summary task and the Link to selected task
is ENABLED. This is a result of Issue #1 I assume. But what gets me is that
when I click the 'Go to linked task' it sets focus on the incorrect task. The
task ID in the deliverable is properly identified but for reasons that I
can't explain, focus ends up on a task that is exactly 17 "tasks" below. This
is the same behavior for all LINKED deliverables/tasks.
Note: I did not add any more tasks to the project plan so I can't explain
why it would jump down by this many for all linked tasks.
As always, help is appreciated. Thanks.