Merge pull request #1127 from solidify/feature/add-option-to-skip-older-changeddate-error-handling

Add option to skip handling of errors where the supplied ChangedDate was older than the latest revision already in ADO

Author: Alexander-Hjelm

azure-pipelines.yml

@@ -37,14 +37,18 @@ steps:
   inputs:
     restoreSolution: '**\*.sln'
 
-- task: SonarCloudPrepare@1
-  displayName: 'Prepare analysis on SonarCloud'
-  inputs:
-    SonarCloud: SonarCloud
-    organization: solidify
-    projectKey: 'jira-azuredevops-migrator'
-    projectName: 'jira-azuredevops-migrator'
-    projectVersion: '$(Build.BuildNumber)'
+# 2025-08-26
+# Alexander Andersson
+# Disabled SonarCloud build tasks due to expired token. The SonarCloud Service Connection does currently not work. 
+
+#- task: SonarCloudPrepare@1
+#  displayName: 'Prepare analysis on SonarCloud'
+#  inputs:
+#    SonarCloud: SonarCloud
+#    organization: solidify
+#    projectKey: 'jira-azuredevops-migrator'
+#    projectName: 'jira-azuredevops-migrator'
+#    projectVersion: '$(Build.BuildNumber)'
 
 - task: VSBuild@1
   displayName: 'Build solution WorkItemMigrator'
@@ -53,13 +57,13 @@ steps:
     platform: '$(BuildPlatform)'
     configuration: '$(BuildConfiguration)'
 
-- task: SonarCloudAnalyze@1
-  displayName: 'Run Code Analysis'
+#- task: SonarCloudAnalyze@1
+#  displayName: 'Run Code Analysis'
 
-- task: SonarCloudPublish@1
-  displayName: 'Publish Quality Gate Result'
-  inputs:
-    pollingTimeoutSec: '300'
+#- task: SonarCloudPublish@1
+#  displayName: 'Publish Quality Gate Result'
+#  inputs:
+#    pollingTimeoutSec: '300'
 
 
 - task: DotNetCoreCLI@2

docs/faq.md

@@ -534,6 +534,20 @@ Example `config.json`:
   "changeddate-bump-ms": 5,
 ```
 
+### Disable the built-in error handling for the error message VS402625
+
+If your Importer gets stuck in a loop where it keeps outputting the following line over and over again:
+
+```txt
+[W][11:15:29] Received response while updating Work Item: VS402625: Dates must be increasing with each revision.. Bumped Changed Date by 2ms and trying again... New ChangedDate: 3/31/2016 3:21:38 PM, ms: 172
+```
+
+You can revert to throwing the error message instead of raising a warning. This may cause the tool to migrate incomplete issue data, but the execution will continue. in order to do this, set the value of **changeddate-bump-ms** to 0 in you config.json, for example:
+
+```json
+  "changeddate-bump-ms": 0,
+```
+
 ## 22. Sprint names are corrupted. ADO Iteration paths are named "[ synced = false  ]"
 
 The issue is usually that a custom field has been defined in Jira which is also named "Sprint", and the tool is picking up this field instead of the default Srpint field.

src/WorkItemMigrator/WorkItemImport/WitClient/WitClientWrapper.cs

@@ -126,7 +126,7 @@ public WorkItem UpdateWorkItem(JsonPatchDocument patchDocument, int workItemId,
                     {
                         // Handle 'VS402625' error responses, the supplied ChangedDate was older than the latest revision already in ADO.
                         // We must bump the ChangedDate by a small factor and try again.
-                        if (ex2.Message.Contains("VS402625"))
+                        if (ex2.Message.Contains("VS402625") && ChangedDateBumpMS > 0)
                         {
                             foreach (var patchOp in patchDocument)
                             {
@@ -143,7 +143,7 @@ public WorkItem UpdateWorkItem(JsonPatchDocument patchDocument, int workItemId,
                         }
                         // Handle 'VS402624' error responses, the supplied ChangedDate was in the future.
                         // We must wait a while and try again.
-                        else if (ex2.Message.Contains("VS402624"))
+                        else if (ex2.Message.Contains("VS402624") && ChangedDateBumpMS > 0)
                         {
                             Logger.Log(LogLevel.Warning, $"Received response while updating Work Item: {ex2.Message}." +
                                 $" Waiting and trying again...");