TF203071: Error when branching a nested branch

TFS 2010 does not support branching a folder that contains child branches in it, and it will give you this error: “TF203071: The operation cannot be completed because the source folder that you specified contains a branch”.

The cause for this is the new branch visualization features.  To work around this, you’ll need to turn the branch back to a regular folder (the underlying branch doesn’t go away):

  • Select your child branch
  • Go to File –> Source Control –> Branching and Merging –> Convert to Folder

This turns the branch back to the “old-style”, which does not support visualization.  But you gain the ability to branch a folder with child branches.  Hopefully they will fix this in the next release.

About esteban

Esteban is the Founder and Chief Technologist at Nebbia Technology, an ALM consulting and Azure-powered technology company. He is a software developer with a passion for ALM, TFS, Azure, and software development best practices. Esteban is a Microsoft Visual Studio ALM MVP and ALM Ranger, Pluralsight author, and the president of ONETUG (Orlando .NET User Group).

4 thoughts on “TFS 2010 Dashboards with SharePoint 2010 (MOSS)

  1. Jose Medero

    Hi Esteban, i am working on integrating my company’s TFS 2010 with a SharePoint 2010 portal. I have been looking that several blogs shows that when the configuration is done they get several dashboards. In my case the only dashboard that was created was “My Dashboard”. Wath do I need to get other dashboards like the ones mentioned in your article.

    I am working on a sharepoint 2010 farm single server test enviroment with my production TFS 2010. My configuration goes as follows:
    – TFS 2010 Standard
    – SharePoint 2010 Enterprise
    – Sql 2008 r2 Enterprise with Report Server in Integrated Mode.
    – SP has been integrated with reporting services.

  2. Esteban Garcia

    Jose,
    Do you see any errors in the Team Project creation log? I seem to remember running into this before, and I think it had to do with permissions during the creation of the Team Project, but I may be mistaken. Can you take a look at your log file and let me know?

  3. Bob Cronin

    I know this is an old post Esteban, but it saved me today. Thanks for publishing!

  4. Anurag Jain

    Hi Esteban, Thanks for this nice explanation, But i do have some other requirement.
    Lest say if we have WorkItemLinkFilters LinkType=”System.LinkTypes.Hierarchy” then WorkItemTypeFilters should be “Task” and if we have WorkItemLinkFilters LinkType=”System.LinkTypes.Hierarchy” then WorkItemTypeFilters should be “child” only. Is it possible to achieve ?


Leave a Reply

Your email address will not be published. Required fields are marked *

Are you human? *