SvnBridge support integration with TFS Work Item by analyzing the commit comment.
You can mark a work item as fixed by adding "Work Items: Work Item Id, Another Work Item Id" to the commit comment.
Note that this should be the last thing on the line, and preferably, on a line of its own.
The follow formats are supported:

work item: 15
work items: 15, 16, 17

SvnBridge also supports the the standard SVN to bug tracking system integration, using SVN properties. You can define those by checking out your code and executing the following commands in the project root:

svn propset bugtraq:label "Work Item:" .
svn propset bugtraq:message "Work Item: %BUGID%" .
svn propset bugtraq:number true .
svn propset bugtraq:url project name goes here/WorkItem/View.aspx?WorkItemId=%BUGID% .
svn propset bugtraq:warnifnoissue true .

Remember to change the project name

After committing that, you'll find a dedicated text box for that in TortoiseSVN.
In addition to that, when viewing the commit log, you'll be able to go directly from the log to the work item page.

Last edited Mar 6, 2008 at 9:13 PM by Ayende, version 2


pflugs Apr 1, 2013 at 5:54 PM 
I tried modifying my settings the way JasonMcF described above, and I found that I was still getting errors. After doing an update to a Work Item (Bug) manually using Visual Studio and tracing the request/response using Fiddler, I realized that I needed additional columns in the XML. Once I added these columns in the XML to match the request I trapped using Fiddler, the next commit using Tortoise --> SVNBridge --> TFS closed the Bug without error.

However, I then discovered that the required columns are different for different types of Work Items. I was able to configure the SVNBridge XML files to work smoothly when resolving Bugs, but the settings did not work when trying to edit Tasks.

After downloading the SVNBridge code and looking through it, I believe the TfsWorkItemModifier class would need to be modified to allow for different XML configurations for different Work Items. The code in that class looks pretty straight-forward, so I might take a stab at modifying it to support this User Story sometime in the future.

However, it's easy enough to manually close tickets and associate them with changes using Team Explorer, Visual Studio Source Explorer, etc., and the feature I was REALLY after was simply connecting TortoiseSVN to TFS, which works just fine.

I'll put this on my "Friday afternoon" work list... ;-)

JasonMcF Aug 11, 2009 at 9:09 AM 
See may be the solution to your problem. The main cause of the problem is that the default template object references are the ones used by CodePlex.

I was able to get the linking working by modifying the file AssociateWorkItemWithChangeSetMessage.xml and copying it locally to where SvnBridge.exe is located. I replaced CodePlex.UpdateBy with System.ChangedBy (this will be dependent on the project template you are using). The file can be retrieved from the Codeplex repository (SvnBridgeLibrary.Infrastructure.Messages).

alexander123 Apr 29, 2009 at 11:41 AM 
Doesn't work. SvnBridge v4, TFS 2008.
Error: Failed to associate work item with changeset. See for details:

CERobertson Mar 19, 2009 at 7:22 AM 
Fantastic. Every step worked perfectly with out a single issue. I'm loving all of CodePlex, thanks!

xelibrion Dec 16, 2008 at 9:11 AM 
How to integrate TortoiseSVN with standart TFS bugtracking system?
I'm using SvnBridge v3. In bugtraq:url property I explain url "http://tfsServerName/my%20project%20name/WorkItem/View.aspx?WorkItemId=%BUGID%", but it not working - changeset not associated with workitem after commit.