The following issues and limitations are known to exist when you perform a
synchronization between CollabNet
TeamForge8.0 and your Microsoft Project
plan.
Known issues
- Update task status in CollabNet
TeamForge through Microsoft Project plan
during initial synchronization
- When you modify task details in your Microsoft Project plan, and synchronize it with
TeamForge, the task status is not updated in
TeamForge. This issue occurs only during the
initial synchronization.
- Delete task (empty task folder) in Microsoft Project plan does not ask for
confirmation
- When you attempt to delete an empty task folder in Microsoft Project plan (a row in
the Microsoft Project plan), the folder is deleted without prompting the user to confirm
the delete.
- Functionality of Migrate TeamForge Synchronization Data
- Attempting to access the Migrate TeamForge Synchronization Data
menu option displays an irrelevant error message.
- Complete unbind does not happen
- After you unbind your Microsoft Project plan from TeamForge, there is no confirmation message stating
that the unbind was successful.
- Object reference not set to an instance of object" error
- During the synchronization process, if you perform an action against Microsoft Project
plan rules, the error "Object reference not set to an instance of object" is
displayed.
Limitations
- If you delete a valid journal (.sfj) file or use a different one, an error message is
displayed preventing you from proceeding with the synchronization process.
- Changes made to the start and end date fields in your Microsoft Project plan do not reflect
in TeamForge after synchronization.
- Changes made to the Successor field in your Microsoft Project
plan do not reflect in TeamForge after
synchronization.