The following are limitations to the connector’s synchronization:
- Changes made to a task’s planning folder in TeamForge will not change the Release for the corresponding task’s backlog item in ScrumWorks.
- Planning folders created as releases in TeamForge will not create Releases in ScrumWorks.
- ScrumWorks Sprints cannot be created from TeamForge.
- ScrumWorks Themes cannot be created from TeamForge.
- Changes made in TeamForge to a Product’s planning folder will not change the corresponding Product name in ScrumWorks.
- ScrumWorks Releases cannot be edited from TeamForge.
- ScrumWorks Sprints cannot be edited from TeamForge.
- ScrumWorks Themes cannot be edited from TeamForge.
- ScrumWorks backlog items cannot be deleted from TeamForge.
- ScrumWorks tasks cannot be deleted from TeamForge.
- Moving a backlog item between products in ScrumWorks will not move the corresponding artifact in TeamForge.
- Moving a task between Products in ScrumWorks will not move the corresponding artifact in TeamForge.
- Attachments are currently not synchronized.
- Comments are only synchronized from TeamForge to ScrumWorks, not the other way around.
- The "Done" status value for TeamForge PBIs is semantically defined to be an "open status" to allow ScrumWorks Pro marking PBIs as done even if their child tasks are not marked as complete. Consequently, TeamForge PBIs will always appear to be open in all reports.
- ScrumWorks Pro entities defined on the program level (program releases and program themes) are duplicated into every TeamForge project mapped to a ScrumWorks Pro product that is part of the program.
- Since the connector only synchronizes release data from ScrumWorks Pro to TeamForge, status changes in TeamForge planning folders are ignored in ScrumWorks Pro.