jira-azuredevops-migrator
jira-azuredevops-migrator copied to clipboard
solidify
ADO history has incorrect change dates (Incompatibility with New Boards Hub feature)
Describe the problem A clear and concise description of what the problem/bug is.
I think this is an issue with Azure Devops with their New Board Hubs feature. I have sent this issue to Microsoft.
When looking at the History of a Feature or any work item With New Board Hubs disabled: The dates show correctly
I have circled the dates when the changes were made
If I enable New Board Hubs I get:
The changes look like they were made today (when I imported them
I don't believe this is an issue with the migrator
To Reproduce Steps to reproduce the behavior:
- Go to '...'
- Click on '....'
- Scroll down to '....'
- See error
Tool version
- Version of the jira-azuredevops-migrator tool [e.g. 2.3.117]
Attachments
Please attach the following files:
- config.json
- jira-export-log.txt
- wi-import-log.txt
Screenshots If applicable, add screenshots to help explain your problem.
I know that we have experienced compatibility issues with New Board Hubs before. See: https://github.com/solidify/jira-azuredevops-migrator/issues/607
Might have to contact the microsoft support on this one, as VincentVerweij did
MS say I am the only person with this issue and they can't reproduce it. Does anybody else have this problem?
@Alexander-Hjelm Are you able to tell me what field in ADO the above dates go into in the history? From ADO I tried to report on history and couldn't find a field with these dates in it.
Cheers, John
It should be System.CreatedDate and System.ChangedDate. See: https://learn.microsoft.com/en-us/azure/devops/boards/queries/history-and-auditing?view=azure-devops&tabs=browser#fields
MS say I am the only person with this issue and they can't reproduce it. Does anybody else have this problem?
Hi @RoyalWulf, I know I'm a bit late, but I've got the exact same problem. I've disabled the New Boards hub for now.
We have verified the issue on our environment. The issue has something to do with the fact that New Board Hubs uses a different data source for the dates than the System.ChangedDate field. This is outside of our control, and we have been unable to identify how the dates are fetched. There does not seem to be any other work item field that matches the value displayed in the Work Item History.
One of our technicians is in a dialogue with MS to try and find a solution.
The temporary solution seems to be to disable New Board Hubs for now.
@Alexander-Hjelm Ah, I was going to do some trial and error today to try and find the date it uses, but glad you told me that! :)
Of course you are welcome to do your own trial and error and see if maybe you can spot anything that we haven't. This is just the status update from us :D
MS say they are rolling New Boards Hub feature out now so the temporary fix (ie turn off the feature) may not be available soon