You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/config.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,6 +38,7 @@ The migration configuration file is defined in a json file with the properties d
38
38
|**suppress-notifications**|False|boolean|Set to True to suppress all notifications in Azure DevOps about created and updated Work Items. Default = False.|
39
39
|**include-development-links**|False|boolean|Set to True to migrated commit links from Jira to Azure DevOps. You will also need to fill out the **repository-map** property. Default = False.|
40
40
|**sleep-time-between-revision-import-milliseconds**|False|integer|How many milliseconds to sleep between each revision import. Use this if throttling is an issue for ADO Services. Default = 0 (no sleep).|
41
+
|**buffer-revisions-succeeding-attachment-imports-milliseconds**|False|integer|How many milliseconds to buffer each subsequent revision if there is a negative revision timestamp offset. Increase this if you get problems with VS402625 error messages. Default = 5 (ms).|
41
42
|**process-template**|False|string|Process template in the target DevOps project. Supported values: Scrum, Agile or CMMI. Default = "Scrum".|
42
43
|**link-map**|True|json|List of **links** to map between Jira and Azure DevOps/TFS work item link types.|
43
44
|**type-map**|True|json|List of the work item **types** you want to migrate from Jira to Azure DevOps/TFS.|
Copy file name to clipboardExpand all lines: docs/faq.md
+21-4Lines changed: 21 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -430,7 +430,26 @@ curl -D-
430
430
"http://johnie:8081/rest/api/2/search"
431
431
```
432
432
433
-
## 19. Sprint names are corrupted. ADO Iteration paths are named "[ synced = false ]"
433
+
## 19. I get the error message "VS402625: Dates must be increasing with each revision."
434
+
435
+
ADO can sometimes add a few milliseconds to the work item changedDate when adding an attachment. This can have unfortunate consequences if the tool attempts to import a subsequent revision with a changedDate that is less than the previous reivison that was successfully imported.
436
+
437
+
You may end up receiving an error message similar to this one:
438
+
439
+
```txt
440
+
[E][18:32:06] VS402625: Dates must be increasing with each revision.
441
+
[E][18:32:06] Work Item 15312 failed to save.
442
+
```
443
+
444
+
The solution is to buffer the subsequent revision's changedDate by a few miliseconds. This is the purpose of the configuration parameter `buffer-revisions-succeeding-attachment-imports-milliseconds` (default: 5). Add this parameter to your `config.json` file and try increasing the value by 1 (5, 6, 7, and so on...) until the import succeeds without errors.
## 20. Sprint names are corrupted. ADO Iteration paths are named "[ synced = false ]"
434
453
435
454
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.
436
455
@@ -458,9 +477,7 @@ It could be worth trying this mapping when running against Jira Cloud too:
458
477
459
478
It seems that for jira server, the field IDs can different between different developer instances. You can use the Get Fields endpoint to find out which field ID (customfield_xxxxx) is used by Sprint in your instance: https://developer.atlassian.com/cloud/jira/platform/rest/v3/intro/#about
460
479
461
-
Give it a try and let me know if it still does not work.
0 commit comments