locked
TFS Integration tool - moving project between TFS 2013 collections RRS feed

  • Question

  • Hi,
    We have some projects we want to move to a different team collection in TFS 2013.
    I created a new project with the same name and same WIT mods as the source project in the target collection and (after installing the 2012 and 2010 Team Explorers) managed to get the TFS Integration tool installed and set up a one way migration from the source project to the target one - however it comes up with conflicts.

    11/03/2015 09:59:43] TfsIntegrationService.exe Information: 0 : WorkItemTracking: Unresolved conflict: 
    [11/03/2015 09:59:43]   Session: c7b8eb41-fa52-45a9-8788-ddb79b973505
    [11/03/2015 09:59:43]   Source: d411b836-4a04-4357-a5e6-d1680bd2c152
    [11/03/2015 09:59:43]   Message: Cannot find applicable resolution rule.
    [11/03/2015 09:59:43]   Conflict Type: TFS WIT invalid field conflict type
    [11/03/2015 09:59:43]   Conflict Type Reference Name: ea1a518b-248b-43e3-90b2-62fe7eb5f366
    [11/03/2015 09:59:43]   Conflict Details: <ConflictDetailsProperties xmlns="http://schemas.datacontract.org/2004/07/Microsoft.TeamFoundation.Migration.Toolkit" xmlns:i="http://www.w3.org/2001/XMLSchema-instance"><m_propertyBag xmlns:a="http://schemas.microsoft.com/2003/10/Serialization/Arrays"><a:KeyValueOfstringstring><a:Key>SourceWorkItemID</a:Key><a:Value>3271</a:Value></a:KeyValueOfstringstring><a:KeyValueOfstringstring><a:Key>SourceWorkItemRevision</a:Key><a:Value>1</a:Value></a:KeyValueOfstringstring><a:KeyValueOfstringstring><a:Key>SourceFieldRefName</a:Key><a:Value>Mirror.System.AssignedTo</a:Value></a:KeyValueOfstringstring><a:KeyValueOfstringstring><a:Key>TargetTeamProject</a:Key><a:Value>Model</a:Value></a:KeyValueOfstringstring><a:KeyValueOfstringstring><a:Key>TargetWorkItemType</a:Key><a:Value>Task</a:Value></a:KeyValueOfstringstring><a:KeyValueOfstringstring><a:Key>TargetTeamFoundationServerUrl</a:Key><a:Value>http://1edevvmtfs:8080/tfs/sla</a:Value></a:KeyValueOfstringstring></m_propertyBag></ConflictDetailsProperties>
    [11/03/2015 09:59:43] 

    The field it's complaining about is Mirror.System.AssignedTo (who the work item is assigned to) which is just one of the standard fields and is definitely present in the target WIT definitions.

    Any idea why I'm getting these conflicts and how I can fix them?

    Thanks,

    Mark.

    Wednesday, March 11, 2015 10:34 AM

Answers

  • Hi Mark,

    I'd like to know whether you have customized your work item type for the team projects, and the conflict error details with screenshot. Please let us know what you mean when you say "created a new project with the same name and same WIT mods".

    If you don't have customization, you can create a new team project without source files and work items. Then try again to do the migration to check if it works for you. If you customized the work item type of source team project, then you can do to same customization for your target team project. Please check if the migration can be worked after taking the customization actions in both team projects.

    To do the migratoin with TFS integration Tools(2012 March) for TFS 2013, make sure Team Explorer 2012 is installed on the machine. If the issue persists, it would be better to elaborate more details about your scenario.

    Best regards,


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.


    Thursday, March 12, 2015 6:28 AM
    Moderator