Component assignments don't propagate into role-driven workflows
Brought to you by:
ken_raisor,
tuma
Menu
▾
▴
#374 Component assignments don't propagate into role-driven workflows
It is a best practice to create components in the WBS representing future work, and potentially assign them to individuals in support of capacity planning.
In the past, if you applied a workflow to one of those components, the capacity-planned assignments would propagate into the tasks created by the workflow, and those new tasks would automatically be assigned to individuals.
However, if the workflow uses role names (entered in the "Performed By" column), this functionality no longer works. Applying a workflow will create tasks, then show the role name placeholders for each new task. The capacity-planned assignments on the parent component won't propagate into the newly created tasks at all.
As a result, you must manually assign roles to people. This is time-consuming and tedious. It is also error prone, since it introduces the possibility of assigning a role to the wrong person by mistake.
Fixed in Process Dashboard version 2.7