Team leads creating new tasks for team members

[stevio]

[1] in my tasks, create a new task called "Task-X", 2 days effort
[2] in my tasks, reassign task to a team member Fred.
[3] Task-X appears in Fred's My Tasks page
[4] this generates two updates to the PM which he approves
[5] PM open plan, the new task has not appeared
[6] Task-X has now disappeared completely from Fred's view.

I can reproduce this everytime. It goes wrong as soon as the reassignment
request is approved. If PM approves the new task addition, republishes and
then goes back and approves the reassignement and then publishes again it
works fine.

Is there an alternative way for web users to add new tasks that are not
assigned to themselves that is known to work?

Thanks,
Stevio

 

[stevio]

After some hopeful experimenting trying to find a workaround, it appears that
if you create an auto-rule to automatically accept NEW TASK REQUESTS this
problem does not happen.

 

[Dale Howard [MVP]]

Stevio --

For whatever it's worth, the team leader cannot do step #2 until the PM has
already approved the new task created in step #1. You have found a
workaround using a Rule to autoapprove the new task, so that is good. Hope
this helps.

 

[stevio]

Hi Dale,

For whatever it's worth, the team leader cannot do step #2

That would make sense, but it doesn't seem to be the case in practice - they
are able to create a new task and then immediately re-assign it.

Cheers,
Stevio

Stevio --

For whatever it's worth, the team leader cannot do step #2 until the PM has
already approved the new task created in step #1. You have found a
workaround using a Rule to autoapprove the new task, so that is good. Hope
this helps.

[1] in my tasks, create a new task called "Task-X", 2 days effort
[2] in my tasks, reassign task to a team member Fred.
[3] Task-X appears in Fred's My Tasks page
[4] this generates two updates to the PM which he approves
[5] PM open plan, the new task has not appeared
[6] Task-X has now disappeared completely from Fred's view.

I can reproduce this everytime. It goes wrong as soon as the reassignment
request is approved. If PM approves the new task addition, republishes and
then goes back and approves the reassignement and then publishes again it
works fine.

Is there an alternative way for web users to add new tasks that are not
assigned to themselves that is known to work?

Thanks,
Stevio

 

[Dale Howard [MVP]]

Stevio --

Um, you said that it didn't work in your original message.

Hi Dale,

For whatever it's worth, the team leader cannot do step #2

That would make sense, but it doesn't seem to be the case in practice -
they
are able to create a new task and then immediately re-assign it.

Cheers,
Stevio

Stevio --

For whatever it's worth, the team leader cannot do step #2 until the PM
has
already approved the new task created in step #1. You have found a
workaround using a Rule to autoapprove the new task, so that is good.
Hope
this helps.

[1] in my tasks, create a new task called "Task-X", 2 days effort
[2] in my tasks, reassign task to a team member Fred.
[3] Task-X appears in Fred's My Tasks page
[4] this generates two updates to the PM which he approves
[5] PM open plan, the new task has not appeared
[6] Task-X has now disappeared completely from Fred's view.

I can reproduce this everytime. It goes wrong as soon as the
reassignment
request is approved. If PM approves the new task addition, republishes
and
then goes back and approves the reassignement and then publishes again
it
works fine.

Is there an alternative way for web users to add new tasks that are not
assigned to themselves that is known to work?

Thanks,
Stevio

 

[stevio]

Sorry for not being clearer. The team lead can do step 1 & 2, and the tasks
appear correct in Fred's my tasks area. It is only when the project manager
gets involved doing the approvals and the addition into the published plan
that things start to go wrong.

When the PM opens the plan it says "there is one update pending" - this is
the new task addition. PM approves this, and it then pops up with the
reassignment request that also needs approving. He approves this. It all gets
applied to the plan. When PM opens the plan the new task is missing
completely.

The auto-rule does seem to offer a work around, but does mean that
visibility is lost to the PM of new tasks. That isn't so bad for us as we
have some VBA that detects new & modified tasks whenever a project is opened
to allow the PM to review them and reschedule them as is appropriate (i.e.
fix some of the funnies with how tasks are updated via the web).

Stevio

Stevio --

Um, you said that it didn't work in your original message.

Hi Dale,

For whatever it's worth, the team leader cannot do step #2

That would make sense, but it doesn't seem to be the case in practice -
they
are able to create a new task and then immediately re-assign it.

Cheers,
Stevio

Stevio --

For whatever it's worth, the team leader cannot do step #2 until the PM
has
already approved the new task created in step #1. You have found a
workaround using a Rule to autoapprove the new task, so that is good.
Hope
this helps.




[1] in my tasks, create a new task called "Task-X", 2 days effort
[2] in my tasks, reassign task to a team member Fred.
[3] Task-X appears in Fred's My Tasks page
[4] this generates two updates to the PM which he approves
[5] PM open plan, the new task has not appeared
[6] Task-X has now disappeared completely from Fred's view.

I can reproduce this everytime. It goes wrong as soon as the
reassignment
request is approved. If PM approves the new task addition, republishes
and
then goes back and approves the reassignement and then publishes again
it
works fine.

Is there an alternative way for web users to add new tasks that are not
assigned to themselves that is known to work?

Thanks,
Stevio