<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>VS/TFS 2012 Tidbits: Merging Changes by Work Item</title><link>http://blogs.msdn.com/b/slange/archive/2012/07/11/vs-tfs-2012-tidbits-merging-changes-by-work-item.aspx</link><description>As the Visual Studio family of products (Visual Studio, TFS, Test Professional) nears its 2012 release, I thought I’d bring some short hits – tidbits, if you will – to my blog. Some of these are pretty obvious (well-documented, or much-discussed), but</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: VS/TFS 2012 Tidbits: Merging Changes by Work Item</title><link>http://blogs.msdn.com/b/slange/archive/2012/07/11/vs-tfs-2012-tidbits-merging-changes-by-work-item.aspx#10338714</link><pubDate>Sat, 11 Aug 2012 13:56:53 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10338714</guid><dc:creator>M.Radwan-MVP</dc:creator><description>&lt;p&gt;thanks for tip&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10338714" width="1" height="1"&gt;</description></item><item><title>re: VS/TFS 2012 Tidbits: Merging Changes by Work Item</title><link>http://blogs.msdn.com/b/slange/archive/2012/07/11/vs-tfs-2012-tidbits-merging-changes-by-work-item.aspx#10332273</link><pubDate>Sat, 21 Jul 2012 20:11:28 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10332273</guid><dc:creator>StevenLange</dc:creator><description>&lt;p&gt;@Colin - I don&amp;#39;t know that there&amp;#39;s a convenient way to merge by multiple work items at a time. Some might argue that merging changesets that are related to different work items all at the same time could reduce the discrete traceability of change propogation. By merging one work item&amp;#39;s changes at a time, you maintain complete traceability, and make it easier to roll out (or roll back) a specific work item change.&lt;/p&gt;
&lt;p&gt;But I do get what you mean - Perhaps there&amp;#39;s a CodePlex or VS Gallery utility that can help you?&lt;/p&gt;
&lt;p&gt;Thanks for your comment!&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10332273" width="1" height="1"&gt;</description></item><item><title>re: VS/TFS 2012 Tidbits: Merging Changes by Work Item</title><link>http://blogs.msdn.com/b/slange/archive/2012/07/11/vs-tfs-2012-tidbits-merging-changes-by-work-item.aspx#10331934</link><pubDate>Fri, 20 Jul 2012 11:25:22 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10331934</guid><dc:creator>Colin Dembovsky</dc:creator><description>&lt;p&gt;Hi Steven - I didn&amp;#39;t know you could track by work item until I read this post - great tip!&lt;/p&gt;
&lt;p&gt;This allows you to merge 1 work item easily - I think there&amp;#39;s still some folk who want to be able to merge more than 1 work item at a time. So to use your example, you&amp;#39;re tracking Task 80 (and merging changesets 17 &amp;amp; 18). What if I wanted to merge all the changesets for Task 80, 82, 85 and 87?&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10331934" width="1" height="1"&gt;</description></item></channel></rss>