Known issue with TFS Sync and BacklogPriority field
2011 R2 of TeamPulse was released with an issue that causes drag and drop prioritization in the backlog to fail with an exception. The exception occurs because it is assumed that all items in the backlog have a value in the BacklogPriority field. Unfortunately there is a bug in the integration service such that new items created in TFS and synchronized into TeamPulse do not get their BacklogPriority field populated.
There are 2 aspects to this problem; fixing the current problem and preventing the problem from recurring.
In order to fix the current problem the attached zip file contains an SQL script that, when run, will populate any missing BacklogPriority fields. Ensure that you backup your database prior to running the script.
In order to prevent this problem from occurring again, there are a few options:
1. If you have done a one way sync from TFS for a new project and intend on remaining in TeamPulse and no longer creating new items in TFS then the problem will no longer occur. You don't need to do anything else.
2. If you will continue to create new items in TFS the attached zip file contains an assembly with a hotfix that corrects the problem. In order to apply this assembly, on the server where TeamPulse is installed, stop the TeamPulse Integration service, locate the TeamPulse.Integration.Core.dll in the IntegrationService folder of the installation, make a backup of the existing dll and then add the hotfixed assembly in it's place. Restart the integration service and the problem will be solved.
This issue will be fixed in the next release of TeamPulse.