Interpret Merging Tasks

The first thing to consider when merging tasks is to ensure that the tasks to be merged are in fact the same.  Listed are a few circumstances when you should and shouldn't merge two tasks:





The following will be kept in the merged task:


For both Knowledge and Capability, there are three things that go together as one:


If the persistent task is set to Has Knowledge/ Capability Component to Yes, the settings for duration and revision dates will remain the same as the persistent task.  However if the Has Knowledge/ Capability Component is set to No, and the Transient task contains the missing component, the transient task's component setting, duration and revision date will be carried across to the remaining task.

The assessments themselves function separately from the Has Component, Duration and Revision Dates trio.  Therefore, if assessments exist in the persistent task, the transient task's components will be cleared:


The task on the right is the persistent object.  The task on the left is the transient object.  If the persistent object does not contain a particular component that the transient object contains, that component (along with its properties) are added to the transient object.  However, if the persistent object already contains the component, if will maintain this component's properties after the merge.  If you had wished to keep the duration on the task, you would have had to change the transient and persistent objects.