Known Tasktop Sync limitations

Integration Visualizer		Appendix: Task Synchronization Troubleshooting

Known Tasktop Sync limitations

Task Linking limitations

Tasktop Sync does not support automated back-linking yet.

Tasktop Synchronization limitations

Here are some known limitations of Tasktop Sync Task Synchronization. There are other vendor-specific limitations; check the Certified Connectors document for more information.

Tasktop Sync does not yet map links in comments which refer to tasks which originated in the other repository. Any comments from the foreign repository which refer to IDs in the foreign repository (e.g. “See bug 32”) will remain unchanged, even if the ID in the current repository is completely different. In future releases of Tasktop Sync, the links will get properly mapped to the current IDs.
Tasktop Sync does not synchronize deletions. If you delete a task from one repository, that will not delete it from the proxy repository.
If Tasktop Sync has been stopped for a long time and then started again it may occasionally fail to run the Changes Query on the specified interval. This should be noticeable right away as no tasks will be synced. Restarting Sync again should resolve the issue.
In rare cases, the Services View may become minimized with no obvious way of bringing it back to its normal state. To restore the Services view type Ctrl-3, and in the popup dialog type “Reset Perspective” and choose the corresponding menu option.
Tasktop Sync can only synchronize one task type (e.g. defect, requirement, work item, etc) per task-mapping. If you want to synchronize more than one task type, then you need to have multiple task-mapping sections.
When logging into a Windows server using RDP, even as the Administrative user, the RDP login is not the console session on the server. This can cause problems when attempting to configure Tasktop Sync when it is installed as a Windows service. The Tasktop Sync dashboard is only available on the console session of a Windows server when it has been installed as a service. The symptom of this problem is that Tasktop Sync dashboard does not appear after selecting “Allow service to interact with the desktop” in the Tasktop Sync Service Manager and restarting the service. To work around this problem on Windows, instead of using the standard Remote Desktop Connection client on your workstation, open up a command prompt and use the following command:

mstsc /admin /v:tasktopsync.example.com

You should replace tasktopsync.example.com with the hostname of the computer running Tasktop Sync in the above command. This command will open a remote desktop session to the Windows server that uses the console session which allows Tasktop Sync configuration to function normally.