Why are Microsoft Project and CollabNet TeamForge doing things I don't expect?

When you synchronize Microsoft Project and CollabNet TeamForge, in some conditions the tool works as designed but the behavior might seem unexpected. For example, an empty task folder in CollabNet TeamForge creates a blank task in Microsoft Project.

Why are there blank tasks in Microsoft Project?

If you have an empty task folder in CollabNet TeamForge, Microsoft Project creates a blank task when synchronizing. This is because Microsoft Project does not have the concept of a task folder, only a parent task. The blank task remains only until you add one or more tasks in the folder.

How are task dependencies handled?

Microsoft Project enforces stricter dependency handling than CollabNet TeamForge does. If you use CollabNet TeamForge dates that conflict with Microsoft Project dependency handling, Microsoft Project adjusts your dates during synchronization. For example, CollabNet TeamForge allows you to have a task end date later than the start date of a successor task. Microsoft Project does not, and adjusts the start date of the successor task.

Are dependency constraints supported?

Synchronization does not support dependency constraints. For example, consider a scenario where the start date of a successor task equals the end date of a predecessor task plus x number of days. If you change the end date of the predecessor task in CollabNet TeamForge , and then synchronize, Microsoft Project does not adjust the start date of the successor task until the end date of the predecessor task runs up against this start date.

Note: This is contrary to the cascading dependency handling behavior in CollabNet TeamForge.

Are zero-duration milestones synchronized?

Zero-duration milestones in your Microsoft Project plan are not synchronized with CollabNet TeamForge. They remain in your Microsoft Project plan, but do not generate CollabNet TeamForge tasks. Only milestones with start dates, end dates, and no dependencies, get synchronized with CollabNet TeamForge.

Does synchronization support removal of dependencies?

In your Microsoft Project plan, if you change the start date of a task that has predecessor dependencies, you are shown a popup window asking whether you want to retain the dependency. You must exit the popup window and remove the dependency manually in order for the change to be synchronized with CollabNet TeamForge. If you remove the dependency using the popup window, it could result in synchronization errors.

Are multiple resource assignments supported?

Microsoft Project allows you to assign a task to multiple resources, and to specify the percentage of time each resource will spend on the task. CollabNet TeamForge supports only single-resource assignment per task. If you have more than one resource assigned to a task in Microsoft Project, with or without percentage allocations, this information gets removed during synchronization. The task is assigned 100 percent to the first resource specified.

Are Gantt chart changes recognized?

Microsoft Project allows you to manipulate task start and end dates by dragging the task bars on the Gantt chart. Task changes made in this way are not recognized by CollabNet TeamForge and are not synchronized.

Are task notes synchronized?

No, task notes entered in Microsoft Project are not synchronized.

How is task duration handled?

Microsoft Project allows you to have a task duration specified in hours. When synchronizing, any task with a duration in hours is rounded up to the nearest whole day.

Parent topic: Why can't I synchronize between Microsoft Project and CollabNet TeamForge?