I have seen that migrated changesets with the free migration utility (2.0) no longer migrates the actual user who made those CheckIns
My question is:
¿ What about the changeset check-In date ?
I have read is a Know limitation ( from https://visualstudiogallery.msdn.microsoft.com/28a90a17-d00c-4660-b7ae-42d58315ccf2 ):
Point 6:
Version Control Known Limitations
- If Branch/Move across project has been done in your on-premises TFS and only some of those projects are selected for migration. Then the utility will convert Branch/Rename (Move) -> to -> Add change type.
- Branching of a folder as a new project is not supported by the utility. Since in the VSO the $/ProjectName folder already exists.
- Migration of data in a project where tf destroy was performed with /keephistory parameter is not supported in the utility, since the data in question is no longer present in TFS.
- Labels created at Collection Level scope will not be migrated.
- Migration of check-in notes, check-in policies is not supported.
- The Check-in Date of a change set(s) will not be retained in VSO. Instead the current time value will be set by default.
As these limitations are below :
2.3.2 Functionalities Supported (Commercial Utility)
Does it means that The Check-In Date cannot be migrated with free even commercial Version ? Is there any workaround to migrate that check-in date? Or is not possible?
Thanks in advance.