How to migrate revisions that doesn't exist in the target? #3128
Replies: 4 comments
-
|
The system can only migreate revissions from a source to a target when the source revision is newer than the target. Can you check if the target has been "edited" more recently than the source for that work item? |
Beta Was this translation helpful? Give feedback.
-
|
The problem was into revision's dates. I updated the target workitem (ReflectedWorkItemId) and it become newer. Manualy uptaing the source workitem solve the porblem. Another question - how to disable attachments migration? Is seting Enabled to false into the TfsAttachmentTool enough? |
Beta Was this translation helpful? Give feedback.
-
|
We have tried this config How to disable image migration? Setting "FixHtmlAttachmentLinks": to false got the same effect - images become unavaliable after the migration |
Beta Was this translation helpful? Give feedback.
-
|
We found another way using "FieldMapType": "RegexFieldMap" |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi!
We got two on premises Azure DevOps servers. The target server is the copy of the source sever before update 2022 Update 2 to AzureDevOps 25H2. Because of this issue all attaches become unavaliable. After the update there was some changes, so we have restored from backup before the update a new server instances (the target) and trying to migrate changes, than has ben made after the update
After manual updating of the ReflectedWorkItemId into a work item on the targer server I'm truing to migrate new revisions from the source with the following config
According to the log the utility sees the revisions diffrence, but finaly says
Found 0 revisions to migrate on Work item:Sourceand leaves the target work item unupdated:We have tried many variants of the TfsRevisionManagerTool confg section .We also have tried to disable attaches migration (the erros in the log's listing is because of the specified issue) whit the same results.
We have also tryed to use Tfs WorkItem Bulk Edit Processor, but we have failed to fount working configuration this that processor.
Could You, please, provide a working example of configuration.json for our migration scenario, or such scenario (migrate only revisions, than are newer) is unsupported?
Beta Was this translation helpful? Give feedback.
All reactions