TFS WorkItem Migration Processor #2481
giscus[bot]
bot
Replies: 9 comments 33 replies
-
|
Is there a why to write recursive queries. For example, I need to migrate specific Epics and all children Work Items (direct and indirect) |
Beta Was this translation helpful? Give feedback.
-
|
Not directly. You could tag all the items you want and move all items with the tag. |
Beta Was this translation helpful? Give feedback.
-
|
This is a beautiful tool. Is there a way to do 20000 work items at a time? Like do the query by date or maybe by the year? We've got 64000 work items and it's failing because it says it can only do 20000 at a time. |
Beta Was this translation helpful? Give feedback.
-
|
Never mind, we got that: we ended up adding "AND [System.CreateDate] >= '1/1/2020' AND [System.CreatedDate] <= '12/31/2021'" to go year by year and then just running several instances at the same time. We did two years at a time for most of the years, but we found one two-year period where they had more than 20K records, so it kicked it back. Anyway, we got it. |
Beta Was this translation helpful? Give feedback.
-
|
Thats what I do. |
Beta Was this translation helpful? Give feedback.
-
|
I'm new at the whole migration/setup and tool(great one) but i keep coming across this error using the setup below...,... Any thoughts? Error.... Setup..... (to migrate only workItems/attachments/screenshots..etc) |
Beta Was this translation helpful? Give feedback.
-
|
Stop trying to use AI to make the config and go read the docs! This config is not valid either. |
Beta Was this translation helpful? Give feedback.
-
|
Appreciate the response, though I must be frank …..after investing significant time iterating through configurations, referencing the official documentation line-by-line, and troubleshooting across multiple tool versions, it's discouraging to receive this kind of reply. If something specific is invalid, pointing that out would be far more helpful than a blanket statement. |
Beta Was this translation helpful? Give feedback.
-
|
@Lucarian77 your config includes elements that either no longer exist or were deprecated years ago. Almost all of the issues you listed can be resolved by starting from the Getting Started guide and using the sample provided there. While some of the inline examples vary in age, every sample in the Examples section of each documented feature is generated directly from the current code and is accurate. If you have an old config, we provide Let’s walk through the issues:
I’m not suggesting our docs are flawless, but everything you needed was right there on the Getting Started page. If you’d actually read through and followed the documented example, you wouldn’t be dealing with these errors. These tools are provided as-is by Azure DevOps consultants for other Azure DevOps consultants. They're not commercial and they’re not designed to be beginner-friendly. If you're unfamiliar with JSON, debugging in Visual Studio, or how the old TFS Object Model works, you might want to find someone to pair with. Also, you commented on the correct documentation but clearly didn’t follow it. One last note: you can format code in GitHub issues using single backticks for inline code and triple backticks for code blocks. See GitHub’s Basic writing and formatting syntax. I’ve cleaned up your post to improve readability. |
Beta Was this translation helpful? Give feedback.
-
|
@MrHinsh The only hiccup I came across is this:
Errors:
|
Beta Was this translation helpful? Give feedback.
-
|
These are all "INF" not errors... the system cant create a link to a work item that doesn't to exist yet. |
Beta Was this translation helpful? Give feedback.
-
|
We are trying to do the migration of workitems from one azure devops org to another. The work items migrate correctly except for the embedded images. The image placeholders shows up in target workitem Description field but no images in target. When I look at html extract of target work item description field, the image url is pointing to source devops organization. Following is our processor config: Can anyone please advise how to enable embedded image migration ? |
Beta Was this translation helpful? Give feedback.
-
|
Your config looks good. Do you get any messages in the logs? Id run your config through the visual studio debugger and see whats happening in the |
Beta Was this translation helpful? Give feedback.
-
|
Thanks a lot. I'll give it a shot. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks a lot @MrHinsh for pointing me to TfsEmbededImagesTool ERR] [16.1.0] EmbededImagesRepairEnricher: Unable to fix HTML field attachments for work item 7126 from https://dev.azure.com/Org1/ to https://dev.azure.com/Org2 Any suggestions would be appreciated. |
Beta Was this translation helpful? Give feedback.
-
|
We managed to get it to work by removing the Required option from Custom.Prio field in both Source and Destination. |
Beta Was this translation helpful? Give feedback.
-
|
I'm having trouble trying to migrate work items from the cloud to on-prem. I used the process-migrator to first migrate the process. I then created the project using the UI and next I'm trying to run the migration tool to get the work items. The error I'm getting is with trying to create the iterations. What is strange is that the log looks to me like it is trying to create the iterations at the Source not the Target. After running and then checking the on-prem Target project, I still just see the default 3 iterations from creating the project. Configuration{
"Serilog": {
"MinimumLevel": "Debug"
},
"MigrationTools": {
"Version": "16.2",
"Endpoints": {
"Source": {
"EndpointType": "TfsTeamProjectEndpoint",
"Authentication": {
"AuthenticationMode": "AccessToken",
"AccessToken": "*****",
},
"Collection": "https://dev.azure.com/acagroundtools",
"Project": "nFDIMU GT",
"ReflectedWorkItemIdField": "Custom.ReflectedWorkItemId",
"LanguageMaps": {
"AreaPath": "Area",
"IterationPath": "Iteration"
}
},
"Target": {
"EndpointType": "TfsTeamProjectEndpoint",
"Authentication": {
"AuthenticationMode": "AccessToken",
"AccessToken": "*****"
},
"Collection": "https://hq-tfs-offside/acagroundtools",
"Project": "nFDIMU GT",
"ReflectedWorkItemIdField": "Custom.ReflectedWorkItemId",
"LanguageMaps": {
"AreaPath": "Area",
"IterationPath": "Iteration"
}
}
},
"CommonTools": {},
"Processors": [
{
"ProcessorType": "TfsWorkItemMigrationProcessor",
"Enabled": true,
"UpdateCreatedDate": true,
"UpdateCreatedBy": true,
"WIQLQuery": "SELECT [System.Id] FROM WorkItems WHERE [System.TeamProject] = @TeamProject AND [System.WorkItemType] = 'Bug' ORDER BY [System.ChangedDate] desc",
"FixHtmlAttachmentLinks": true,
"WorkItemCreateRetryLimit": 5,
"FilterWorkItemsThatAlreadyExistInTarget": false,
"GenerateMigrationComment": true,
"SourceName": "Source",
"TargetName": "Target"
}
]
}
}Log |
Beta Was this translation helpful? Give feedback.
-
|
Your log shows a bunch of areas and iterations have been created.. Does it stop on the same one every time? |
Beta Was this translation helpful? Give feedback.
-
|
Yes it does stop on the same one every time. And no amount of refresh shows any iterations have been created in the target. In fact this is the REST API response to https://hq-tfs-offside/acagroundtools/nFDIMU GT/_apis/wit/classificationnodes?$depth=2{
"count": 2,
"value": [
{
"id": 263,
"identifier": "bf365b41-6d24-4dcf-8b6a-91774fa01615",
"name": "nFDIMU GT",
"structureType": "area",
"hasChildren": false,
"path": "\\nFDIMU GT\\Area",
"url": "https://hq-tfs-offside/acagroundtools/a7091e00-b8fe-49dc-ae3b-c9a4578d18c8/_apis/wit/classificationNodes/Areas"
},
{
"id": 258,
"identifier": "fa178e0b-7edd-41f4-b1ba-7b13ab8ab755",
"name": "nFDIMU GT",
"structureType": "iteration",
"hasChildren": true,
"children": [
{
"id": 260,
"identifier": "44e23053-751e-45a6-805d-fe2269d88112",
"name": "Iteration 1",
"structureType": "iteration",
"hasChildren": false,
"path": "\\nFDIMU GT\\Iteration\\Iteration 1",
"url": "https://hq-tfs-offside/acagroundtools/a7091e00-b8fe-49dc-ae3b-c9a4578d18c8/_apis/wit/classificationNodes/Iterations/Iteration%201"
},
{
"id": 261,
"identifier": "8eb6f61d-2feb-4540-9b13-18883af184eb",
"name": "Iteration 2",
"structureType": "iteration",
"hasChildren": false,
"path": "\\nFDIMU GT\\Iteration\\Iteration 2",
"url": "https://hq-tfs-offside/acagroundtools/a7091e00-b8fe-49dc-ae3b-c9a4578d18c8/_apis/wit/classificationNodes/Iterations/Iteration%202"
},
{
"id": 262,
"identifier": "f35a1829-d5e2-488d-8a1d-c39c0aac64e1",
"name": "Iteration 3",
"structureType": "iteration",
"hasChildren": false,
"path": "\\nFDIMU GT\\Iteration\\Iteration 3",
"url": "https://hq-tfs-offside/acagroundtools/a7091e00-b8fe-49dc-ae3b-c9a4578d18c8/_apis/wit/classificationNodes/Iterations/Iteration%203"
}
],
"path": "\\nFDIMU GT\\Iteration",
"url": "https://hq-tfs-offside/acagroundtools/a7091e00-b8fe-49dc-ae3b-c9a4578d18c8/_apis/wit/classificationNodes/Iterations"
}
]
}I have used this tool before with no problem on this same setup but that was more than a year ago on an older version. |
Beta Was this translation helpful? Give feedback.
-
|
Ah I figured it out! It was an Azure DevOps Server configuration issue on my part. I'll explain briefly. We have 2 Azure DevOps Servers that we use in a blue-green deployment type setup. We use a DNS CNAME to swap which one is production and backup so the short name I updated the public url in the Azure DevOps Server to match its current DNS CNAME and now things are working fine. |
Beta Was this translation helpful? Give feedback.
-
|
@MrHinsh I kindly need your feedback again...
In the 1st migration, all embedded images, within comments and such were migrated just. But in this version 16.2.10Preview 4 none of the embedded images are getting moved over. This is my setup.... any thoughts? ...much appreciated! |
Beta Was this translation helpful? Give feedback.
-
@MrHinsh It was working just fine in version 16.1. This is one the error messages I'm getting in version 16.2.10 P4 EmbededImagesRepairEnricher: Unable to fix HTML field attachments for work item 0 from https://dev.azure.com/source to https://dev.azure.com/target/ |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
Specifically, we should look at:
These are the only deliberate changes to the embedded images loader... but it could slo come from elsewhere... |
Beta Was this translation helpful? Give feedback.
-
|
@MrHinsh It was version v16.1.0 (Release) |
Beta Was this translation helpful? Give feedback.
-
|
What I did was just correction of authorization header. Without it, client returned To me, it seems that something has changed on the server side, that it redirects to some new address. Maybe if @Lucarian77 can debug it and inspect HTTP respone headers where it wants to redirect, it will help him. |
Beta Was this translation helpful? Give feedback.
-
|
@satano i ran it with Debug option.....I've attached a few screenshots |
Beta Was this translation helpful? Give feedback.
-
|
I did not mean this. I meant that you will run in from Visual Studio, let it fail and then inspect the state. I am not sure, but probably you can set breakpoint in line |
Beta Was this translation helpful? Give feedback.
-
|
Or maybe set |
Beta Was this translation helpful? Give feedback.
-
|
@satano I did not spend too much time trying to debug. Instead, i cleanup the previous installation and did a clean reinstall of version 16.2.10-Preview.8. As of right now, 3200 work items are getting migrated just fine, including embedded images, links...etc.... @MrHinsh @satano Thank you again for your input. Appreciated! |
Beta Was this translation helpful? Give feedback.
-
|
@MrHinsh - I'm attempting to run the TfsWorkItemMigrationProcess against a source and destination that are using a default process type (i.e. Agile) - appears this does not work because getting warnings that the "Custom.RelfectedWorkItemId" field does not exist. Should I assume I need to create an inherited process add the field to work items for my source and desitation and then move my project to the new inerited process crerated to get this to work? |
Beta Was this translation helpful? Give feedback.
-
|
You have two errors there:
I do not know if you really need these types of work item. Probably exclude them from migration, or add required field to them. |
Beta Was this translation helpful? Give feedback.
-
|
I'm using the following statement in my Processors section for TfsWorkItemMigrationProcessor - however the check seems to still look for these work item types "WIQLQuery": "SELECT [System.Id],[System.WorkItemType] FROM Workitems WHERE [System.TeamProject] = @teamproject AND [System.WorkItemType] NOT IN ('Test Suite','Test Plan','Shared Steps','Shared Paramter') ORDER BY [System.ChangedDate] desc", Is my query wrong? |
Beta Was this translation helpful? Give feedback.
-
|
Can someone confirm, is the WIQLQuery selectively removing work items to be reviewed? if so, why does the Validating work item types appear to list work items that I have specifically excluded with my query? 
|
Beta Was this translation helpful? Give feedback.
-
|
Its because validation of work item types validates all work item types. This is on purpose. Some time ago, first work item types were loaded (using your set query) and then were validated only those work item types, which were really loaded. But the downside of this was, that it took too long in bigger projects. For example in our case, we had 10 000 work items to migrate (and it is not a really big project at all) and it took more than 5 minutes to load them. Then they were validated and migration was stopped. We moved validation an the begining of the process – before the work items are loaded – to make validation really fast. So clients are not waiting just to realize, that something is wrong. I have plan to improve this validation to minimize the problems you had. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for sharing - glad to know it's on the radar (in the backlog). |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
TfsWorkItemMigrationProcessor
The
WorkItemMigrationContextprocessor is used for migrating work items from one Azure DevOps instance to another. This encompasses a variety of activities:Overall, the
WorkItemMigrationContextprocessor is a comprehensive tool for transferring work items and their associated data and metadata between Azure DevOps instances. It should be used whenever there is a need to move work items between instances while preserving as much information as possible.https://nkdagility.com/learn/azure-devops-migration-tools/Reference/Processors/TfsWorkItemMigrationProcessor/
Beta Was this translation helpful? Give feedback.
All reactions