Replies: 1 comment
-
Not realy. You would need to do an additional edit to bring the files across as well as update the description. I would suggest that you run a reverse update with some custom code. Loop through the target and for each item that has an old item in the Source bring across and update any images. This would be a custom processor... |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Would be great if someone has some suggestions or ideas around the following issue.
There was a previous migration from a year or so ago (before my time at the client), the problem is that the image attachments in the work items haven't been migrated but pointing back to the original collection.
The client haven't noticed this until now since the original collection and projects are still there, so the image location/links still works.
From some quick testing it looks like this have been resolved and can be fixed with FixHtmlAttachmentLinks option and set the FilterWorkItemsThatAlreadyExistInTarget to false.
But we wouldn't like to re-introduce e.g. work items that have been deleted since the first migration.
So is there a way to filter the "repair" to only update links in items that exist in the target?
Beta Was this translation helpful? Give feedback.
All reactions